How strategy really works in the Lean Startup framework

Executive overview

Most companies treat strategy as a fixed destination with a known route. The Lean Startup view is different: strategy admits uncertainty and uses experiments to build confidence before committing resources.

The core tool is a strategic rubric — an objective set of criteria that decides what gets into the portfolio, what stays in, and what gets cut. Without it, teams burn out working on too many unrelated things and leaders can't communicate what's actually in or out of bounds.

A good strategy is mostly a list of what you're not going to do.

Strategy operates at three levels

• Business level: which portfolios get resourced and whether returns justify investment
• Portfolio level: which products, services, or use cases advance business goals
• Product level: which features go into the development funnel and why

The rubric: making strategy objective

• A rubric is a transparent, predefined set of criteria — not a personal judgment call
• Teams know in advance what is expected; decisions don't depend on who likes whom
• OKRs are a natural form of rubric: they define the results an initiative must deliver
• When a senior leader requests something out of scope, the rubric lets teams say no without conflict
• Exceptions are allowed, but they must be explicit and deliberate — not default behaviour

What happens without a rubric

• Teams become a mile wide and an inch deep, busy but unproductive
• No shared understanding of what the group is actually for
• Burn-out without meaningful output
• Example: a New Zealand engineering firm's innovation team had no defined scope, so every executive request landed on their plate and nothing meaningful got done

Narrowing focus multiplies returns

• A small set of strategic themes forces real prioritisation under limited bandwidth
• Initiatives within a shared theme learn from each other — cross-team insight compounds
• Breadth feels expansive but destroys throughput; focus feels constraining but accelerates it

Strategy must cover the full journey — including success

• Incubation teams often hand off to execution partners who were never part of the strategy conversation
• If scale-up owners don't see the initiative as aligned to their own strategy, great work lands with a thud
• Strategy must answer: what happens if this succeeds and who catches the ball?

Strategy and governance work together

• Milestones are where teams demonstrate alignment to strategy, not just product progress
• Regular check-ins (not annual reviews) catch misalignment before months of wasted work
• Example: a telecom client uses replicability as a milestone criterion — each gate asks whether evidence of replicability has grown
• Going off-strategy is sometimes right, but only when the team and leadership consciously agree it is

Where to focus: find the uncertainty

• Lean Startup is designed for uncertainty, so direct it at the most uncertain part of the current strategy
• Core business (H1) often carries more uncertainty than it gets credit for — and the cost of getting it wrong is higher
• Caution: using core/adjacent/transformational or H1/H2/H3 as filters can falsely assume core = no uncertainty
• Identify what is genuinely important and genuinely uncertain, then build that into the rubric

Strategy as living questions, not a fixed binder

• Traditional strategy planning takes six-plus months and demands sign-off at every level
• Framing strategy as a set of questions to resolve cuts that effort dramatically
• After one quarter of learning, themes can be parked, pivoted, or replaced without trauma
• Even the strategy itself needs to be evidence-based — the rubric should evolve as you learn