Section 03 Flashcards — Writing Engineering Strategy
flashcards selt strategy engineering-leadership
What is engineering strategy according to Will Larson?
?
Engineering strategy is a specific, actionable set of decisions and constraints that guides future technical choices within an organization. It is grounded in current reality, makes trade-offs explicit, and is specific enough that reasonable people could disagree with it. This distinguishes it from vague principles.
What is the difference between engineering strategy and engineering vision?
?
Vision is the 3–5 year directional picture of where the organization wants to be technically — broad and aspirational. Strategy is the 6–18 month, decision-guiding layer that closes the gap between today and the vision — specific and actionable. Vision tells you where you’re going; strategy tells you what you will and won’t do to get there.
Why do most engineering “strategies” fail to be genuinely useful?
?
Most “strategies” are actually lists of principles — statements like “we value simplicity” that are too abstract to guide a concrete decision between two real options. Principles feel authoritative without requiring the author to take a stance, which is why they dominate default strategy-writing exercises. They provide no guidance when it matters.
What is the “uncomfortably specific” heuristic for evaluating a strategy statement?
?
If you cannot imagine reasonable people disagreeing with a strategy statement, it is too vague to be useful. A real strategy makes specific choices that exclude alternatives — and those exclusions might be wrong. That falsifiability is what makes the strategy meaningful and testable.
Describe Larson’s three-step process for writing engineering strategy.
?
- Write five design documents — real decisions with context, alternatives, constraints, and rationale.
- Synthesize patterns across those documents — recurring trade-offs, consistent choices, implicit values.
- Extract the implied strategy — write specific, actionable decisions derived from the patterns, then test each against the “uncomfortably specific” heuristic.
Why does Larson recommend starting with design documents rather than writing strategy top-down?
?
Design documents provide an evidence base grounded in real decisions and actual constraints. Strategy synthesized from them reflects what the organization actually values and faces, rather than aspirational ideals that engineers will immediately recognize as disconnected from reality. The bottom-up approach also builds organizational buy-in because the strategy emerges from work many people contributed to.
What is the difference between an engineering principle and an engineering strategy element?
?
- Principle: “We value operational consistency.” — States a value, cannot decide between two specific options.
- Strategy: “All new backend services must be written in Go and deployed via our internal Kubernetes platform.” — Names a specific choice that excludes alternatives and could be wrong.
Principles are more durable and change more slowly; strategy is more specific and needs regular revision.
Give an example of turning a principle into a strategy.
?
- Principle: “We prefer boring technology.”
- Strategy: “New services may only introduce a technology not already in our stack if a Staff+ engineer writes an RFC approved by the platform team. Unapproved technology introductions will not receive platform support.”
The strategy makes the principle operationally enforceable and creates a clear decision process.
What five elements should a design document include to serve as useful strategy raw material?
?
- Context — What was the situation when this decision was made?
- Alternatives — What else was considered?
- Constraints — What could not be changed?
- Decision — What was chosen?
- Rationale — Why was this chosen over the alternatives?
Without all five, the design doc cannot be synthesized into strategy effectively.
Why do real strategies make trade-offs explicit?
?
Every strategic choice forecloses other options. A strategy that does not name what it trades away has probably not been thought through. Naming trade-offs (“we trade deployment flexibility for operational simplicity”) makes the strategy honest, testable, and more credible — engineers can see that the author has actually thought through the consequences.
Why does acknowledging constraints make strategy more credible, not less?
?
Engineers immediately apply their knowledge of real constraints when evaluating any proposed strategy. If the strategy ignores a major constraint (existing systems, team skill levels, budget), they will recognize it as aspirational fiction and dismiss it. Naming what you cannot change shows the strategy is grounded in reality, making engineers more likely to accept and use it.
What are four common reasons engineering strategies fail?
?
- Too abstract — principles masquerading as strategy.
- Not grounded in reality — ignores actual constraints, existing systems, or team capability.
- Trade-offs not made explicit — avoids hard choices, so conflicts are deferred rather than resolved.
- Written once, never revisited — strategy has a shelf life; what applies at 50 engineers misleads at 500.
What is a fifth common reason engineering strategies fail?
?
Written by too few people in isolation. Strategy written by a single person lacks the organizational buy-in needed for it to influence decisions. The synthesis step — drawing from design documents authored by many engineers — is also how broad buy-in is built into the process.
What is the shelf life problem with engineering strategy?
?
A strategy written for one phase of organizational scale may actively mislead an organization at a different scale. Strategy must be revisited regularly — not just maintained as a document — so it reflects current constraints, team capabilities, and product direction. Without revision, strategy becomes archaeology: a record of past thinking rather than a guide to current decisions.
What are the two simultaneous purposes of design documents?
?
- Immediate: Records the reasoning for a specific decision, preserving it for future reference without relying on the memories of the people in the room.
- Strategic: Across a corpus of documents, patterns become visible that reveal what the organization actually values vs. what it claims to value — the raw material for synthesizing real strategy.
What makes writing engineering strategy explicitly Staff-level work?
?
It requires:
- Cross-organizational visibility to see enough decisions across teams to synthesize patterns
- Long time horizon — experience with what has been tried, what failed, and why
- Influence without authority — strategy is adopted through persuasion, not mandate
- Willingness to be wrong — a real strategy is falsifiable and requires courage to publish
What is the difference between “specific enough to be wrong” and a bad strategy?
?
“Specific enough to be wrong” means the strategy makes falsifiable claims — if the predicted outcomes don’t materialize, you have reason to revise it. This is a feature, not a flaw. A strategy that cannot be tested by outcomes is either a principle (too vague) or fiction. A bad strategy makes specific claims that are clearly not grounded in evidence or reality — specificity alone is not sufficient.
How does the strategy-writing process build organizational buy-in?
?
When strategy is synthesized from design documents authored by many engineers, those engineers recognize their real decisions and constraints reflected in the output. The strategy does not feel imposed from outside — it feels like a codification of what the organization already does when it does its best work. This recognition creates buy-in that top-down strategy writing cannot achieve.
Describe the relationship between engineering vision and engineering strategy using a navigation analogy.
?
Vision is the destination on the map — where you want to be in 3–5 years. Strategy is the planned route — the specific roads you will take, turns you will avoid, and constraints (no toll roads, must stop in X city) that shape how you travel. A destination without a route is aspiration; a route without a destination is purposeless movement. Both are necessary and serve different functions.
What is the correct unit of measurement for testing whether a strategy statement is real?
?
A strategy statement must be decision-guiding for a concrete choice. The test: “Can an engineer use this statement to decide between two real options they are facing, without asking for further clarification?” If yes, it is strategy. If they would still need to ask someone, it is a principle at best.
What should the ideal length of an engineering strategy document be, and why?
?
Short enough to be read in approximately 20 minutes and for key decisions to be recalled without re-reading. Strategy documents that are too long are effectively no strategy at all — they will not be read or remembered. Length is itself a signal of whether the author has made clear choices; vague strategies tend to be long because the author has not yet done the hard work of deciding what to exclude.
Summarize the core argument of “Writing Engineering Strategy” in one sentence.
?
Real engineering strategy consists of specific, actionable, falsifiable decisions synthesized bottom-up from real design documents — not top-down lists of principles that feel authoritative but cannot guide a concrete technical choice.
Total Cards: 22
Review Time: ~16 minutes
Priority: HIGH
Last Updated: 2026-05-30