How to build a product strategy that scales across your whole company

Executive overview

Most product teams work hard but move nothing — teams are shipping constantly while executives see the metrics flat-line. The root cause is almost never poor execution; it's a missing or undeployed strategy that leaves teams without context on what to work toward.

The core insight: strategy failure looks like a training problem but is almost always a goal-setting and communication problem.

The fix is a layered strategy tree — from company vision down through strategic intents, product initiatives, and team-level solutions — written in plain two-pagers and deployed so every team can connect what they're building to a business outcome.

Signs your team has no strategy

• Teams work long hours but no business metrics move
• Executives describe product and tech as a "black box"
• Different people across the org give different answers about what the company's vision is
• Teams can't explain why they're building what they're building
• Executives are fighting over competing goals rather than making calm trade-offs

The missing middle

• The missing middle is the gap between company-level strategic intents and what teams actually build day to day
• Without it, teams spread effort thin across too many initiatives and none move the needle
• Strategy doesn't have to be absent — it often just lives in people's heads and hasn't been written down
• Exercise: interview leaders — ask what "good" looks like, what numbers should move, what the company wants to be in 5–10 years; mismatched answers reveal the gap

How to build and deploy strategy

• Start with a two-pager from the CEO: company origin, current state, external threats, competition, what you will and won't do
• Strategic intents are the 2–3 big business moves for the next 2–3 years (e.g. go upmarket, expand geographically, enter a new market) — prioritise them explicitly
• Directors and VPs write product initiatives: meaty, problem-oriented themes made up of multiple workstreams, each tied to a strategic intent
• Teams write solution options: what they'll actually build to address those problems
• Link all levels in a wiki so anyone can read from tactic up to vision
• Test deployment quality: ask any team what they're working on and why — if they can trace it to a business outcome, it's working

What a good vision looks like

• Concrete enough that people can picture the end state — not a tagline like "be the backbone of healthcare"
• Lofty enough that you can't hit it with a single release; it should guide iteration over years
• Explicitly states how the company is different from competitors, not just that it will "be the best"
• Names what the company will not do — this is as important as what it will pursue
• Combine written narrative with visual mocks or diagrams; designers make vision far more persuasive

When to hire a CPO

• Key trigger: executives say they don't know what product is doing or whether goals are being met
• Structural trigger: moving from single-product to multi-product, entering new markets, or running a major merger
• Headcount signal: roughly 7–8 PMs, or when scope expands beyond product to include design, analytics, or engineering under one leader
• A VP of Product handles one or two products well; a CPO is needed when portfolio complexity requires executive-level navigation, board communication, and revenue projection

What CPOs do that VPs don't

• Translate roadmap to revenue projections for the board and CFO
• Operate as an executive peer across sales, finance, and marketing — not just a functional leader
• Oversee multiple functions (design, product ops, sometimes engineering) under a single strategic leader
• Make hard prioritisation calls across the whole portfolio, not just within one product area

Product operations: making strategy scale

• Product operations solves the breakdown that happens after you've trained teams and deployed strategy but things still don't scale
• Three components:
  1. Internal data and insights — surface financial, usage, and OKR data so leaders can monitor strategy and make decisions
  2. Customer research and user insights — standardise how research is done so teams aren't hitting the same customers repeatedly and interviews are searchable
  3. Process and cadence standardisation — own cross-functional rhythms (roadmap reviews, quarterly planning, sales updates) without dictating how individual teams run their standups
• Prod ops doesn't centralise research; it enables more people to do it safely at scale

Getting better at strategy as a PM

• Mentally rehearse: even without the scope, imagine what you'd do as CPO and why
• Talk to sales about win-loss patterns — they hold market knowledge most PMs never access
• Talk to your CPO about their decision-making process, not just their decisions
• Hire or partner with a data analyst; good strategy starts with answering clear questions with clean data
• Study how specific companies (e.g. Netflix) moved from point A to point B — frameworks matter less than the underlying questions they forced people to answer

How to learn as a PM without burning out

• Focus first on execution — learning from doing outpaces learning from reading
• Identify specific gaps, then do a targeted deep-dive on that topic only
• The core PM loop (talk to users, test, build iteratively, measure) is stable — how you execute each step is where you adapt
• Agile and other processes are tools, not dogma — if a process isn't making you better, change it
• Do a personal retrospective: is this habit, framework, or meeting actually improving your output?