Fix Execution Drag by Developing the Leadership Team as a Group

Why group development is the hidden lever in execution

If your leadership team is “busy” but execution keeps slowing down, you’re likely not looking at a capacity problem. You’re looking at a membership and dynamics problem—how people join, influence, disagree, decide, and follow through as a group.

Most mid-sized organisations try to fix this with more structure: new processes, new tools, new meetings, a refreshed org chart. Those interventions can help, but they rarely touch the real friction: the unwritten rules that govern trust, accountability, and decision-making between functions.

Group development is a practical lens for identifying those unwritten rules. It explains why teams that are full of capable individuals can still operate in silos—and what to do next without turning the conversation into blame.

What “group development” actually means (and why leaders should care)

Group development is the psychological journey a set of individuals goes through before they become a reliable team. It’s not about personality types or whether people “get along.” It’s about how the group establishes safety, roles, norms, and a shared way of making decisions under pressure.

In leadership teams, the cost of skipping this development is rarely obvious in a single moment. It shows up as decision cycles that stretch across multiple meetings, handoffs that require “just one more check,” and quiet conflict between functions (e.g., Sales commits; Ops absorbs the risk; Finance blocks; everyone complains).

A helpful way to understand it: your organisation has formal systems (KPIs, reporting lines, governance). But your team runs on informal systems (who gets heard, what’s safe to challenge, how commitments are made, how accountability is enforced). Group development is the work of making the informal system visible—so you can deliberately improve it.

The four predictable stages—and how dysfunction hides in each

Teams tend to move through recognisable stages as they form and mature. Different models use different names, but the pattern is consistent: early politeness, then friction, then alignment, then high performance. The risk is not being “in a stage.” The risk is getting stuck there while the business keeps demanding faster execution.

Early-stage teams often look fine on paper. The meetings are calm, the updates are thorough, and everyone is professional. But underneath, people are still testing whether it’s safe to disagree, who really has authority, and what happens when priorities collide.

Later-stage teams can still be stuck if they’ve normalised workarounds. They may appear productive because things get done—yet the same issues resurface: revisiting decisions, unclear ownership, and silo optimisation.

Stage 1: Polite alignment (high courtesy, low truth)

In this stage, teams prioritise harmony and information-sharing. People are careful with disagreement, and meetings can become “status theatre” where work is reported rather than integrated across functions.

What it often sounds like:

• “Let’s take that offline.”
• “I’m sure we can make it work.”
• “We’re aligned… mostly.”

The hidden cost is that risks don’t surface early, so they surface late—when change is expensive.

Stage 2: Friction and testing (the necessary discomfort)

This is the stage many leaders try to avoid. It’s where the group tests boundaries: who can challenge whom, what happens when someone blocks, and whether decisions stick after the meeting.

When this stage is avoided, teams don’t become “nice.” They become political. Disagreement moves into side conversations, escalations, and passive resistance.

Healthy friction looks like direct debate with respect. Unhealthy friction looks like defensiveness, sarcasm, and “yes in the room, no in execution.”

Stage 3: Norming (shared rules that reduce friction)

Here the team starts to codify how it works: how decisions are made, what “ownership” means, what gets escalated, and what’s expected cross-functionally.

This is where execution speed is won. Not through more pressure, but through fewer repeated negotiations. When norms are clear, handoffs become smoother because people know what “good” looks like and what they can expect from each other.

Stage 4: High performance (trust + clarity + pace)

At this stage, teams can move fast without chaos. They challenge each other early, commit clearly, and follow through without constant reminders.

Importantly, high performance doesn’t mean “no conflict.” It means conflict is handled quickly and cleanly—without dragging the organisation into it.

Why functional silos persist even with smart leaders

Silos don’t exist because leaders don’t care. They persist because they’re psychologically efficient. They reduce short-term tension by letting each function optimise locally and avoid the messy work of negotiating shared priorities.

This is why many leadership teams default to familiar fixes: more meetings, new dashboards, tighter governance, another planning cycle. These tools can create the appearance of control, but they don’t automatically create shared accountability.

Silos also persist because the organisation learns workarounds. People become fluent in navigating around misalignment: double-checking decisions, pre-aligning in side meetings, escalating to get movement. Those behaviours become “how we do things,” even when everyone hates them.

If you want to break silos, you need to change the team’s membership dynamics—the lived experience of who belongs, who influences, and how commitments are made across boundaries.

The diagnostic: how to tell what stage your team is in

Most leaders sense something is off, but struggle to name it. A simple diagnostic is to observe where energy goes in meetings: toward solving the business problem, or toward managing each other.

Look for patterns across three areas: decisions, trust, and accountability. When those are healthy, execution is usually healthy.

A practical set of signals to watch

• Decisions: Are decisions made once and held, or revisited repeatedly?
• Trust: Do people raise risks early, or only when they have cover?
• Accountability: Is ownership explicit, or assumed and later contested?
• Handoffs: Do cross-functional handoffs move with confidence, or with constant re-clarification?
• Conflict: Is disagreement expressed in the room, or displaced into side chats and escalations?

These signals don’t tell you who’s “the problem.” They tell you what the group has learned is safe and effective. That’s a solvable system.

How to help a team mature without turning it into “soft skills training”

Leaders often hesitate to address team dynamics because it can feel intangible or risky. They worry it will become performative, blame-oriented, or uncomfortable without payoff.

A better approach is to create a structured setting where dynamics become observable without starting with personal critique. When people can see patterns play out in real time—how decisions form, who hesitates, where ambiguity appears—they’re more willing to discuss changes pragmatically.

What tends to work in practice

1. Make dynamics visible (in a contained, facilitated environment).
2. Name the pattern neutrally (avoid “you always / you never”).
3. Translate insights into operating rules (roles, decision rights, handoffs).
4. Commit to small behavioural shifts that can be tested immediately.
5. Review outcomes (speed, clarity, fewer rework loops) rather than intentions.

The goal is not catharsis. It’s operational clarity: faster decisions, cleaner accountability, and fewer cross-functional collisions.

Conclusion: the status quo isn’t neutral—it’s costing you

When teams operate in silos, the cost isn’t just inefficiency. It’s compounding drag: duplicated work, delayed decisions, and the quiet conflict that erodes trust over time.

Group development gives you a non-blaming way to understand what’s happening beneath the surface—and a pathway to change it. You don’t need a culture overhaul to start. You need a clearer shared language for how the team makes decisions, builds trust, and holds commitments.

If you want a structured, low-risk way to surface these dynamics and convert them into practical shifts in roles, handoffs, and execution, explore Reveal team dynamics—without blame or disruption: descriptive text.