--- title: "The One-Page Strategy Test: If It Fits, You've Actually Decided Something" description: "A practical structure for writing a product strategy that fits on a single page and forces genuine trade-offs instead of hedged ambition." author: "Kody Everson" url: "https://theipp.org/insights/the-one-page-strategy-test-if-it-fits-you-ve-actually-decided-something" date: "2026-06-25T11:01:17.173Z" --- # The One-Page Strategy Test: If It Fits, You've Actually Decided Something ## Summary A practical structure for writing a product strategy that fits on a single page and forces genuine trade-offs instead of hedged ambition. ## Main content A product strategy that needs more than one page is usually hiding something: a decision nobody wanted to make. The thirty-slide deck, the elaborate Notion workspace, the quarterly strategy offsite that produces a 4,000-word document, these are not signs of rigour. They are signs of avoidance. When everything is in scope, nothing has been chosen, and a strategy that refuses to choose is just a disguised request for more budget. The constraint of a single page is not just an executive preference. It is a forcing function. You cannot fit five competing priorities and a roadmap onto one page without the contradictions becoming visible. ## Why length signals indecision Long strategy documents grow for predictable reasons. Each stakeholder wants their concern in the document, so it expands. Nobody wants to be the person who said no to the engineering platform investment, the enterprise segment, and the consumer growth play simultaneously, so all three survive. The result is a document that satisfies everyone in the room and guides no one outside it. Real strategy is the allocation of scarce resources against an explicit theory of how you will win. The scarcity is the substance. If your strategy does not make some people uncomfortable because their preferred initiative did not make the cut, you have written a wish list. A one-page format makes hedging physically difficult. There is no room for the paragraph that says "while we will primarily focus on X, we will also continue to invest in Y and Z." ## The five components that fit on one page A useful one-page strategy contains five linked elements with each depending on the one before it. ### 1\. Diagnosis: what is actually true right now Richard Rumelt's insistence that strategy begins with diagnosis remains the most ignored advice in the discipline. The diagnosis names the central challenge or opportunity in plain, falsifiable terms. Not "the market is competitive" but instead "three of our top five accounts renewed at reduced seat counts because our activation flow loses 60 percent of invited users in the first week." A good diagnosis is specific enough that someone could disagree with it on the evidence. If your diagnosis cannot be wrong, it is not a diagnosis. This is where discovery work pays off. The diagnosis should rest on evidence you can cite: usage data, win-loss analysis, support themes, cohort retention curves. Reserve roughly a quarter of the page for it. The strength of everything below depends on the honesty here. ### 2\. Goal: one outcome, time-bound and measurable State a single primary outcome you intend to achieve within a defined horizon. The temptation to list a balanced scorecard of objectives is exactly the temptation to resist. A real goal implies sacrifice; if you are optimising for activation rate this year, you are explicitly accepting that average revenue per account may not move, and you should say so. Express the goal as an outcome metric, not an output. "Ship the redesigned onboarding" is not a goal. "Lift week-one activation from 40 to 60 percent" is. ### 3\. Bets: the two or three moves you will actually make Bets are how you intend to close the gap between the diagnosis and the goal. Limit yourself to two or three. Each bet should carry an explicit hypothesis: "We believe that removing the mandatory account linking step will raise activation because support data shows 45 percent of churned trials never connected an account." The word "believe" matters. A bet is a claim about cause and effect that could be falsified. Frame bets this way and you build in accountability, because you can later check whether the believed mechanism actually held. Crucially, bets are not a roadmap. A roadmap is a sequence of features; a bet is a thesis about leverage. The team retains the freedom to discover the right solution within the bet. This preserves the line between strategic decision rights, which belong to the strategy, and solution decision rights, which belong to the empowered team. ### 4\. Anti-goals: what you are explicitly refusing This is the discipline test. Name the things you will not do this period, even though they are reasonable, even though smart people want them. "We will not pursue enterprise SSO requirements this half, despite three active deals requesting it, because our diagnosis says the activation problem is more valuable to solve first." The anti-goals protect the team from the constant gravitational pull of urgent-but-off-strategy requests. ### 5\. Proof: how you will know you were right or wrong For each bet, state the leading indicator that will tell you, early, whether the underlying belief is holding. This converts the strategy from a static declaration into a learning instrument. Define the proof condition in advance so you cannot rationalise a failing bet after the fact. ## Writing it: a sequence that works Start with the diagnosis and the evidence behind it, because that is the hardest and most consequential part. Then draft the goal. Then, before writing any bets, write the anti-goals. Forcing the refusals first is uncomfortable and productive; it reveals what you secretly assumed was still on the table. Only then write the bets, checking that each one plausibly closes the gap the diagnosis identified. Finish with proof conditions. Attach a named owner to each bet. Not a team, a person who is accountable for the outcome and holds the decision rights to pursue it. Diffuse ownership is how bets quietly die. The owner is the person who will stand up in the quarterly review and report whether the outcome was met. Apply an evidence standard to the page. Every claim in the diagnosis should map to a source. Every bet's hypothesis should rest on something more than a feeling. A useful rule: if a sceptical colleague asked "how do you know that?" of any sentence on the page, you should have an answer that is not "it feels true." ## Practical implications for how you operate A one-page strategy changes prioritisation downstream. When a feature request arrives, the test is no longer "is this a good idea" but "which bet does this serve, and if none, why are we doing it." The anti-goals give product managers explicit cover to decline well-intentioned work, which is one of the most valuable things a strategy can provide. It also changes review cadence. Review it quarterly against the proof conditions. Where a bet's leading indicator failed to move, kill the bet or revise the diagnosis. The willingness to retire a failing bet on schedule is the clearest evidence that an organisation treats strategy as a discipline rather than a ritual. Finally, the page becomes the alignment artefact. Because it fits on a screen, executives, engineers, and designers can all hold the same model in their heads. A strategy that cannot be remembered cannot be executed, and a forty-slide deck is not remembered. ## Conclusion The page does not make the decisions for you. It makes the absence of decisions impossible to disguise. If you sit down to fill the five sections and find you cannot name a single primary goal, cannot write three honest anti-goals, or cannot cite evidence for your diagnosis, the page has done its job: it has told you that you do not yet have a strategy, only a set of hopes. That diagnosis, uncomfortable as it is, is worth more than another well-formatted deck. Write the page. Let it force the choices, and then live by what it forced you to decide. ## Related pages - [Insights](https://theipp.org/insights.md) - [Product Profile](https://theipp.org/tools/product-profile.md) - [Standards](https://theipp.org/standards.md)