AvailableFrom January 2027 for product, service, design systems and leadership contract roles.Get in touch
Luke James Taylor Logo

— A design system, reviewed. People first.

  • An independent review of a multi-brand design system.
  • Several consumer brands, on mobile, desktop and web.
  • People and experience first. System second.
Client
Global consumer tech company (under NDA)

The short version

A 30-second read
  • The problem

    A design system serving several consumer brands had good foundations, and leadership wanted an independent view before deciding what came next.

  • What I did

    I reviewed it like a product: interviews, workshops, and a close look at its libraries, tokens, documentation and ways of working.

  • What changed

    An independent view for leadership, prioritised recommendations, and a plan for what to reuse, evolve and start fresh.

  • 10principles, shared first
  • 4layers reviewed
  • 6recommendations
Read the full story

01/ Summary

What was delivered and how
  • — Services
    • Design system audit
    • Stakeholder interviews
    • Workshop facilitation
    • Research synthesis
    • Design system strategy
    • Figma architecture
  • — Deliverables
    • 10 design system principles
    • Workshops with the design system team
    • Interviews with designers, engineers and contributors
    • A review of libraries, tokens, documentation and ways of working
    • A playback to leadership, with recommendations
    • A plan for what to reuse, evolve and start fresh
  • — Outcomes
    • An independent view for leadership to make decisions from
    • Prioritised recommendations, aimed at usability, visibility and product-led growth
    • A plan for what comes next: what to reuse, what to evolve and what to start fresh
    • Principles shared first, so the review was judged against something open and agreed

02/ Why a review

A big system, decisions to make, and a need for an outside view

The system

A token-driven design system serving several consumer brands, across mobile, desktop and web. Good foundations, and a lot of teams relying on it.

What leadership needed

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.

03/ How I approached it

Research, done in the open
  • Stakeholders

    Conversations with designers, engineers and contributors about day-to-day use, adoption and friction.

  • Product design

    How well the system supports real product work, across brands and platforms.

  • System artefacts

    The libraries, component structures, tokens, documentation and ways of working.

  • Usage signals

    Recurring themes, workarounds and confidence gaps, across every conversation.

  • Workshops

    What needs to change, ideas, a vote on what matters most, and next actions.

  • A confidence check

    Each workshop ended with one question: how confident do you feel using the system right now?

04/ My principles

Ten things I believe about design systems, shared before judging anyone's
  1. Let the product build the design system. Don't let the design system build the product.
  2. Start lean, with no bloat. Only systemise what's needed now or in the very near future.
  3. Documentation that enables self-service first, but never discourages teams from asking for help on a human level.
  4. The design system team does the hard work so other teams can contribute. Accept contributions at any fidelity.
  5. Accessibility from the start. Not a nice-to-have, and never a come-to-later.
  6. Give teams clarity and confidence. Track your work, share your estimates, help them deliver on time.
  7. Know exactly who you're supporting, when they need you, and how to help. Always lead with empathy.
  8. The IBM Hallmark Effect is real: do something brilliantly for one team, and it becomes the benchmark others want.
  9. The best tech choices are shared ones, made with, not for, the people they impact.
  10. Open up your roadmap. Share your wins and your work in progress. Clarity earns trust.

05/ Looking layer by layer

From foundations up to whole experiences

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.

The base

Foundations and tokens

Colour, type, spacing and theming, and how design decisions reach every platform's code.

06/ What I recommended

Less new infrastructure. More support for real product work.
  1. Be clear about the system's role

    Does the system shape experience quality, or provide the consistent foundations underneath it? Say which.

    FromInfrastructure to some teams, an experience guide to others
    ToOne stated role, so teams know where it leads
  2. Make it easy to use day to day

    Get designers from a blank canvas to a working layout quickly.

    FromAnswers spread across tools, chats and old files
    ToOne clear starting point, and help in person
  3. Make decisions visible

    Clear signals about priorities and timing, so the system never feels slow or opaque.

    FromPriorities set out of sight
    ToAn open roadmap, and a simple update: new, updated, deprecated
  4. Show what's ready

    Confidence that design and code match.

    FromLooks finished in design, isn't ready in code
    ToStable, evolving or experimental, at the point of use
  5. Guide whole experiences, carefully

    Not everything should be standardised. Only what more than one team needs.

    FromEvery team solving common journeys its own way
    ToReference layouts and flows, where demand is shared
  6. Let products lead

    Grow the system through what's proven in real products.

    FromGood ideas stuck inside individual products
    ToA clear path from a local solution to a shared one

07/ What comes next

What to reuse, what to evolve and what to start fresh

Reuse what works

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.

Evolve the rest

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.

08/ Outcomes

Clarity for leadership, and a way forward

What it delivered

  • An independent view

    For leadership to make decisions from.

  • Prioritised recommendations

    Aimed at usability, visibility and product-led growth.

  • A plan for what comes next

    What to reuse, what to evolve and what to start fresh.

  • Principles shared first

    So the review was judged against something open and agreed.

There's more to this one

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.

Private case studies

Available from January 2027

Looking for a design leader?

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.