Manu's Vault

Strategy-vs-Vision

3 min readStatus:Seedling

Strategy vs Vision

Strategy and vision are two distinct organisational tools that serve different purposes, operate on different time horizons, and address different audiences. Conflating them causes both to fail.

Vision

  • What it is: A description of the desired future state — where the organisation is going
  • Time horizon: 3-5+ years
  • Tone: Inspirational and motivational
  • What it does NOT do: Explain how to get there or acknowledge current constraints
  • Audience: The whole organisation, including people who will join years from now
  • Durability: A good vision should not change every year

Example: “Every engineer can deploy to production without waiting for anyone else, in under 5 minutes, at any time.”

Strategy

  • What it is: A description of how to navigate current constraints toward the vision
  • Time horizon: 6-18 months
  • Tone: Analytical and directional
  • What it must do: Take current reality seriously — name constraints, obstacles, and trade-offs
  • Audience: The team responsible for execution and their stakeholders
  • Durability: Should evolve as constraints change
  • Critical requirement: Must state what you will NOT do

Example: “Given our current monolithic deployment pipeline and 47 flaky integration tests, we will focus Q1-Q2 on pipeline decomposition and test reliability before investing in developer tooling.”

How They Relate

  • Vision provides the north star — an unchanging destination
  • Strategy provides the route — the current best path given today’s terrain
  • A strategy without a vision optimises for constraints and loses sight of the destination
  • A vision without a strategy gives no guidance on where to invest effort today

Failure Modes of Conflation

  • “Strategic” aspirations like “we will be world-class” are vision statements masquerading as strategy — they don’t guide decisions
  • Over-tactical visions get stale as circumstances change, requiring constant updates that erode trust
  • Over-aspirational strategies fail to acknowledge real constraints, making them unexecutable

Larson’s Practical Test

If a statement doesn’t tell you what to prioritise when two good ideas conflict, it’s a vision, not a strategy.

This test cuts through ambiguity. A genuine strategy resolves trade-offs; a vision merely points at an aspiration.

Sources

  • Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9.

    • Chapter 5.4: “Strategy and vision”
    • Primary source for the strategy/vision distinction and the practical test

  • Hamel, Gary and C.K. Prahalad (1989). “Strategic Intent.” Harvard Business Review, Vol. 67, No. 3, pp. 63-76.

    • Foundational academic work on aspirational long-term goals vs. near-term competitive positioning; closely related to the vision construct

  • Rumelt, Richard (2011). Good Strategy Bad Strategy: The Difference and Why It Matters. Crown Business. ISBN: 978-0-307-88623-1.

  • Collins, James C. and Jerry I. Porras (1996). “Building Your Company’s Vision.” Harvard Business Review, September-October 1996.

  • Mintzberg, Henry (1987). “The Strategy Concept I: Five Ps for Strategy.” California Management Review, Vol. 30, No. 1, pp. 11-24.

    • Defines strategy as pattern, plan, ploy, position, and perspective — emphasising that real strategy is emergent and constraint-aware, not purely aspirational

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks