How-to · Design systems

How to audit a design system in 5 days.

A pragmatic, 5-day framework for auditing a design system end-to-end. Stakeholder interviews on day 1; ship a prioritised punch list and adoption roadmap on day 5. This is the version I run for clients.

By Devina Naik · 2026-05-04 · 8 min read

Most design system audits sprawl. They start with "let's inventory everything", spend three weeks tagging components, and produce a 60-page Notion doc nobody reads. Five days is enough — if you focus on the diff between the library and reality, and you finish with prototypes, not a punch list.

Day 1 — Listen

Run six 30-min interviews across product, design and engineering. Ask: what does the system make easy? What does it make hard? Where do you copy-paste components instead of using them? Capture verbatims; resist the urge to redesign in real time.

Day 2 — Inventory the diff, not everything

Walk the Figma library and the production codebase side-by-side. List every component, every variant, and every detached instance you can find in shipping product. The diff between library and reality is the audit's most valuable artefact — far more than a count of components.

Day 3 — Cluster

Group findings into themes — usually four or five: governance, documentation, naming, accessibility, and "components that don't exist but should". Bucket each finding by impact (High / Medium / Low) and effort (Small / Medium / Large). Resist a 1-to-100 ranking.

Day 4 — Prototype the fix

For the top two High-impact / Small-effort findings, prototype the proposed change in Figma. The audit lands very differently when stakeholders can see what "fixed" looks like instead of reading about it.

Day 5 — Deliver and align

Ship a 12–15-page report with: the punch list, the prototypes, a 30/60/90-day roadmap, and an explicit "what we won't fix yet" section. End the day with a 60-min readout. Decisions you don't get on this call won't get made later.

Why 5 days, not 3 weeks

Three-week audits drift because they have time to. Five-day audits force triage — and triage is the actual deliverable. The teams that get the most out of a system audit aren't the ones with the most thorough findings; they're the ones who move on the top three within a quarter.


If you're considering a design-system audit for your team, Concept Folie runs this engagement as a fixed-price, 5-day sprint.

Start a design system audit →   ← All journal posts