The most expensive gap in a scaling SaaS company is not between product and engineering. It's between product and strategy. Product teams build features from specs, roadmaps, and customer asks. Strategy teams write positioning briefs that live in Google Drive, get read once at launch, and rot in the background as the product evolves. Six months later, the product ships capabilities that don't match the positioning, and the positioning claims capabilities the product hasn't built. Neither team is at fault; the gap is structural.
The fix is not to make product managers read the positioning brief more often. It's to move strategic context out of the brief and into the places PMs are already working.
Why the brief-as-reference-doc fails
The positioning brief is a written artifact. PMs operate from tickets, dashboards, and meeting notes. The friction of opening the brief, re-reading the relevant section, and applying it to the current decision is higher than the friction of just making the decision with whatever context is in the PM's head. The brief loses, every time.
This is not a diligence problem. A PM making twenty decisions a day cannot pause to re-read a six-page document for each one. The expectation that they do is a misunderstanding of how product decisions actually get made — they get made quickly, in context, with the information that's immediately available. A positioning brief that requires a PM to seek it out is a positioning brief the PM will stop using within two months.
The three places strategic context has to live
For strategic context to actually inform product decisions, it has to be present in three specific artifacts PMs already produce. Adding it anywhere else is optional; leaving it out of these three is the source of the strategy-product gap.
1 · The one-pager that justifies the feature
Most PMs write a one-pager (or equivalent spec document) for any feature above a certain scope. The one-pager usually contains the customer problem, the proposed solution, and the rollout plan. It almost never contains a line connecting the feature to the positioning — which is the moment strategic context should enter the PM's decision-making.
A useful addition: a single section called "Positioning fit," two or three sentences. "This feature supports our Layer 4 differentiator — in-house build is a real alternative, and this feature increases the cost of that alternative by removing the workflow-customization reason customers cite for building internally." The PM who writes this sentence has now thought about the feature's positioning implications; the PM who doesn't hasn't.
2 · The roadmap-review deck
The quarterly roadmap review is the venue where product leadership and executive leadership align on what's shipping. Most roadmap decks organize features by quarter or by team; few organize them by the positioning claim they support. The reorganization — even as a secondary view — forces the conversation about whether the roadmap is shipping the positioning, or whether the positioning is claiming what the roadmap isn't building.
The mechanic: for each major feature on the roadmap, add a tag indicating which of the company's top three differentiators the feature supports. Features that don't support any of the three get flagged for explicit discussion. The flag is not a veto — it's a forcing function for the "why are we building this" conversation.
3 · The customer-research notes
PMs talking to customers capture notes that shape the roadmap. Those notes almost never reference the positioning — they reference pain points and feature requests. A small addition: after each customer conversation, the PM writes one sentence on what the conversation revealed about the positioning. "The customer does not use our category noun to describe us; they say [other noun]. Third time this quarter."
This one sentence, aggregated across 20 customer conversations a quarter, becomes the fastest positioning-drift detector a company has. The messaging team reviews the sentences at the end of each quarter and notes the patterns. The feedback loop from "customer said X" to "positioning should reflect Y" tightens from six months to six weeks.
We added one line to our customer-interview template — 'what did this conversation reveal about our positioning' — and caught a category-noun drift six months before marketing did. Marketing wasn't talking to customers; product was. The positioning intel was there, it just wasn't being aggregated.
What product teams should not own
The fix is not to make product managers own positioning. That is a strategy team's job, and the division of labor matters. Product manages the specific, the concrete, the shippable. Strategy manages the enduring, the comparative, the positional. Collapsing the two produces a company where product managers write marketing copy and marketing teams argue about APIs, which is the worst of both.
What product teams should own: the embedded-context work inside their own artifacts. Adding a "positioning fit" line to the one-pager. Tagging features against differentiators on the roadmap. Capturing positioning signals in customer research notes. None of these require product managers to become PMMs. They require product managers to hold the existing positioning in their head while making product decisions — and the three embedded-context additions are the infrastructure that makes that possible.
The alternative is the gap everyone has been pretending doesn't exist. Product ships features that don't land positioning-wise. Marketing writes positioning that the product doesn't quite deliver on. The sales team is left to reconcile the two in the moment of the customer call. Fixing this is not a Marketing-and-Strategy problem; it's a problem of making the positioning live where product work already happens. The three additions above do that without asking either team to become the other.
Strategic Context
Your pillars, decisions, audit snapshots, and notes — the foundation the Analyst reads from.
See how it worksOne sharp positioning read, most Thursdays.
Field-tested frameworks, teardowns, and pattern notes from our working library. No "Top 10" lists. No launch roundups. Unsubscribe whenever.
Keep reading
Strategic Context: Why Most Strategy Docs Become Graveyards
Strategy work fails to compound because the artifact isn't where the work lives. The shape of strategic context that actually survives — and the three practices that keep it alive.
The Strategic Context Manifesto: Memory as a Moat
The strongest moat a modern company can build is the accumulated memory of its strategic reasoning, made legible and reusable. A long read on why — and how.
Strategic Context: The First 30 Days of Memory
A strategic-context system is worth nothing empty and worth everything full — but the first 30 days is where most founders give up. Here's what to log, when, and the five-minute daily ritual that makes the system durable.