Most documents labelled "strategy" are vision statements, roadmap screenshots, or the word "leverage" used four times. Here is how a new PM tells the difference.
You will, within your first three months as a PM, be invited to read something called The Strategy. It will be a PDF. It will have one decorative mountain on the cover. Somewhere inside there will be a line about being the most loved platform in the category, and somewhere else there will be a quarterly roadmap dressed up as a bar chart.
You will nod. Everyone around the table will nod. And then you will spend the next six weeks trying to figure out what, concretely, you are supposed to do differently because of this document. That confusion is not your fault. The document is usually not a strategy. It is the wish list your org produced because saying "we don't have one" is too expensive to say out loud.
This piece is about telling the two apart — because for a new PM, the biggest unlock in the first year is not building faster or shipping more. It is learning to recognise when you are being handed a real decision versus a pretty idea.
Picture a building with six floors. Each floor gives meaning to the one above it. If a floor is missing, everything on top starts to float.
The building fails in a very specific place. Almost every org has the top (mission, vision) and the bottom (goals, roadmap, tasks). The third floor — strategy — is where the lights are off. Nobody lives there. The roadmap, left without a strategy above it, starts reporting directly to the vision, which is a bit like asking a junior PM to report to a philosophical concept.
When people complain that prioritisation is hard, that stakeholders are fighting, that the roadmap feels arbitrary — it is almost always because the third floor is empty.
Here are the symptoms of an org without a real strategy. You will recognise at least three.
That last one is the cleanest tell. A real strategy is largely a list of the things you are refusing to do. If your strategy can't name any of them, it is a vibe, not a strategy.
You can stress-test any strategy doc with three questions. If a document cannot answer all three without hedging, it is not a strategy. It is a collection of intentions, which is different, and usually sadder.
A PM who can answer those three questions about the product they work on is, almost by definition, operating ahead of their title.
Strategy work produces no visible output for weeks at a time. It makes no Jira ticket close. It does not show up in a sprint demo. In orgs that measure productivity in velocity, strategy is the slowest, quietest, most easily-cancelled activity on the calendar.
Which is why, when you see someone actually doing it — slowing down, asking the uncomfortable question, refusing to unblock the roadmap until the direction is clearer — take a note. That is the behaviour that separates a senior PM from a competent ticket-runner, and it is almost never rewarded in real time.
"We need to move faster" is often the polite version of "we refuse to decide what we are doing."
You are new. Nobody will hand you a blank page. What they will do, by accident, is assume you have read and internalised The Strategy. And then ask you to go execute against it.
Here is what to do instead.
Take your team's current roadmap and, for each item, write one sentence answering: which bet is this serving? If you cannot answer for more than half of them, you have just discovered your team's real strategy problem, without having to say it out loud.
There is always one. Usually a senior engineer or designer with three-plus years of memory. Buy them coffee and listen. They will tell you which decisions were actually made, which ones were just announced, and which ones are still unresolved fights.
Every "we'll come back to that," every "let's park it," every "interesting, but later." These are strategy-shaped holes. After eight weeks you will have enough of them to write the memo that nobody else has written — and you will not need to write it; you will need to start asking about the decisions, one at a time, in 1:1s.
On the days where the roadmap feels arbitrary and the stakeholders feel like they are rowing in three directions and your sprint planning feels like it's being held together with hope — the thing that is broken is almost never the roadmap or the stakeholders or the sprint. It is the third floor, where the strategy is supposed to live.
Your leverage as a new PM is not to build that floor yourself. It is to notice that it is missing, and to ask the questions out loud, patiently, in the right rooms, until someone with the authority to pour concrete agrees with you.
Strategy is not a document. It is a set of decisions people would defend to their bonus. If nobody is defending anything, that is the information.
← Back to Product Strategy