Good-enough design is intentionally sufficient architecture: it solves the current problem, meets a non-negotiable minimum floor, and leaves room to evolve. It rejects both the fantasy of a complete ideal end state and the false economy of building too little for the consequences at stake. The aim is operational fitness—not reduced quality. section 3.2 section 3.6
Table 3.1 Perfect architecture vs. good-enough architecture
|
Perfect
architecture
|
Good-enough
architecture
|
|
·
Assumes
near ideal conditions.
·
Optimized
for elegance and purity.
·
Designed
for a complete end state.
·
Often
commits early.
·
Can
exceed teams or business capacity.
·
Harder
to justify economically.
|
·
Designed
for real conditions.
·
Optimized
for delivery, operation and change.
·
Solves
the current problem well.
·
Preserves
room for evolution.
·
Fits
team capability and timing.
·
Tied
to value, cost and context.
|
The contrast is practical: optimize for delivery, operation, change, team capability, timing, value, and cost rather than purity under ideal conditions. section 3.0
The design level of rigor should match intent, expected lifetime, constraints, and risk. Time, cost, skills, ownership, uncertainty, and organizational priorities are architectural forces, not background inconveniences. A design is good enough only while those conditions continue to support it; changing conditions can make an earlier decision worth reopening. section 3.2 section 1.7
A good-enough decision balances several obligations:
- Solve the known problem while avoiding complexity justified only by hypothetical futures. section 3.1
- Meet context-appropriate standards for correctness, security, operability, understandability, and recoverability. section 3.6
- Give additional care to decisions that are expensive to reverse, while keeping uncertain decisions cheap to change. section 3.2
- Choose structures the team can operate, debug, support, and evolve without relying on external heroes. section 3.1
- Justify cost and operational attention through the value the system creates for its organization. section 3.4
A lightweight review before commitment
State the present intent and minimum floor. Name the strongest forces: time, cost, skills, risk, ownership, or uncertainty. Then examine overbuild and underbuild risks, choose the justified rigor, and record a trigger—such as changed value, scale, risk, ownership, or team capability—for revisiting the decision. This makes compromise explicit rather than accidental. section 3.6
Use early delivery and production feedback to strengthen only the parts that prove important. Stabilize decisions whose late reversal would affect environments, release flow, access control, data, or accumulated ownership boundaries; leave less certain choices open until evidence improves. Designing the entire future too early delays value and makes reversal more expensive. section 3.3
The central discipline is to resist two drifts. Overengineering pays now for futures that may never arrive. Oversimplification makes tomorrow’s necessary change unnecessarily hard. Good-enough design stays between them by making trade-offs visible, testing them against reality, and adapting before their costs become embedded. section 3.2 section 3.7
