Statements vs Systems
Judge systems, not sentences. A generic-sounding strategy backed by compounding machinery is real; a distinctive-sounding claim backed by nothing is an impostor.
Most strategy evaluation stops at the wording, and the wording lies in both directions. "Customer obsession" sounds generic and gets dismissed; "AI-native, category-defining, hyperscale platform" sounds distinctive and gets applauded. Both judgements are wrong, because a strategy is not its sentence. It is the machinery underneath, and the only honest test evaluates the machinery.
Why the sentence lies both ways
Amazon operationalises "customer obsession" into four reinforcing loops, so a generic-sounding claim is backed by a real compound advantage. Meanwhile a rival with a thrilling mission statement and nothing reinforcing it is running an impostor. Read the sentences and you rank them exactly backwards. Read the systems and the truth is obvious. This is why the Opposite Test must be applied to the system, not the slogan.
The test in practice
For any strategic claim, ignore how it reads and ask three things. Can you draw the loop, the specific way today's success makes tomorrow's easier? Is anyone actually resourcing that loop, or just describing it? And would a rival copying the sentence gain anything, or would they need to rebuild the whole system to compete? A claim that survives is a strategy however plain it sounds; a claim that does not is decoration however sharp it sounds.
Why this is ours to name
The move came out of stress-testing conventional strategy rules against more than 500 businesses in our compound advantage research. The recurring finding: evaluators kept mis-scoring strategies because they judged phrasing, and the fix was to judge whether compounding machinery existed beneath the phrase.
One line to keep: judge systems, not sentences. The question is never how the strategy sounds. It is what compounds underneath it.
Two decks. Deck A: "delight customers with quality." Deck B: "become the AI-first leader in our space." A has a drawn loop, reviews fund quality, quality earns reviews, reviews win customers; B has a slogan and no machinery. By wording B wins; by systems A wins, and A is the real strategy.
How do I test whether a strategy is real? +
Ignore the wording and look for the system: can you draw the loop where success compounds, is anyone resourcing it, and would copying the sentence alone gain a rival anything? Real strategies pass however plain they sound.
Does a generic-sounding mission mean weak strategy? +
Not necessarily. "Customer obsession" is generic wording backed, at Amazon, by powerful compounding machinery. Judge the system beneath the phrase, not the phrase.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
Telling a real strategy from a well-worded one is the difference between betting well and betting on adjectives. We pressure-test your strategy for the machinery underneath, then build the OKRs that feed it.