Guidance Review highlights where your system documentation is outdated, duplicated, or missing. By running this regularly, you keep guidance trustworthy and easy for teams to follow. Use it when your system grows quickly or after big shifts such as new tokens, major releases, or updated accessibility standards.
How to
-
Define scope Decide if you're reviewing all system docs, or focusing on one part such as specific patterns or tokens.
-
Gather inputs Pull current guidance into one place. Include guidance pages, specs, and inline component workshops.
-
Check for gaps Look for missing pages, outdated images, or inconsistent naming. Mark where system changes have outpaced documentation.
-
Spot duplication Identify repeated content across multiple places. Choose one source of truth, and archive or merge the rest.
-
Rate severity Tag findings as high, medium, or low impact to prioritise updates.
-
Feed into improvements Push results into your System Health Check or Roadmap Planning so fixes scale with other system improvements.