Managing Design Debt and Entropy
Day 21 of 30 · The Playbook 2026 – Masterclass for Designers
Detect, measure, and reduce design debt with a repeatable cadence.
Learning Goal
- Define design debt and signals.
- Metrics: duplicated components, token anomalies, missing states.
- Impact × effort matrix.
- Debt backlog and monthly reduction ritual.
Why This Matters
- Debt raises cost and risk.
- Measurement unlocks resourcing.
- Reduced debt → faster releases, better UX.
Explanation
- Signals: duplicate button variants, inconsistent colors, undocumented states.
- Metrics: “divergences per 100 screens”, “non-tokenized values count”.
- Process: audit → backlog → fix X tickets per sprint.
Examples
Bad: “Feels messy” with no list.
Good: Debt table, quantified, monthly quota.
Guided Exercise
- Create a debt audit template (item, issue type, impact, estimate).
- Audit 5 screens and fill the table.
- Set a monthly quota (e.g., 3 debt tickets per sprint).
Independent Exercise
Present the numbers to the team and get commitment to the quota.
Self-Check
- Debt table exists.
- Impact × effort prioritization set.
- Monthly quota defined.
Optional Deepening
- NNG design debt: https://www.nngroup.com/articles/design-debt/