Interview frequency: …
Short answer
It is the gradual accumulation of inconsistent components, varying interaction patterns, and quick temporary workarounds added to a product over time without cleanup, weighing down the user experience and slowing development.
Explanation
Just as developers pay for technical debt, users experience design debt: 14 different shades of blue, six button styles, and inconsistent error messages in every section. Its costs include: (1) confusing users and weakening trust in the platform's professionalism; (2) wasting designers' and developers' time debating repeated details; and (3) making new features harder to adopt. The solution is to schedule regular Design Debt Sprints.
Common mistakes
- Failing to document rushed design decisions and letting them accumulate for years until the platform becomes inconsistent.
- Assuming that a complete ground-up redesign is the only way to clean up Design Debt.