The Operating Loop: Keeping Strategy Connected to Execution as You Scale

Companies rarely fail because their people cannot execute. More often, the decisions made at the top are not clearly connected to the work happening at the bottom and signals from delivery do not travel back up quickly enough to change the thinking at the top.

The usual advice is to balance strategy and execution. But balance suggests two opposing forces that need equal attention. Strategy and execution do not need to be balanced. They need to be looped, with strategy informing action and evidence from execution updating strategy.

The strategy-to-execution gap is the loss of alignment that occurs when daily decisions and delivery work no longer support the outcomes leadership intended. Closing it requires a two-way operating loop: strategy guides action, while evidence from execution updates strategy.

This idea appears across the operating practices of Winston Weinberg, co-founder and CEO of Harvey; Bret Taylor, co-founder of Sierra and former co-CEO of Salesforce; and Martin Eriksson's Decision Stack.

The loop breaks in two places, often at once

The first break is strategy drift. Daily actions quietly detach from the longer-term goal. Everyone is busy and progress appears healthy, but the company is moving steadily in the wrong direction. Outputs are delivered; outcomes are not.

Bain & Company reports that executives say they lose 40% of their strategy's potential value to breakdowns in execution. Eriksson describes strategy drift as a gradual loss of connection between intent and action, and explains how to identify and correct it in his guide to spotting and fixing strategy drift.

The second break is delivery failure. The strategy may be sound, but something fails on the path from decision to delivery. Decisions sit unresolved. Blockers do not surface in time. Work gets completed, but quietly drifts from what the strategy required. By the time the risk reaches leadership, the cost of fixing it has multiplied.

Both failure modes have the same cause: the loop only runs one way. Strategy gets pushed down, while what the team discovers along the way has no reliable path back up.

Most organisations have upward reporting through status updates, board decks, and quarterly reviews. But a status report does not necessarily tell you whether what shipped still serves the goal it was meant to serve.

Strategy and execution have more layers than you think

Most teams compress the loop into three levels: vision, quarterly targets and daily tasks. That version breaks because it skips the layers where teams often lose the thread.

Eriksson's canonical Decision Stack contains five connected layers: vision, strategy, objectives, opportunities, and principles. For a scale-up operating cadence, I find it useful to adapt that logic into six practical layers:

1. Vision and mission. Where are we going, and what will be different if we succeed? Everything else should navigate from here and be able to connect back to it.
   
2. Operating principles. How do we make decisions when priorities conflict? These should be practical rules that reduce unnecessary escalation, not values that only live on a wall.
   
3. Strategic themes and objectives. Which outcomes are we committing to? Themes establish broad areas of focus. Objectives define measurable outcomes within them.
   
4. Goals and OKRs. How will teams make time-bound progress against those objectives? An OKR that cannot be traced to a strategic objective may be measuring activity rather than progress.
   
5. Initiatives and projects. Where does delivery happen? Weekly reviews, dependencies, approvals, blockers, and decisions should all be evaluated against the relevant objective.
   
6. Daily execution. What are teams building, testing, and validating today, and what evidence is that work producing?

Winston's operating system, and where it breaks

Winston Weinberg runs much of his personal operating system through a large Google document he calls "The List." It contains motivational anchors, priority trackers, quarterly priorities and a ranked daily list that he revisits throughout the day. In his Knowledge Project interview, he explains that repeatedly re-ranking the document forces him to think about how he is spending his attention.

His quarterly layer is deliberately thin. It commonly includes a key hire, one product priority, and one major area of the company that needs fixing. The point is not to maintain a long list of nominal priorities. It is to keep a small number of active bets accountable every day.

His decision filter reinforces this discipline: understand the company's current goal and its Priority Zero, then ask whether a decision helps it, hurts it, or is irrelevant to it. If it is irrelevant, make a quick call and move on. If it hurts the Priority Zero, the answer is no.

But Winston's system works in part because he personally holds the context. Each time he re-ranks his list, he processes the difference between yesterday and today.

As a company grows, memory and founder proximity stop being reliable operating systems. Strategic intent gets translated across documents, meetings, dashboards, and project tools. Each handoff can lose context.

At twenty people, a founder may be able to hold the Priority Zero in their head and apply it to most important decisions. At a hundred, that approach becomes a bottleneck. The priority needs to be visible in the operating system and the connection from strategy to active projects must be traceable by others.

The goal is not to replace the founder's judgement. It is to create the connective tissue between strategy and delivery so the organisation can act with the same context.

The upward loop most teams skip

Top-down is easy to describe. Strategy flows down: vision shapes goals, and goals direct delivery. The harder direction runs the other way, and it is what separates an operating loop from a planning cascade.

Vision and strategy give daily work direction. Execution produces evidence about whether the strategy is achievable, needs to be refined, or no longer deserves the company's time and attention.

Strong operators move continuously between the two, using what they learn today to sharpen where the company goes next. But that only works when the organisation creates conditions for the signal to travel upward safely and quickly.

Bret Taylor frames the principle directly: "The best strategy is the one that works on the field, not the one you came up ahead of time." Strategy is only as good as the execution that tests and refines it. The field talks back, and the operating loop needs a path for what the field is saying to reach the people setting strategy.

Research reported by Harvard Business Review illustrates the gap. In a study involving more than 500 frontline employees, middle managers, and senior executives across 12 organisations, respondents perceived strategic alignment at 82%. Analysis of their written descriptions found actual alignment of only 23%.

The teams did not know how misaligned they were. People believed they were executing the same strategy while pursuing different and sometimes conflicting priorities. Without a reliable upward loop, those differences can remain hidden behind positive status updates until they appear as delivery problems.

Closing the upward loop requires timely visibility into strategic drift, blockers, approvals, capacity pressure and portfolio risk, while there is still time to change the next decision.

Cadence is what keeps the loop running

Knowing the loop exists is not enough. It requires discipline to maintain cadence when things feel urgent, because that is when teams are most likely to drop the process and start reacting. It is also when drift accelerates fastest.

The cadence should match the layer:

• Review vision and operating principles when something fundamental about the market or company changes.
• Reset strategic objectives properly each quarter, rather than treating the review as a status check.
• Review initiatives weekly against the objectives they serve.
• Ask during daily execution whether the current work still serves the current goal.
  

For a founder, COO, PMO team, or head of delivery, maintaining this cadence is a core operating responsibility. The job is not only to set strategy. It is to keep the live connection between strategy and the work teams are doing this week.

What the operating loop looks like at scale

At scale, founder judgement needs a system that keeps priorities, delivery evidence and decisions connected. Leaders need to see whether active work still serves the intended outcome and spot blockers, approval delays, capacity pressure and portfolio risk before they become expensive.

This is where decision intelligence can strengthen the operating cadence. Pulse OS provides a decision layer across goals, OKRs, projects and delivery. By scoring work before commitment and tracking viability as conditions change, it helps leaders know when to proceed, when to intervene, and when to stop. It supports the operating cadence; it does not replace it.

Put the operating loop into practice each week

Founders can apply these principles without creating a heavy planning process.

At the start of each week:

1. Confirm the most important outcome and the constraint most likely to prevent it.
2. Choose the smallest set of actions that could reduce that constraint, and define the evidence they should produce.
3. Agree what would trigger continuation, intervention, or a stop.
   

At the end of each week:

1. Review the evidence and capture what changed in the team's understanding.
2. Reassess whether active work still supports the intended outcome.
3. Set the next test, and stop or deprioritise work that no longer earns its place.
   

The purpose of the rhythm is not to defend the plan. It is to make the next decision using current evidence.

The strongest vision stays connected to evidence

The founders building some of the fastest growing companies are not necessarily those with the sharpest vision. They are the ones who keep that vision connected to the evidence their teams produce every week.

Taylor argues that the field tests strategy because the field is where assumptions meet reality. Eriksson's framework shows how every layer of an organisation must remain connected to both the "why" above it and the "how" below it.

One thing Winston said has stayed with me: flexible vision-setting is one of the hardest parts of building a company. Founders need to know when to communicate the long-term destination and when to focus the team on what needs to happen today.

That tension is difficult to manage. The discipline is keeping the loop honest and connected in both directions, with strategy guiding delivery and evidence shaping what happens next.

Sources

• Bain & Company, "Five Ways the Best Companies Close the Strategy-Execution Gap"

• Bret Taylor, "How to Sell to Enterprise Companies as an AI Startup," Frameworks for Growth

• Harvard Business Review, "Is Your Company as Strategically Aligned as You Think It Is?"

• Martin Eriksson, "Strategy Drift: How to Spot It, Fix It, and Stop It From Happening"

• Martin Eriksson, "What Is the Decision Stack?"

• Winston Weinberg, "Harvey CEO: How a 31-Year-Old Runs an $11B Company," The Knowledge Project