Conceptual Integrity

A system should reflect one coherent set of design ideas, so that it feels designed by a single mind. Brooks calls it the most important consideration in system design: better to have one consistent set of ideas, even omitting some good features, than many good but uncoordinated ones.

Why it Matters

Conceptual integrity makes a system easier to learn, use, and extend, because people can predict the whole from a part. It usually requires separating architecture (the coherent design) from implementation, so a small group or a single architect can hold the vision.

Signals

• Parts that feel consistent and predictable across the system.
• The opposite: a patchwork where every module has its own conventions and the whole resists a simple mental model.

Benefits

Predictability, learnability, and lower complexity, because consistency means less to remember and fewer surprises.

Risks

Protecting integrity can centralize design and slow contribution; lost entirely, the system fragments into an inconsistent collection, often via the second-system effect or design by committee.

Tensions

Coherence pulls toward central control while delivery and inclusion pull toward many independent contributors; conceptual integrity also competes with completeness when keeping the design clean means dropping good ideas.

Examples

A tool with a small, consistent set of commands that compose predictably; an API where every endpoint follows the same conventions, versus one stitched together from many teams' styles.