The New PM's Ninety-Day Strategy Audit
How to quietly figure out whether your team's strategy is real, without accusing anyone, torching your relationships, or getting exiled to the backlog grooming room.
You are a new PM. You suspect — based on two weeks of meetings where people said "let's align on strategy" without ever aligning on anything — that your team may be operating without a real one. You are almost certainly correct. What you should not do is say so.
What you should do is conduct a ninety-day private investigation. Not the paranoid kind. The curious kind. By day ninety-one, you will know more about how your team actually sets direction than anyone who has been there less than three years. That is leverage a new PM is not supposed to have, which is why almost nobody does this.
Here is the playbook.
What to do
- Book a 30-minute coffee with every person on your team, plus three cross-functional partners (design lead, engineering lead, go-to-market counterpart).
- Ask two questions, and shut up: "What does this team do best?" and "What do you think our strategy is, in your words?"
- Write the answers down verbatim afterward. Do not synthesise yet.
- Read every strategy-adjacent document you can find — strategy decks, OKR docs, all-hands recordings, founder memos. Timestamp them. Old documents often reveal more than recent ones.
What you're looking for
Contradictions. One person says the strategy is "expand into enterprise." Another says it's "win the SMB share we're losing." Both are told this is the strategy. Neither knows the other person has a different version. That is a gold seam. You do not mine it yet — you just note where it is.
What to do
- Pull the last two quarters of roadmap items. For each, write one sentence: which bet does this serve? If you can't, that's data.
- Ask your engineering lead where the team's capacity actually went. Not what was planned — what happened. The delta between those two is the real operating story.
- Find out which requests got escalated, fast-tracked, or quietly deprioritised in the last ninety days. These decisions are where the strategy actually lives. A strategy doc says what you believe. Escalations say what you do.
- Look at hiring. The two or three roles the team is currently recruiting for reveal the next 18 months of strategy more honestly than any document will.
What you're looking for
The gap between the declared strategy (what the deck says) and the revealed strategy (where people and money actually go). This gap is never zero. If it's under 20%, your team is healthier than most. If it's over 50%, the declared strategy is ceremony and the real strategy is a running negotiation nobody has written down.
What to do
- Identify the one contradiction or gap from phases one and two that (a) matters to outcomes, (b) you have evidence for, and (c) you can raise as a question, not a verdict.
- Bring it up in a 1:1 with your manager first, not in a group meeting. Frame it as curiosity. "I'm trying to make sense of why our capacity last quarter went to X, while the strategy foregrounds Y. What am I missing?" Two outcomes: either you learn something you didn't know (which means the strategy was more coherent than you thought), or your manager confirms the gap and is now thinking about it with you.
- If the gap is real and your manager agrees, ask: "Who would be the right person for me to raise this with, or to help you raise it?" You are not trying to be the hero. You are trying to be useful to the person who can actually fix it.
- Document your understanding of the strategy in a doc for your own use. Not to share. Share it with your manager if asked.
What you're looking for
One useful intervention. Not a rewrite. You are a new PM. Your goal at day ninety is not to have authored the new strategy. It is to have become one of the small number of people who genuinely understand the current one, its gaps, and its politics.
The mistakes to avoid
- Don't audit out loud. The second you frame this as "I'm evaluating our strategy," every conversation becomes performative. Do the work privately. Share conclusions, not the audit.
- Don't write a long memo at day ninety. Nobody wants a takedown from the new PM. Everyone wants a good question from the new PM. Questions travel. Memos get archived.
- Don't assume malice. Fake strategy is almost never a leadership failure. It is usually a bandwidth failure — the real strategy is in someone's head, and they haven't had time to write it down in a way that survives contact with fifty other people. Your job is to help surface it, not to publish it.
- Don't skip phase two. The temptation is to jump from reading the strategy doc to raising questions. The whole game, though, is the delta between the document and the operating reality. Without phase two, you're just debating decks.
The real point
The ninety-day audit is not about finding out whether the strategy is good or bad. It is about developing the habit of paying serious attention to strategy as a living system — who believes what, where the money goes, which decisions got made, which ones are still pending, what the trade-offs were, who paid the price of them.
That habit — cultivated early, cultivated quietly — is what separates the PMs who become senior PMs in two years from the PMs who spend six years being pretty good at shipping features.
The most senior thing a new PM can do is notice what the org isn't saying — and figure out, patiently, whether that silence is deliberate, accidental, or covering for something nobody has had the time to fix.
Your strategy career does not start when someone hands you the pen. It starts when you realise that most people around you are operating from guesses — and that some of those guesses are catastrophically different from each other — and that the fastest way to become useful is to be the person who, quietly, knows which guesses are which.
← Back to Product Strategy