There is a useful test for whether you have a real strategy: ask yourself what you're explicitly not doing.
If the answer is "nothing — we're doing everything," you don't have a strategy. You have a list.
A strategy that tries to do everything is a strategy that does nothing. It gives equal weight to all initiatives, equal urgency to all goals, equal attention to all markets. It provides no guidance when two priorities conflict — and they always conflict.
The tradeoff is the strategy
Every real strategy is, at its core, a set of explicit tradeoffs. Richard Rumelt's definition is the clearest: a good strategy is a coherent set of analyses, policies, and actions designed to achieve a specific goal. The key word is coherent — which means it excludes as much as it includes.
Amazon's "obsess over customers" isn't a strategy until it answers: what do we do when a customer request conflicts with short-term revenue? What types of customer requests do we invest in versus ignore? Where do we draw the line between "customer-centric" and "trying to be everything to everyone"?
The tradeoff is the strategy. The moment you say "we're going to do X by not doing Y" is the moment your strategy becomes real. It's also the moment it becomes uncomfortable — because tradeoffs mean saying no to people, requests, and opportunities.
Where tradeoffs get lost
In most organizations, tradeoffs exist in leadership's heads but never make it onto paper. Here's what typically happens:
A leadership team discusses strategic direction and reaches what feels like alignment. What they actually reach is vague agreement on direction — which is not the same as agreement on tradeoffs. The CEO believes the team understands that entering the enterprise market means deprioritizing SMB. The VP of Sales believes the team understands that enterprise sales cycles are incompatible with the current quota structure. The CTO believes the team understands that building for enterprise requires a six-month architectural investment before any revenue can come in.
None of these beliefs are wrong. The problem is that each leader believes the others have internalized a tradeoff that was never explicitly stated. When execution starts, teams run into these implicit tradeoffs and have no framework to navigate them. The result: decision paralysis, repeated escalations, or quiet reversals that undo months of work.
Dave Bailey's work on decision-making highlights how this plays out in practice: good data and good logic still produce bad decisions when the people making them are operating on different implicit models of what the goal actually is. The tradeoff was never surfaced, so teams make different bets and end up pulling in different directions.
Making tradeoffs explicit
The practice that separates companies with real strategies from companies with lists: they write down the tradeoffs.
Not in the board deck. Not in the all-hands talking points. In the actual strategy document that people reference when they're confused.
A tradeoff statement looks like this: "We are choosing to prioritize product depth over platform breadth. This means we will say no to feature requests that serve small user segments even if those users are loud. It means we will invest engineering time in making existing features excellent rather than shipping new features. It means we will measure success by retention and expansion in our core segment, not by new logo acquisition in adjacent segments."
That's a strategy. It tells the product manager what to do when a sales deal requires a feature the team decided not to build. It tells the engineer what "good enough" means. It tells the marketing team who to go after and who to ignore.
It also makes it possible to have a conversation when circumstances change. "We said we'd prioritize depth, but market conditions have shifted — here's why we're updating that tradeoff" is a fundamentally different conversation than "I guess we're changing direction again."
The uncomfortable part
Writing down tradeoffs is uncomfortable because it creates accountability. Once a tradeoff is written, it can be violated — and when it is, that's visible. Companies that avoid writing down tradeoffs can always claim they never said that, or that circumstances changed, or that everyone misunderstood.
The companies that execute well use tradeoffs as governance tools. They revisit them quarterly, update them when the environment changes, and treat them as living decisions rather than one-time declarations. They make the implicit explicit precisely so they can have honest conversations about when and why they're changing course.
