Design System Audit.
Find what's actually broken in your design system.
If your components feel inconsistent, your system is hard to maintain, or your team is solving the same problems differently every sprint — this is where to start.
You're stuck in the same loops
Not every team needs an audit. But if one of these sounds painfully familiar, it's probably time for an honest look.
Your component library has become inconsistent or hard to trust.
Designers and developers are solving the same UI problems differently.
Accessibility issues keep surfacing late — in QA, in audits, in production.
Your system exists, but it isn't working the way it should.
Most teams try to fix their system by adding more. More components. More documentation. More rules.
That usually makes things worse.
A clear view of what's actually going on
No vague "here are some ideas" deck. You get a structured, honest, prioritized plan.
Where it's inconsistent — and why
A clear view of what's drifting visually, structurally, and in code — plus the reasons it keeps happening.
Accessibility risk, component-by-component
A WCAG 2.1 AA breakdown that tells you exactly where your risk lives — not just a score.
A prioritized list of issues
Not everything is equally broken. You'll know what to fix first, what to defer, and what to ignore.
Specific recommendations for each fix
"Refactor your button API" isn't advice. I give you the actual approach, tradeoffs, and what "done" looks like.
A roadmap your team can actually follow
Sequenced, scoped, and honest about effort. Something you can run without me if you want to.
A debrief with your team
A live walk-through so findings don't just land in a doc and die. Your team asks questions; I push back on mine.
The full scope
Five focused tracks across your system, your code, and your documentation.
-
Component consistency analysis
Visual and code-level. Where components diverge from the spec, each other, and themselves.
-
Accessibility risk assessment
WCAG 2.1 AA scored at the component level, with the real risks called out in plain language.
-
Design token structure & naming review
Are your tokens doing the work they should? Do the names tell the truth? Where are the leaks?
-
Documentation quality & coverage
Does your documentation match the code people actually ship? Where are the gaps driving forks?
-
Prioritized remediation roadmap
Ranked, sequenced, and sized. The thing your team can point to when someone asks "what's next?"
Four steps, no surprises
Share access
Storybook, Figma, repo — whatever represents the actual state of your system. We start by looking at the real thing, not what you wish existed.
Audit review
I work through consistency, accessibility, tokens, and documentation — one track at a time, with notes and evidence as I go.
Structured report
You get a ranked set of findings with recommendations, tradeoffs, and a roadmap — written for humans, not for a pitch deck.
Debrief walk-through
We meet, I walk your team through it, answer questions, and make sure the recommendations actually land somewhere they'll get used.
Design System Audit
Final scope depends on system size and surface area — we'll sort that out on the intro call. No retainers, no surprises.
From folks who've worked with me
Josh has an unusual ability to hold the big picture and the details at the same time. He brings clarity to messy systems and the kind of structure that actually holds up under delivery pressure.
Josh sees the real problem quickly and knows how to articulate it in a way that gets teams moving. That's rare — and genuinely valuable.
Let's find what's actually broken.
Book a 30-minute intro call. Tell me what's frustrating about your system and I'll tell you whether an audit is the right next step — honestly.