chapter three

3 Good enough architecture vs. perfect architecture

 

This chapter covers

  • The difference between perfect architecture and good-enough architecture
  • Designing within the limits of time, cost, skills, and risk
  • Keeping systems evolvable as requirements and context change
  • The economic reality behind architectural decisions
  • Recognizing where perfection really matters
  • Practical questions for assessing whether architecture is good enough

As the saying often attributed to Voltaire reminds us, “Perfect is the enemy of good.” For architects, that tension appears constantly: between what is theoretically ideal and what can realistically be built, supported, and evolved.

Perfect architecture is seductive because it offers clarity. Boundaries are sharp, dependencies intentional, components replaceable, and patterns applied cleanly. But real architecture is rarely created under perfect conditions. Deadlines loom, budgets shrink, teams change, requirements drift, and organizational priorities shift. The architect’s challenge is not to abandon quality, but to judge what level of quality, rigor, and flexibility the context actually justifies. Table 3.1 describes the difference between perfect architecture and good-enough architecture.

3.1 Perfect architecture: the seduction of clean lines

3.2 Good enough architecture: the art of trade-offs

3.3 Architecture reality: evolution as a cornerstone

3.4 The economics of good enough

3.5 When perfection actually matters

3.6 How to know if architecture is “good enough”

3.7 Summary