Most product teams I’ve worked with believe they have a strategy. They can talk about it in meetings, reference it in planning sessions, and nod along when leadership mentions it. But when I ask a simple question, “Can you show it to me?”, the room gets quiet. That silence tells me more about the state of a product organization than any roadmap ever could.
The Strategy That Doesn’t Exist
Here’s something I’ve learned after years of building products in the SaaS industry: if your strategy isn’t written down, you don’t have a strategy. You have a vibe.
That sounds harsh, but it’s precise. An unwritten strategy is a shared hallucination. Everyone thinks they’re aligned until the first real trade-off arrives. Then you discover that the CEO’s version of the strategy, the VP of Product’s version, and the engineering lead’s version are three different stories that happen to share a few keywords.
I’ve seen this pattern repeat across organizations of every size. The symptoms are always the same. Prioritization debates that never resolve. Stakeholders who keep reopening decisions that were supposedly settled. Teams building features that are technically competent but strategically incoherent. The root cause isn’t bad judgment or poor communication skills. It’s that there’s nothing to point to. No written artifact that says: this is what we’re doing, this is why, and this is what we’re choosing not to do.
Why PMs Avoid Writing It Down
The obvious explanation is that people are busy. Strategy documentation feels like overhead, one more artifact to maintain in a world already drowning in Confluence pages nobody reads.
But that’s not the real reason.
The real reason is that writing forces clarity, and clarity is uncomfortable. When you write a strategy down, you have to commit. You have to say what you actually believe about your market, your customer, and your competitive position. You have to name the bets you’re making and, more painfully, the bets you’re not making. You have to be specific enough that someone could disagree with you.
Most product organizations aren’t allergic to documentation. They’re allergic to commitment.
An unwritten strategy gives you room to shift, reinterpret, and claim alignment after the fact. A written strategy holds you accountable. That’s exactly why it’s valuable, and exactly why it meets resistance. I’d go further: the degree of resistance you feel when trying to write your strategy down is a reliable signal of how much unresolved disagreement your organization is carrying. If it’s easy to write, your team is more aligned than most. If it feels impossible, you’ve just learned something important.
What Written Strategy Actually Does
A written strategy isn’t a plan. It’s not a roadmap, a vision statement, or a list of OKRs. It’s a clear articulation of the choices you’ve made and the logic behind them. When it’s done well, it does three things that no verbal agreement can replicate.
It creates a shared reference point. When a new opportunity lands on the table, a written strategy gives the team something to evaluate it against. Not “what does the CEO think?” or “what did we say in that meeting last month?” but “does this fit the strategy we committed to?” That shifts conversations from opinion to analysis.
It surfaces disagreement early. When strategy lives in people’s heads, disagreements stay hidden until they become expensive. Someone reads the written strategy and says, “Wait, I thought we were going after enterprise customers, not mid-market.” That moment of friction is a gift. It’s far cheaper to resolve a strategic disagreement in a document review than in a failed product launch.
It makes delegation real. This is the benefit most product leaders underestimate. A senior PM or product leader can’t be in every room where decisions get made. A written strategy acts as a proxy for your judgment. It lets teams make good decisions without waiting for permission, because they can see the boundaries and the intent behind them. Without that written artifact, delegation breaks down in a predictable way: teams either wait for approval on everything (which kills speed) or they make their best guess (which produces strategically incoherent work). The teams I’ve seen operate with the most autonomy and the most coherence are always the ones that have a written strategy they can reference in real time. That document doesn’t replace judgment. It gives judgment a frame. [A specific example from the author’s experience, describing a time a team made a strong autonomous decision because a written strategy was in place, would make this point land harder.]
The “Show Me” Test
Here’s a simple diagnostic: Go ask three people on a product team, separately, to describe the product strategy. Not the vision, not the mission, not the goals for this quarter. The strategy. The choices, the trade-offs, the “why this and not that.”
If all three give you roughly the same answer, and they can point me to a document that captures it, the team has a strategy. If they give you three different answers, or if they all say something vague like “we’re focused on growth” or “we’re building the best platform,” the team doesn’t have a strategy. They have a direction at best, and an assumption at worst.
What makes this test revealing isn’t the question. It’s what happens in the silence before people answer. That pause, where someone searches for language they’ve never actually had to produce, tells you whether strategy is an operating tool or a comfortable fiction in your organization. I’ve never run this test and been wrong about the result.
I encourage you to try it this week. Don’t warn people in advance. The uncoached version is the honest one.
What Good Looks Like
A written strategy doesn’t need to be long. Some of the best ones I’ve seen are two to three pages. What it needs is specificity. Here’s a structure I’ve pressure-tested across multiple product organizations:
- Context. What’s true about your market, your customers, and your position right now? Not aspirations. Facts. If your context section reads like a pitch deck, you’ve already gone wrong.
- Diagnosis. What’s the core challenge or opportunity you’re choosing to address? This is where most strategies fall apart. They skip the diagnosis and jump straight to solutions. A team that can’t clearly name the problem it’s solving will build confidently in the wrong direction.
- Guiding approach. What’s your overall method for addressing that challenge? This is the heart of strategy: the set of choices that guide everything else. It should be specific enough to rule things out. If your guiding approach is compatible with every possible initiative, it isn’t guiding anything.
- Coherent actions. What specific moves follow from that approach? These should reinforce each other, not just be a list of unrelated initiatives.
You’ll notice this structure forces you to do something most strategy documents avoid: make a diagnosis before you prescribe solutions. In my experience, the diagnosis is the hardest part to write and the most valuable. It’s where you have to say, out loud, “this is the real problem.” Not the polite version. Not the version that makes every stakeholder comfortable. The real one.
Don’t confuse this with vision docs, roadmaps, or goal frameworks. Those are outputs that a strategy should inform. They’re not the strategy itself.
The Hidden Tax
Every unwritten strategy carries a cost that doesn’t show up on any dashboard. It shows up in the time spent re-litigating priorities. In the features that get built because someone assumed they were strategic. In the talented PMs who leave because they can’t figure out what the organization actually cares about.
That last one deserves emphasis. The best product people I’ve worked with can tolerate ambiguity, but they can’t tolerate the absence of intent. When a strong PM starts asking “what are we actually trying to do here?” and gets a different answer from every leader they talk to, they don’t file a complaint. They update their LinkedIn. The cost of an unwritten strategy isn’t just inefficiency. It’s the quiet departure of the people you can least afford to lose.
You can’t measure this tax directly, which is part of why it persists. But if you’ve worked in product long enough, you’ve felt it. That nagging sense that the team is busy but not making progress. That the roadmap is full but the strategy is empty.
Start Here
If you don’t have a written strategy today, don’t try to produce a perfect document by Friday. Start with one page. Answer three questions: What are we choosing to focus on? What are we choosing not to do? Why?
Share it with your team. See if they agree. See where they push back. That pushback isn’t a problem. It’s the whole point.
A strategy that lives only in your head feels safe because nobody can challenge it. A strategy that lives on paper feels risky because everyone can. That’s not a weakness. That’s the mechanism that makes it real.