Right to Win
Right to win is a competitive-strategy test: before committing resources to a market or product, ask not only whether you can compete but whether you hold an unfair advantage that is hard to replicate — and whether it is logical that you specifically are the one to build it. Jeetu Patel credits the framing to Aaron Levie at Box and uses it as Cisco’s primary lens for deciding where to expend effort.
Permission to play vs right to win
The distinction is the whole idea, and most companies confuse the two.
- Permission to play — you have the capability to compete: the technology, people, capital, and a route to market. Necessary, but not sufficient. Building an excellent product does not by itself earn mass-scale distribution.
- Right to win — you have a durable, hard-to-replicate advantage and it makes obvious sense that you are the builder. When this holds, the dollars spent on product return outsized results; when it does not, product spend dissipates and the familiar product-versus-sales blame cycle sets in (‘the sales guys can’t sell it’ / ‘the product guys can’t build it’).
Patel’s test: ‘Is it logical for people that we built this, versus another company building it?’ Cisco networking the GPUs is not a far cry — it has connected the world’s infrastructure for forty years. Cisco entering B2C is a far cry — it lacks the distribution DNA, so it has no permission to play, let alone a right to win.
How to apply it
- Treat focus as caloric expenditure: concentrated effort yields disproportionate returns; spread thin, nothing gains enough mass to matter. Patel says no to new-market ideas ‘99% of the time.’
- In an era where AI makes building cheap, the right to win matters more, not less: when code is abundant, the scarce inputs are judgement about which problems to solve and a defensible reason you will win them.
- Pair the test with a route-to-market check. A right to win with no distribution is inert — distribution is the sixth and last of Patel’s company factors (timing › market › team › product › brand › distribution), but ‘just because you build it, they will not come.‘
In the wiki
- 7 Powers — Hamilton Helmer’s taxonomy of durable advantage gives the structural vocabulary (scale economies, switching costs, network effects, etc.) for what a right to win can be made of. Right to win is the upstream go/no-go question; 7 Powers names the moat that answers it.
- Product Positioning — positioning decides how you frame a right you already hold; right to win decides whether to enter at all.
- LLM OS — Patel’s claim that Cisco owns the interconnect layer beneath AI compute is a right-to-win argument pitched at the new computing substrate.
- Jeetu Patel on Cisco, AI at Enterprise Scale, and the Right to Win — source episode; see the deep notes for the full framework.