Given the strategy, can the machine actually execute?

‍Why good strategies still stall inside the business

One of the most expensive myths in growth is that execution failure usually lives inside a single department. Marketing blames positioning. Sales blames lead quality. Product blames the roadmap. Operations blames prioritisation. Leadership blames execution. Each function sees a real symptom, but symptoms are not the same as mechanism. In practice, the real constraint often sits in the interactions between leaders and teams: the ambiguity over who decides, the lack of clarity about what matters most, the duplication that appears when functions optimise locally, and the trust erosion that follows when results are slower than promised. McKinsey describes organisational health as the way leaders run the place, especially how they make decisions, allocate resources, execute strategy, and renew the organisation over time. That is exactly the territory this framework is designed to expose.

By the time the problem becomes visible in revenue, margin, pipeline velocity, launch quality, or customer confidence, it has usually already travelled through the system. Deloitte’s work on decision rights shows that ambiguity over who decides slows response time and can let decisions fall through the cracks. McKinsey’s survey work shows that organisations that make fast, high-quality decisions also tend to see better financial returns. Gallup’s engagement research shows that clear expectations materially affect productivity, turnover, and safety outcomes. Put simply, strategy does not fail at the whiteboard first. It fails in the mechanics of interpretation, authority, coordination, and follow-through.

The inside-out mechanics of execution

The Alignment Flywheel is not a scorecard and it is not a checklist. It is a way of seeing the organisation as a living system of force and friction. HubSpot popularised the flywheel in business strategy because it captures a simple truth: momentum grows when force is applied consistently and friction is reduced. In that model, poor internal processes, weak communication between teams, and misalignment create drag. Inside a leadership team, the same physics apply. When alignment produces clarity, clarity improves decisions, decisions strengthen execution, execution creates results, and results build trust, the next cycle starts from a stronger position than the last. When any one of those stages weakens, the whole organisation pays for it.

The best way to visualise the flywheel is as a circular operating system, not a ladder and not a funnel. Read clockwise. Alignment creates a common direction. Clarity turns that direction into clear expectations, role definitions, and priorities. Decisions translate clarity into choices with real owners and real speed. Execution coordinates activity across functions and handoffs. Results provide evidence that the system is converting energy into value. Trust gives people the confidence to commit, challenge, delegate, and move faster in the next cycle. That trust then strengthens the next round of alignment. This mirrors what CCL describes in its Direction, Alignment, Commitment model: leadership is not just the behaviour of one individual, but a social process produced through interactions, responsibilities, and shared work across the whole system.

Large visual description for the page designer:
Design the Flywheel as a circular system with six equal outer segments arranged clockwise: Alignment, Clarity, Decisions, Execution, Results, Trust. Place a smaller centre hub labelled Operating cadence or Leadership operating logic. Use curved arrows to show continuous motion. Add subtle friction markers between Clarity and Decisions, Decisions and Execution, and Results and Trust, because these are the points where organisations often lose force through ambiguity, delay, rework, disappointment, or re-litigation. The visual should feel mechanical and executive, not playful. It should communicate that this is how the business actually moves. The stronger the internal logic, the faster the wheel spins. The more friction accumulates, the more force gets wasted. That is the central idea.

Alignment as force distribution

Alignment is the point where force first enters the system. It is not bland agreement and it is not groupthink. It is a shared understanding of what the organisation is trying to achieve together, what matters most now, what trade-offs are acceptable, and how each function contributes to the whole. CCL’s work is useful here because it treats alignment as a collective outcome of leadership, not as a personal virtue of the CEO alone. In groups with strong alignment, work is coordinated in service of shared direction. In groups with weak alignment, people feel pulled in competing directions and start working at cross-purposes. For CEOs and MDs, this matters because local optimisation looks productive until it starts cancelling itself out.

A leadership team can look calm and still be misaligned. Everyone nods in the meeting. Everyone leaves with a different interpretation of priority, timing, and acceptable risk. Product assumes the roadmap is leading. Sales assumes customer pressure will overrule the roadmap. Marketing assumes the offer is clearer than the market thinks. Operations assumes the commercial team will adapt around capacity. In that kind of system, the organisation is not missing commitment. It is missing shared operating logic. That is where the flywheel begins.

Clarity as signal quality

Clarity is what stops direction from dissolving into interpretation. Google’s Project Aristotle found that structure and clarity, clear roles, goals, and plans, were among the strongest dynamics of effective teams. Gallup goes even further and describes clear expectations as the most basic and fundamental employee need. In other words, clarity is not a communication nice-to-have. It is operational infrastructure. Without it, teams burn energy decoding intent, second-guessing authority, and translating strategy for one another in every meeting.

In Flywheel terms, clarity is signal fidelity. It tells people what matters, how to judge trade-offs, what “good” looks like, and where their work fits. Gallup reports that employees who strongly agree that their work aligns with what is expected of them are more likely to be engaged, and that organisations that expand this clarity can improve productivity while reducing turnover and safety incidents. For leadership teams, the commercial implication is simple: if the business has to be re-explained every week, the machine is already slipping force.

Decisions as throughput and authority

Decisions are where strategy either gains velocity or starts queueing. McKinsey’s survey research shows that only a small minority of organisations feel they truly excel at decision making, and that the organisations that do tend to make decisions that are both faster and higher quality, not one at the expense of the other. BCG notes that when decision rights are unclear or contested, leaders spend time navigating who actually has authority, which delays action and weakens confidence in the decision that finally emerges. Deloitte reaches the same conclusion and ties stronger decision-rights maturity to better business outcomes.

This matters because many businesses still treat decisions as a cultural issue instead of a design issue. But decision rights are design. Deloitte defines them in practical terms: who decides, what decisions matter most, and how those decisions are supported by forums, procedures, evidence, and accountability. If that architecture is murky, the organisation compensates through escalation, politics, side conversations, and invisible vetoes. If it is clear, people move with more confidence and less coordination cost. The Flywheel therefore treats decisions as a load-bearing mechanic, not as a meeting habit.

Execution as coordinated motion

Execution is where interdependence becomes real. Google’s team research emphasises that true teams are highly interdependent: they plan work, solve problems, make decisions, and review progress together. McKinsey’s work on cross-functional collaboration then shows what happens when this interdependence is poorly managed: customer interactions become sluggish, communication lines get blocked, and end-to-end performance weakens even when individual functions look competent in isolation. In Flywheel terms, execution is not activity volume. It is coordinated motion across dependencies.

This is where many leadership teams misread the situation. They see visible effort, full roadmaps, active campaigns, and busy sales teams, and assume the organisation is executing. But execution is only strong when the handoffs work. If sales overpromises, customer success inherits debt. If product shifts priorities without commercial translation, marketing generates noise. If marketing launches without operational readiness, revenue quality declines. If leadership sets new priorities before the previous ones have landed, the business accumulates rework instead of momentum. Execution is the point where the machine proves whether the functions truly reinforce one another.

Results as feedback and proof

Results are not just scorecards for the board pack. They are the feedback mechanism that tells the organisation whether the flywheel is converting force into value or merely consuming effort. McKinsey’s organisational-health research links healthier organisations with stronger long-term shareholder returns, greater resilience, higher EBITDA improvement in some cases, and fewer safety incidents. Their decision-making research also shows that decision-making winners report stronger returns from their recent decisions. The message for CEOs is clear: results do not only validate the strategy, they validate the operating mechanics behind it.

This is why results need to be visible, interpretable, and shared. If outcomes are vague, every function writes its own story about why progress is slower than expected. If outcomes are explicit, the conversation becomes more honest. The team can ask whether the issue is market reality, weak positioning, poor decision design, execution friction, or simple over-complexity. Results close the loop between intent and reality. Without that loop, the organisation drifts back into opinion.

Trust as load-bearing confidence

Trust is the mechanic that keeps the next cycle from collapsing under politics, defensiveness, or repetitive debate. Gallup shows that employees who trust their leaders are far more engaged and more likely to stay, while Google’s Project Aristotle identifies psychological safety as the strongest dynamic of effective teams. That combination matters because high-performing leadership teams need more than alignment on paper. They need the confidence to raise hard issues, admit uncertainty, ask for help, challenge assumptions, and delegate without constant rescue.

Trust is often mislabelled as a soft issue. It is not. It is an operating condition. Gallup explicitly ties trust to transparency, accountability, and leadership behaviours that promote open dialogue. Google’s findings similarly show that dependable work, structure and clarity, and psychological safety sit close together. When trust is weak, people protect themselves. Information travels selectively. Escalation happens late. Agreement becomes performative. In the Flywheel, trust is what allows the next cycle of alignment to begin from confidence rather than fatigue.

Where the flywheel breaks

The Hero Leader

‍This pattern appears when one senior leader becomes the primary engine of movement. Delegated decisions boomerang back to them. Their calendar becomes the approval system. Their judgment becomes the organisation’s substitute for decision design. McKinsey describes this failure mode clearly: leaders attempt more delegation, only to see decisions return upward, committees multiply, and more operational noise consume strategic time. Your own site language already points the other way, arguing that aligned systems should reduce dependence on individual heroics. That is exactly why the Hero Leader is a failure pattern, not a success pattern.

The Consensus Trap

‍This pattern appears when inclusion gradually becomes indecision. McKinsey’s critique of RACI is useful here: too many stakeholders end up with votes or vetoes, there is no clean decider, and the effort to involve everyone creates bureaucracy that degrades decision quality. Google’s own team research also found that consensus-driven decision making was not one of the key variables linked with team effectiveness. Healthy teams need input and challenge, but they still need a decision architecture. Otherwise, the machine spins in circles without committing torque.

The Functional Silo

‍This is the classic case of local excellence and systemic drag. McKinsey notes that silos make customer interactions sluggish, block communication, and make it harder to manage operations end to end. In practice, this looks like teams hitting their own targets while the customer experiences confusion, delay, inconsistency, or duplicated effort. The problem is rarely lack of capability. It is that the organisation has not designed the handoffs as carefully as it designed the functions.

The Escalation Loop

‍This is what happens when unclear decision rights and poor delegation feed one another. A team feels uncertain, so it seeks more approval. The senior leader becomes overloaded, so response times slow. Committees are formed to solve the bottleneck, which creates more ambiguity, not less. McKinsey’s work on delegation and RACI shows exactly how these loops form. In a flywheel, escalation is sometimes necessary. An escalation loop is different. It means the organisation has stopped trusting its own operating logic.

Reorganisation Addiction

‍Reorgs are often proposed as if structure itself will create performance. Bain’s research on 57 reorganisations is more sobering: most had no effect, and some destroyed value. McKinsey adds that reorganisations frequently create fear, uncertainty, distraction, and rumour when poorly handled. The deeper problem is that many leaders hope structure will solve what decision design, accountability, trust, or cross-functional mechanics have not solved. Reorganisation can be useful. But if each slowdown produces a new shape before the organisation has fixed its bottlenecks, the flywheel never gets a chance to build momentum.

Three Patterns I See Repeatedly

The following vignettes are composite illustrations built from recurring organisational patterns. They are designed to show how the Flywheel works in practice without making unverifiable claims about a specific client.

The scale-up with a strong product and weak throughput
The CEO of a software business believed the company had a messaging problem. Pipeline looked uneven, launches kept slipping, and sales argued that the roadmap was not keeping pace with customer reality. After a closer inspection, the strategy itself was not the issue. The real bottleneck sat in the decision layer. Product was waiting for more evidence, sales was selling ahead of product certainty, and marketing was trying to bridge the gap by producing more content. Once the leadership team clarified which decisions belonged where, tightened the operating cadence, and stopped treating escalation as normal, execution sped up and campaign quality improved.

The business unit that kept re-opening settled questions
A managing director inherited a business unit with decent market position and capable people, but every significant initiative seemed to restart halfway through. Regional teams wanted flexibility, group leadership wanted control, and commercial leaders had learned that the safest move was to wait for someone more senior to go first. The issue was not poor intent. It was weak trust and low role clarity after repeated change. A focused reset on decision rights, leadership handoffs, and collective priorities did more to restore momentum than another structural redesign would have done.

The company that did not need a bigger strategy deck
A founder-led industrial business had already done the strategy work. The market thesis was solid. Customer feedback was not the problem. Yet the organisation still felt slower every quarter. Marketing said sales ignored the message. Sales said product complexity made the message impossible. Leadership kept stepping in to resolve tensions case by case. The breakthrough came when the team stopped diagnosing itself function by function and started looking at the mechanics of the whole machine. Once the hidden dependencies were brought into the open, the discussion moved from blame to throughput.

What sits behind the flywheel

The Flywheel should not give away a rigid nine-step recipe. It should show that there is a serious operating system behind the framework without pretending every assignment follows the same route. The current Clarity Engine page already gives you the right public architecture for this. It presents three visible phases, Diagnose, Align, and Activate, and it explicitly says that many engagements begin with a short diagnostic and then adapt to the outcome rather than locking the client into a fixed commitment.

That is exactly the right bridge here. Under the surface sits a flexible toolbox. Some organisations need deeper customer or commercial evidence before they can act. Some need sharper decision rights. Some need value proposition work, content planning, sales enablement, or role clarification. Some need a half-day offsite because the issue is less about information and more about candour, trust, and collective ownership. The objective is not to force every client through the same sequence. The objective is to identify the real bottleneck, choose the right intervention, and reconnect strategy with execution in a way that can actually compound.

Suggested bridge copy to the Clarity Engine:
The Alignment Flywheel explains why momentum builds in some organisations and leaks away in others. The Clarity Engine is how that diagnosis turns into action. It starts by finding where the system breaks, then helps leadership teams restore shared direction, clarify the critical decisions, and turn that clarity into practical execution. Some organisations need market evidence. Some need sharper ownership. Some need a more forceful go-to-market. The method adapts to the bottleneck. The goal stays the same: build a machine that can move.

Diagnose the bottlenecks

The call to action on this page should be direct and diagnostic. The current Matrix assessment already uses the right philosophy: the purpose is not to produce a decorative score but to create clarity about where growth is constrained. The Clarity Engine page uses similar language, promising a written audit of where the growth system breaks and a prioritised action list. Reuse that logic here, but narrow it to internal mechanics. The assessment should help leaders see where decisions slow down, where roles overlap, where handoffs fail, where heroics are substituting for systems, and where trust is too weak to support speed.

Suggested CTA copy:
If strategy is sound but execution still feels harder than it should, the issue may not be effort. It may be the machine. Diagnose the bottlenecks, identify where your flywheel is losing force, and decide what to fix first.

Primary CTA button: Diagnose your bottlenecks
Secondary CTA button: Book a clarity call

‍