Design Debt
The accumulated cost of inconsistent, undocumented or expedient design decisions that make every future change slower than it should be.
Process & MethodsDesign debt looks like six button styles, four date formats and three empty-state patterns that arrived one deadline at a time. Like technical debt it is not automatically bad — shipping a slightly wrong component to hit a launch is often correct — but it compounds, because each new screen has to choose between the existing variants and every choice adds another.
The symptom teams notice is estimation drift: small changes start taking a week because nobody is sure which component is canonical or what breaks. Paying it down is what a design system is for, and the honest way to fund that work is to name the interest payment rather than to describe it as a redesign.
In practice
A dashboard had accumulated five card components with different padding. Before: adding a metric card meant copying the nearest one and adjusting, roughly half a day. After consolidating to one card with variants, the same task took under an hour. The catch — consolidation touched every screen, so it needed a full regression pass nobody had budgeted.
Learn more
You may ask
Frequently Asked Questions
How do we measure design debt?
Count duplicates — how many button, input, table and empty-state variants exist versus how many are intentional — and track how long small UI changes take. Both numbers are crude, but a trend in either is enough to justify the work.
Should we pay it all down at once?
Rarely. A full cleanup is a large regression risk with no user-visible benefit. Paying it down component by component, starting with the ones touched most often, gets most of the speed back at a fraction of the risk.
Related terms
All terms- Design SystemThe single source of truth for how a product looks and behaves: tokens, components, patterns, usage rules and the process for changing them.
- Component LibraryA shared, versioned set of reusable interface components that designers and engineers build from instead of recreating elements per screen.
- UX AuditA structured review of an existing product against usability, accessibility and business criteria, producing a prioritised list of problems and fixes.
- Design TokenA named variable holding one design decision — a colour, spacing step, radius or type size — so the value can change everywhere from one place.
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us