Lesson 1 · Strategy
Strategy basics
A strategy is a set of choices — including what you will not do.
Strategy is a set of choices about where to play and how to win, and equally about what not to do. A goal such as “grow 40%” is not a strategy, and neither is a list of projects. Richard Rumelt's kernel of good strategy has three parts: a diagnosis of the challenge, a guiding policy for dealing with it, and coherent actions that carry the policy out.
Competitive advantage comes from something rivals cannot easily copy: a lower cost structure, differentiation customers will pay for, network effects, switching costs, or scale. Porter's five forces — rivalry, new entrants, substitutes, buyer power and supplier power — explain how much profit an industry lets anyone keep.
For an engineering leader, strategy shows up as trade-offs: which platform to bet on, what to build or buy, where to accept technical debt. Build what differentiates you and buy what does not. A technical strategy that does not trace back to how the business wins is a wish list.
Picture it
A logistics startup's engineers want to build their own maps stack. The CTO asks: “Do customers choose us for our maps?” They do not — they choose the routing optimization that sits on top. So the company buys maps and puts its best engineers on the routing engine. Saying no to the maps project is the strategy.
Key formulas & frameworks
- Strategy
- Where to play + How to win + What not to do
- Rumelt's kernel
- Diagnosis → Guiding policy → Coherent actions
- Porter's five forces
- Rivalry · New entrants · Substitutes · Buyer power · Supplier power
- Build vs buy
- Build what differentiates you; buy what does not
Practice
Score: 0 / 5
Up nextPrioritization
Next lesson