What I recommended
I brought the audit and workshop findings together in a report and played it back to design leadership, then agreed priorities together.
The report covered 16 areas across two levels, each with its own evidence and examples. This is its index:
AreaObservationSuggested direction
System structureCurrent DS behaves more like a component libraryEvolve towards a more teachable, principle-driven system
Product expressionSame library serving for products with different needsDefine product expression principles before adding DS complexity
Documentation & source of truthDocumentation fragmented across Figma and SupernovaDefine clearer source of truth and platform roles
AccessibilityAccessibility applied as ceiling on design expressionDefine clearer principles and application boundaries
Token architectureTokens defined by values rather than semantic rolesUse semantic tokens referencing shared base values
Component behaviour and rolesComponents primarily stacked vertically, limiting hierarchyIntroduce varied behaviours and layout patterns
System fragmentationMultiple parallel systems used across productsClarify roles or consolidate systems into one
System governanceUnclear process for adding new elementsDefine request, review, and release process
TypographyStyles structured by viewport rather than semantic roleDefine typography roles (Hero, Title, Body, Label, etc.) and apply responsive scaling through breakpoints
ColoursDark tones (green, black, grey) used across many UI elements creating limited hierarchyIntroduce clearer semantic colour roles and broader palette usage
Surface hierarchyCards stacked on similar backgrounds reduce spatial hierarchyIntroduce surface tokens (background, surface, subtle, elevated, animated)
Icon systemLimited flexibility in size and treatmentExpand icon properties (size, surface, colour roles)
DividersDivider lines feel visually heavy in some contextsLighten divider styling and standardise usage
Page transitionsSingle transition used across most flowsIntroduce small set of contextual transitions
Micro-interactionsInconsistent styling across statesRefine button states and introduce more interaction patterns
Visual expressionUI relies heavily on text and iconographyIntroduce imagery, patterns, and richer visual accents
Setting priorities
We prioritised the findings by impact and effort. The clearest conclusion was that the UI uplift depended on the foundations: it couldn’t land consistently until the tokens had a clear semantic structure.
That set the order for the work that followed:
- 01Token ArchitectureProposing a semantic token architecture the uplift could stand on.
- 02UI UpliftConcepts showing how stronger foundations lift the whole experience.
- 03Blueprint & DecisionTwo routes, a feasibility test, a rollout plan, and the decision the team took forward.