The cost of fixing the same defect rises as development advances

What it is

The same usability defect ("users can't find the export entry") costs a pen stroke at the sketch stage, a design round at review, code and tests after development, and a release plus migration plus support plus user relearning after launch—cost amplifies at every step of the development ladder. This is the hardest economic reason to evaluate usability early.

Why it happens

The rise comes from accumulating dependencies: at each later stage the defect is referenced by more finished artifacts—design documents, code, test cases, copy, published help content, and users' habits. The fix no longer touches just the defect; it cascades through all downstream artifacts and pays coordination and relearning costs. After launch, discovery cost stacks on top (the defect is only confirmed through user behavior). Amplification factors vary by estimate—the classic software-engineering 10–100x figures concern code defects—but the direction holds for usability defects and is often steeper, because the interaction model permeates more than the code does.

Studying it

The cost curve can be evidenced from internal data: track fix hours for comparable defects by discovery stage (requirements/design/development/post-launch) and plot the stage-cost curve. The key control is defect complexity—different defects have different intrinsic difficulty, so cross-stage comparison must match types. The curve feeds economic argument directly: the cost of early evaluation against the estimated late-stage fix cost of the defects it intercepts yields "inspection cheaper than repair" evidence.

Where it stops holding

The curve is a strong tendency, not a law: lightweight iteration and feature flags flatten some late-stage costs, and some defects only surface with real users, so no "early fix cost" exists for them. Amplification depends heavily on organizational process—release cadence, test coverage, support capacity—and borrowed numbers do not transfer. The curve argues for earlier evaluation, not unlimited front-loading: evaluation itself costs, and an optimal inspection density exists.

Applying it

• Place low-cost evaluations (walkthroughs, quick tests) at the process gates—before requirements freeze, at design review, mid-development—to intercept defects in the cheap stages.
• Add "discovery stage" and "fix hours" fields to the defect tracker and accumulate your own cost-curve data.
• When arguing for early usability budget, use your organization's curve, not literature multipliers.

Related

• Same group: B5.14.1 Usability investment is adopted only when its payoff is translated into cost or revenue items the organization already tracks · B5.14.3 Support cost and churn are the two easiest doors for attributing value to usability · B5.14.4 Internal systems justify by hours saved; external products by conversion and retention—and the two must not be mixed · B5.14.5 Arguments must land inside the decision-maker's budget cycle; long-term gains beyond it are not counted
• Nearby: R2 Design Systems and Engineering Delivery · Q1 Research Methods and Evaluation
• Search terms: cost of defects · early usability evaluation · cost escalation