Topic 15 — Product strategy and vision

Goal: Set a direction — vision and strategy — that guides what to build and why.

Lesson 15.1 — Vision: where you're going

In a Monday meeting, Dan wants a referral program because a big customer asked. Priya wants to redesign the slow loading screen. The CEO is still talking about an "AI assistant." Maya, six months into her PM job at Lumi, realizes nobody in the room is asking the same question. Each person is pulling toward a different idea of what Lumi is even for.

That missing thing has a name. A product vision is the inspiring, long-term picture of the world your product is trying to create. Where you're going, and why it matters. Not a feature you ship, not a date you hit. Think of it as the destination on the map, the fixed point every other choice gets to aim at.

A good vision earns its keep three ways. The ambition is what pulls people forward. Keeping it user-centered means it stays about the person you're helping rather than your revenue chart. And because it's durable, it survives longer than a quarter without getting rewritten every time the wind changes.

Without one, a team drifts and builds whatever's loudest in the room. With one, every idea gets a reference point: does this move us toward where we said we're going? For Maya, learning to put that destination into words is how she gets twelve people, including a skeptical engineer and a sales lead with a quota, to row in the same direction for more than a week.

Lesson 15.2 — Strategy: how you'll get there

So Lumi's vision is "make personal finance effortless for everyone." Maya writes it on the whiteboard, feeling good. Then Sam, the senior engineer, leans back and asks the question that deflates the room: "Okay. So what do we build Monday morning?"

He's right to ask. A destination doesn't tell you which road to take. That's the job of product strategy: the high-level choices about which users, which problems, and which approach will win, given that you can't do everything at once. Vision is where. Strategy is how you'll get there.

The heart of strategy is choice. You're deciding what to do, and just as much, what to leave on the table.

Here's the trap Maya almost falls into. The CEO says the strategy is "grow revenue 30% this year." That feels like a plan, but it's a goal, not a strategy. It names a number, not a way to win. Compare it to this: "Become the easiest budgeting tool for small teams by winning on simplicity and onboarding, starting with freelancers." That one names who you're for, how you'll beat everyone else, and where you'll start. A goal tells you the score you want. A strategy tells you the game you're playing to get it.

Lesson 15.3 — A framework for the hard choices

Maya needs a way to turn that fuzzy whiteboard line into real decisions. She doesn't need MBA vocabulary. She needs five questions, a simplified take on the classic "where to play / how to win":

• Who is our target user? (Where will we play?)
• What problem will we own for them?
• How will we win — what's our wedge or advantage? Simplicity? Price? Speed? A unique capability?
• Why us — why can we pull this off when others can't?
• What we won't do — the explicit non-goals that protect our focus.

The magic is in the last question. Answering "what we won't do" is what forces the rest to mean something, because a strategy that says yes to everything has decided nothing.

One idea in there deserves its own name. A wedge is a narrow starting point where you can win decisively, and then expand from. Win one feature for one segment, dominate it, then broaden. A wedge feels too small at first, which is exactly why it works: it's small enough to actually win.

Strategy is as much about what you exclude as what you include.

Lesson 15.4 — From strategy to the actual work

A strategy that lives in a slide deck and never touches a sprint is just nice writing. Maya's real job is to connect the layers so the strategy shapes what gets built on a Tuesday.

The chain looks like this: vision → strategy → goals (the OKRs you'll meet in Topic 16) → roadmap (Topic 6) → the work. Each layer serves the one above it. So when Sam asks Maya "why are we building this onboarding flow?", she can trace it up out loud: this feature serves this quarter's goal, which advances our bet on winning through simplicity, which moves us toward effortless finance. Nothing floats unattached.

That traceability is the line between a strategic PM and a feature-factory PM. The feature factory ships whatever lands on the pile. The strategic PM can point at any item and show the thread running up to the vision.

It quietly solves two other problems too. Prioritizing gets easier, because an idea that doesn't ladder up to the strategy is an easy no. And communicating gets stronger, because Maya can explain any decision in terms of the bigger picture, which is how she keeps Dan, Priya, and the CEO aligned even when she tells one of them no (more on that in Topic 12). The skill underneath all of it is zooming: out to the whole map, in to the next turn, and making sure the two still connect.

Lesson 15.5 — Keeping strategy alive without whiplash

Six months after Maya writes the strategy on the whiteboard, the freelancer segment she bet on starts churning, and a quieter group of new parents keeps renewing. The strategy she was so proud of is being argued with by the data. Good. A strategy is a living hypothesis about how to win, and it's supposed to change as you learn. That's the same Build–Measure–Learn loop from Topic 3, just pointed at your direction instead of a single feature.

But "change as you learn" cuts both ways, and both edges can hurt you.

Picture two versions of Maya. The first sticks to her plan for three years while the evidence quietly screams that it's wrong. Call that stubbornness. The second rewrites the strategy every month chasing the latest customer call, so the team never builds momentum on anything. Call that thrash. Both fail, just at different speeds.

The balance is about cadence. Hold the vision steady. Revisit the strategy on a slow rhythm, maybe yearly, or when the market actually shifts. Let the roadmap flex all the time. A strong PM repeats the strategy until everyone can recite it, watches for the signals that it's time to update, and when she does change it, she explains the why instead of just quietly steering somewhere new. Done well, the strategy is the quiet force that makes a hundred small decisions add up to something big.

Worked example — Turning a vague ambition into a strategy

Back to that whiteboard. "Make personal finance effortless for everyone." Inspiring, and completely unbuildable, because a team can't ship anything for "everyone." Maya runs it through the five questions and watches it sharpen into something her team can act on.

• Who. Young professionals overwhelmed by budgeting. Start here, not "everyone."
• Problem to own. "I don't know where my money goes." That exact sentence, in the user's own words.
• How we win. Radical simplicity and automation, against the complex incumbent apps people open once and abandon.
• Why us. A small, design-led team that can out-simplify a big bank, because we have nothing to protect and they have everything.
• Won't do. Investing and crypto features. Out of focus for now, however loudly anyone asks.

That last line is the wedge: win budgeting for young professionals first, dominate it, then expand. And now the roadmap nearly writes itself. Every candidate either advances "effortless budgeting for this segment" or it gets cut. When Dan brings the crypto request next week, Maya doesn't fall back on "no because I said so." She can say "not yet, because it's not the game we're playing." The vision never moved. The strategy is what made it real.