Run an audit before any major system change, whether you are aligning a pattern, creating new tokens, or preparing to pitch a system. Audits reveal what really exists today, surfacing strengths, inconsistencies, duplication, and gaps. They create a shared foundation that guides alignment, setup, and design decisions.
How to
-
Set your scope
Decide what you are auditing, such as a single pattern, tokens, accessibility, or something broader.
-
Collect real examples
Gather design files, live product screenshots, or code snippets across platforms.
-
Sort and group
Organise examples in a way that fits your audit focus. This could mean grouping by platform for consistency checks, by token type for naming reviews, or by categories like colour, spacing, or patterns to spot gaps and overlaps.
-
Extract insights
Capture issues, gaps, and duplication, as well as what is already working well.
-
Define requirements
Translate findings into actions, such as naming standards, missing tokens, component clean up, or documentation updates.