Winning Aspiration
Box one of the Strategy Choice Cascade: what does winning look like, for whom, against whom? The key word is winning, and most companies quietly delete it.
An aspiration to participate, to serve, to improve: these are the postures of Playing to Play, and they read as humble while committing you to nothing. Martin's demand is that the aspiration name a victory condition. Not "be a leading provider", which no outcome could ever falsify, but a statement someone could check: for these customers, against these alternatives, winning means this.
The most commonly isolated box
The Winning Aspiration is the cascade box most often answered alone, and answering it alone is precisely how it fails. A company writes an inspiring sentence, mounts it on the wall, and changes nothing. This is the core failure examined in Corporate Purpose: purpose that lacks integration with the other four choices is decoration, and employees can tell. The same failure has a grander cousin, the moonshot that never touches the operating plan, examined in BHAGs through Martin's lens.
Three tests of a useful aspiration
First, it passes the Opposite Test: a sane rival could aim somewhere else. If no competitor could sensibly pursue the reverse of your aspiration, it is not a choice, it is a platitude. Second, it traces downward: you can follow the aspiration through where to play and how to win and see it constraining those answers. Third, it compels trade-offs: something in the company must stop because the aspiration is what it is. An aspiration that has never killed a project is not doing strategic work.
How this connects to OKRs
In our methodology the aspiration matters because autonomous goal-setting depends on it. Teams writing their own OKRs need to know what winning means at company level, or their quarterly bets optimise in every direction at once. When we find an organisation whose team OKRs cannot be traced to a victory condition, the fix is almost never better OKR writing. It is answering box one honestly, then letting the goals inherit the answer.
Our opinion: the aspiration is a narrative, never a number
The most common way we see box one break inside an OKR system is a leadership team that turns the aspiration into a top-line metric and stops there. A winning aspiration belongs in an Objective's narrative, the sentence that says who we intend to beat and for whom; the numbers live below it in aspirational targets that are labelled as stretch so nobody sandbags to protect a bonus. Our position, and it is falsifiable in one reading: if your top Objective could sit unchanged on a competitor's wall, box one is still blank, however impressive the number beneath it.
One line to keep: An aspiration that has never killed a project is decoration; the OKR set that inherits it is strategy.
Our synthesis of Roger Martin’s published work, sources credited. Read the originals: they’re excellent.
Should the winning aspiration be a Key Result? +
No. It belongs in an Objective's narrative, the statement of who you intend to beat and for whom. Turning it into a single top-line number strips out the victory condition and quietly invites sandbagging on the metric beneath it.
How do we know our aspiration is real? +
Three tests: a sane rival could aim elsewhere; you can trace it down through where-to-play and how-to-win; and something in the company has to stop because of it. If it could sit unchanged on a competitor's wall, box one is still blank.
Reading about method is not the same as running it. We install this system and build the capability that stays.
Turn strategy into executed strategy →