liveBook · Manning

Premature optimization

As explained in Software Architecture Decision-Making

Premature optimization is optimizing a system before sufficient evidence shows that the targeted problem is significant and worth the added cost.

Premature optimization solves a possible problem before evidence shows that it is significant enough to justify added cost, complexity, and delay. Foresight remains valuable, but treating every future risk as an immediate design obligation turns anticipation into overengineering. section 1.1

Use a proportionate response to architectural signals:

  • Act when evidence shows meaningful value; otherwise document the concern, watch it, and revisit it between sprints, releases, or review points. section 1.1
  • Compare the expected benefit of solving a problem now with the complexity, cost, delay, and operational burden introduced. section 1.1
  • Keep deferred risks visible in a lightweight architectural-concerns backlog rather than allowing them to become forgotten TODOs. section 1.1
Figure 1.1 Architecture as a feedback loop. Intent is shaped by forces, translated into decisions, and tested through consequences, feedback, and adaptation.

A feedback loop shows how intent, constraints, decisions, consequences, and adaptation continually influence whether an optimization becomes worthwhile. section 1.1

How Software Architecture Decision-Making covers it

How deep it goes
Explains the trade-off and proposes monitoring, backlog management, and review points, but stops short of a quantitative decision method.
Examples
Contrasts speculative distributed reporting designs with a constrained internal reporting capability shaped by delivery date, team size, usage, and operations.
What you can do after
Evaluate architectural concerns and choose whether to act, monitor, or defer them using cost, evidence, and feedback.
How it connects
Connects premature optimization with overengineering, architectural feedback, operational resilience, and adaptation.

Also explained in

Compare how 5 books explain premature optimization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.