A write-up of my presentation on 'design debt'

Justice Digital

Giving Justice Digital a shared language and practical toolkit for identifying and managing design debt.

Justice Digital
Community of practice
Design ops
GDS

The problem

Across Justice Digital, design quality was inconsistent - and nobody had a shared language for why, or what to do about it. Teams were accumulating design debt without realising it, firefighting problems that could have been prevented, and there was no framework for tracking or prioritising design issues over time. The word 'design debt' meant different things to different people, which made it almost impossible to have a productive conversation about it.

Illustration of a person struggling to carry a large webpage wireframe, with smaller design layouts floating in the background — Design debt can quickly become unmanageable if teams lack a shared language for identifying and prioritising it. Illustration from Headway

What I did about the problem

I researched and structured a community of practice session specifically to fix that. I broke design debt down into its three types - UX, visual, and operational - and explained how each one accumulates differently during agile delivery, what the symptoms look like in practice, and what the long-term risks are if it goes unmanaged. I didn't just diagnose the problem - I introduced practical frameworks teams could use immediately, including maintaining a design debt backlog and mapping debt impact against user journeys, so people left with tools not just theory.

Diagram showing the loop of building design debt alongside a comparison of a misunderstood MVP versus a true MVP that includes functional, reliable, usable, and empathic design — A cycle of rushed fixes leading back into more debt, next to two MVP pyramids - one covering only the functional layer, and a true MVP cutting a thin slice through functional, reliable, usable, and empathic design.

What came out the other side

The Justice Digital design community had a shared language and a practical toolkit for identifying and managing design debt. It contributed to the broader UCD maturity work aimed at raising design quality and consistency across the organisation - and it came from one designer deciding the conversation needed to happen and making it happen.

What I learned

The most valuable design work isn't always on a screen. Sometimes the biggest impact you can have is giving a community the language to talk about a problem they've been feeling but couldn't articulate.