# Design Debt

Design debt is the accumulated cost and user harm created when short-term design compromises, inconsistencies, or neglected evidence remain unresolved.

- Type: term
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-debt/>)

## What it means

Design debt is the growing burden caused by intentional or accidental shortcuts in a product’s experience. It includes incoherent interactions, inaccessible patterns, outdated content, fragmented journeys, unsupported edge cases, and decisions that no longer fit user needs. The related term UX debt emphasizes that users often pay the interest through extra effort, errors, exclusion, or lost trust.

## Why it matters

Small compromises compound. Each workaround makes future changes harder, trains users on inconsistent behavior, increases support demand, and can deepen accessibility or fairness problems. Naming and tracking debt lets teams compare cleanup with feature work in the same planning system and make the human consequences of delay visible.

## When to use it

Use the concept when repeated shortcuts or legacy decisions degrade an experience, when teams inherit products, after rapid growth or acquisitions, and during planning discussions that otherwise treat only technical debt as real. Do not label every imperfection debt; reserve it for persistent costs that merit deliberate management.

## How it works

1. Identify debt through usability research, accessibility evaluation, support themes, analytics, design-system audits, content review, and frontline knowledge.
2. Describe each item from the affected person’s perspective, including frequency, severity, reach, inequitable impact, and evidence quality.
3. Record origin, owner, dependencies, compounding effects, remediation options, and the explicit consequence of deferring it.
4. Prioritize alongside features and technical debt using user harm, strategic value, urgency, effort, and opportunities to fix connected causes together.
5. Allocate recurring capacity, verify fixes with affected users, and change the process or incentives that repeatedly create the same debt.

## A practical example

A subscription product has five cancellation patterns inherited from acquisitions. Customers with screen readers face unlabeled controls, and support agents use workarounds. The team groups the issues as journey, component, content, and accessibility debt, fixes the shared account architecture first, and validates a consistent cancellation flow before migration.

## Where it breaks

The debt metaphor can imply that every shortcut is irresponsible or that harm can be repaid later without consequence. Some losses—such as exclusion, financial damage, or eroded trust—are not reversible. Debt inventories also become graveyards unless tied to ownership and capacity, and subjective scoring can favor visible polish over serious but less visible barriers.

## Common mistakes

- Calling personal design preferences debt without evidence of persistent cost or user impact.
- Creating a separate backlog that product planning never funds.
- Polishing visual inconsistency while deferring accessibility, content, workflow, or trust failures.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-debt/#visualization-design-debt>)

## Sources

1. [UX Debt: How to Identify, Prioritize, and Resolve](<https://www.nngroup.com/articles/ux-debt/>) — Nielsen Norman Group · Professional guidance
2. [UX Debt: Developers Borrow While Users Pay](<https://arxiv.org/html/2104.06908>) — ACM / arXiv · Peer-reviewed research

## Related topics

- [DesignOps](<https://wiki.soroush.uk/topic/design-ops/>)
- [Design Maturity](<https://wiki.soroush.uk/topic/design-maturity/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
