STRATEGYWeeks to result

Execution-as-Strategy Diagnostic

Most execution problems are strategy problems wearing an execution mask

Problem it solves

execution — missing deadlines

Best for

Teams that are struggling with execution — missing deadlines, building the wrong features, experiencing quality issues — and leaders who keep adding process without improving outcomes

Not ideal for

Teams with genuinely clear strategy that have specific execution capability gaps (e.g., they need a specific technical skill they lack)

Overview

Why this framework exists

When a team struggles with execution — missing deadlines, building wrong features, poor quality — the instinct is to fix execution. Add more process, more check-ins, more accountability, more project management tools. Shreyas Doshi argues that this instinct is usually wrong. Most execution problems are actually strategy problems in disguise. The team is not executing poorly; they are executing the wrong strategy well. Or more precisely, they are executing without a clear strategy at all. The diagnostic questions reveal the truth: Is the team clear on what success looks like? Does everyone agree on the most important problem to solve? Are there conflicting priorities that no one has resolved? Has leadership actually made the hard strategic choices, or are they pushing all options simultaneously? When these questions reveal confusion, the fix is not better execution systems — it is clearer strategic choices. Adding process to a team without strategic clarity is like adding a more powerful engine to a car driving in the wrong direction.

Core principles

4 total
  1. Most execution problems are strategy problems in disguise.
  2. Adding process to a team without strategic clarity is like putting a bigger engine in a car driving the wrong direction.
  3. The fix is not better execution systems — it is clearer strategic choices.
  4. Leadership's job is to make hard choices, not to push all options simultaneously.

Steps

3 steps
  1. Run the Four Diagnostic Questions
    When a team is struggling with execution, before adding any process or accountability, ask these four questions independently to each team member: (1) Is the team clear on what success looks like? (2) Does everyone agree on the most important problem to solve? (3) Are there conflicting priorities that no one has resolved? (4) Has leadership actually made the hard strategic choices, or are they pushing all options simultaneously? If team members give inconsistent answers to any of these questions, you have a strategy problem, not an execution problem.
    Pro tipAsk these questions individually, not in a group setting. In groups, people defer to the most senior person's answer rather than sharing their actual understanding.
    WarningDo not lead witnesses. Ask open-ended versions of these questions and listen for inconsistency across team members.
  2. Identify the Missing Strategic Choice
    If the diagnostic reveals strategic ambiguity, identify the specific hard choice that has not been made. Common unmade choices include: which customer segment to prioritize, which feature to cut to meet the deadline, which metric to optimize when metrics conflict, and which team or project to deprioritize to resource this one. The unmade choice is usually obvious once you look for it — someone has been avoiding it because it is politically difficult or because it means saying no to a stakeholder.
    Pro tipThe unmade choice is usually the one that everyone knows about but no one talks about openly. Look for the elephant in the room.
  3. Escalate or Make the Strategic Choice
    Once the missing strategic choice is identified, either make it yourself if you have the authority, or escalate it to someone who does. Present the choice clearly: here are the options, here are the trade-offs of each, and here is why this choice must be made before execution can improve. Do not frame it as a process problem — frame it as a strategic decision that is blocking the team. Provide your recommendation but make the trade-offs explicit so the decision-maker can make an informed choice.
    Pro tipFrame the escalation as: 'The team needs one strategic decision to unblock their execution. Here are the options and trade-offs. Which direction should we go?'
    WarningBe prepared for the possibility that leadership prefers ambiguity because making the choice means disappointing someone. Your job is to make the cost of ambiguity visible.

Checklist

Saved in your browser

Examples

1 cases
Stripe Teams Misdiagnosed as Execution-Challenged

As Stripe's first PM manager, Shreyas Doshi received frequent escalations about teams with execution problems — missed deadlines, scope creep, and quality issues. In each case, he applied the four diagnostic questions and consistently found that team members had fundamentally different understandings of what success looked like. The teams were executing different strategies simultaneously because no one had made the hard choice about which strategy to pursue.

OutcomeOnce the strategic ambiguity was resolved — by making explicit choices about priorities, customer segments, and success metrics — the execution problems largely disappeared without any changes to process or tooling.
Discussed by Shreyas Doshi on Lenny's Podcast

Common mistakes

2 traps
Adding More Process to Fix a Strategy Problem
When teams miss deadlines or build the wrong things, the reflexive response is to add standups, check-ins, tracking tools, and accountability mechanisms. But if the underlying problem is strategic ambiguity — the team does not know what success looks like — more process just creates more overhead without improving outcomes. Process cannot substitute for clarity.
Blaming the Team for Leadership's Unmade Choices
When leadership avoids making hard strategic choices (which customer to prioritize, which feature to cut), the resulting confusion manifests as execution problems at the team level. Blaming the team for poor execution when the real issue is leadership's avoidance of strategic decisions is both unfair and unproductive.

Origin story

How this framework came to be

Shreyas Doshi identified this pattern repeatedly across his PM career at Google, Twitter, Yahoo, and Stripe. At each company, he observed teams that were labeled as having execution problems when the real issue was strategic ambiguity. At Stripe, when teams came to him as PM manager with execution complaints — missed deadlines, scope creep, quality issues — he developed a standard diagnostic: four questions that reliably revealed whether the problem was genuinely execution or was actually strategy masquerading as execution. In the vast majority of cases, the diagnostic revealed strategy problems. The teams did not need more process; they needed someone to make the hard strategic choices that leadership had been avoiding.

Source

Traced to primary
Source · PODCAST
Shreyas Doshi on Pre-Mortems, the LNO Framework, and Strategy vs. Execution
Shreyas Doshi · 2022
Open source →

Related frameworks

Browse all Strategy →