
A design system serving several consumer brands had good foundations, and leadership wanted an independent view before deciding what came next.
I reviewed it like a product: interviews, workshops, and a close look at its libraries, tokens, documentation and ways of working.
An independent view for leadership, prioritised recommendations, and a plan for what to reuse, evolve and start fresh.
A token-driven design system serving several consumer brands, across mobile, desktop and web. Good foundations, and a lot of teams relying on it.
Decisions about the system's scope and direction were coming up. I was brought in as an external design systems practitioner, to find out how it worked in practice and give leadership an independent view to decide from.
A design system is a product. So I researched it like one: people and experience first, system second.
Conversations with designers, engineers and contributors about day-to-day use, adoption and friction.
How well the system supports real product work, across brands and platforms.
The libraries, component structures, tokens, documentation and ways of working.
Recurring themes, workarounds and confidence gaps, across every conversation.
What needs to change, ideas, a vote on what matters most, and next actions.
Each workshop ended with one question: how confident do you feel using the system right now?
A design system can be strong at one layer and thin at another. So I looked at each in turn, and at how they fit together. Choose a layer to see what I look for there.
Onboarding, multi-step journeys, loading and feedback states. Is there a shared approach, or does every team solve them differently?
When a team solves something well, can it flow back into the system? Or does it stay stuck inside one product?
Coverage across platforms, how mature each one is, and whether designers can see what's ready where they work.
Colour, type, spacing and theming, and how design decisions reach every platform's code.
Does the system shape experience quality, or provide the consistent foundations underneath it? Say which.
Get designers from a blank canvas to a working layout quickly.
Clear signals about priorities and timing, so the system never feels slow or opaque.
Confidence that design and code match.
Not everything should be standardised. Only what more than one team needs.
Grow the system through what's proven in real products.
I went area by area, rating how much could be carried forward. Strong foundations, like a token structure and theming that works across brands, are worth keeping.
Components that are simpler and slot-based rather than variant-heavy, accessibility from the start, and documentation that lives beside each component, where designers work.
For leadership to make decisions from.
Aimed at usability, visibility and product-led growth.
What to reuse, what to evolve and what to start fresh.
So the review was judged against something open and agreed.
This is the version I can share openly. The full case study, with the client named and the detail left in, is in my private case studies. Ask me for the password.
Available from January 2027
I take on contract roles as a design consultant, head of design or fractional design lead, across product, service and design systems. Remote anywhere, or hybrid across the UK.