Every locally optimal difference accumulates into overall inconsistency

What it is

A small change made by one page or team can look reasonable locally: one more synonym here, a button moved there, “later” substituted for a precise state. None is serious alone, but together they turn internal consistency from a set of local optima into product-level confusion.

Why it happens

Consistency is a product-level relational property, while local decisions see only the page metric, the team’s users, or the current release. Each change becomes a precedent that the next person copies and extends. Variant counts grow with modules and versions, and mapping conflicts surface during cross-task use. Users experience not a set of well-reasoned design decisions but a path whose object names, control locations, and feedback meanings keep changing.

Where it stops holding

Not every difference is debt. Real task differences, accessibility needs, platform constraints, and experimental learning can require variation; blocking all deviation locks the product into an old model. The test is not “exactly the same everywhere,” but whether the difference is explainable, whether it changes the expression of the same meaning, and whether it has entered a reusable artifact.

Applying it

• Keep a consistency-debt ledger recording the meaning, current variants, locations, causes, and migration plan.
• Before adding an expression variant, check whether it is only local taste; if difference is necessary, state the semantic distinction and why the existing expression cannot be reused.
• Sample core tasks each quarter for end-to-end walkthroughs and count changes in object names, action consequences, and key control paths.
• Sync fixes in high-traffic modules back into shared components and vocabulary, so improvement is not limited to the page where the problem was found.

Related

• Same group: B2.23.1 Internal consistency is judged by whether the same meaning always uses the same expression · B2.23.2 Consistency maintained by shared components and a unified vocabulary survives; consistency maintained by documentation erodes over time · B2.23.4 The benefits of internal consistency grow with product scale and frequency of use
• Nearby: B2.10 Consistency · R2 Engineering Delivery
• Search terms: local optimization · consistency drift · design debt