You've conceived an idea; now, write its rule book. A Quick Reference Guide keeps your design consistent from start to finish. Clarity is key. This guide puts style, form, and conventions in one place. It's easy to grasp but thorough enough for various people. I've seen these guides prevent countless design misunderstandings over the years.
Duration
3 hours
Group Size
3-5
Category
Luma
Difficulty
Easy
Summarize the design rationale.
A quick reference guide that documents key information.
An accessible summary for users.
Improved information access.
Design intent fades over time. Documentation prevents misunderstandings. Aim for a 2-4 page guide covering 90% of use cases. Show bad implementations with screenshots. People remember failures. Update the guide with every design change and schedule quarterly reviews. The designer should draft it; someone else should edit it. Figma, Notion, Confluence, Storybook, and PDFs are good format options.
Identify What Needs Documenting (15 minutes): Review your design system, component library, or new feature. What will someone need to know in six months when you're unavailable? Focus on misused components, edge cases, and the 'why' behind decisions.
Gather Your Materials (20 minutes): Collect existing materials: design files, Slack threads, code comments, and screenshots. Don't start from scratch.
Structure Your Guide (30 minutes): Create sections for: 'When to use this' (the problem it solves), 'Anatomy' (labeled diagrams), 'Variations' (states/sizes), 'Do/Don't' (visual examples), and 'Specs' (spacing, colors, typography).
Write Like You're Explaining to a New Hire (60 minutes): Assume the reader is smart but lacks context. Use screenshots. Highlight common mistakes. I find this step is often underestimated; clear writing is crucial.
Test It (30 minutes): Have someone unfamiliar with the design use the guide to implement it. Identify areas of confusion and edit accordingly. This reveals gaps you didn't know existed.
Make It Findable (15 minutes): Place the guide where people look: design system site, Confluence, or Notion. A perfect guide is useless if no one can find it.
Unlock Step-by-Step Instructions
Join 2,500+ facilitators who use Workshopr to plan better workshops — free during beta.
Before you run the room, you read it. Steal from facilitators who've made every mistake, study the moves that worked, and stockpile exercises you can pull when the agenda goes sideways. Your reading list now is your toolkit later.
A workshop is a sequence of decisions you make before anyone walks in: who's there, what changes by the end, where the energy spikes and dips. Block out the time, name the moves, leave room for the room. Plan tight enough to start, loose enough to follow what actually happens.
The plan meets the room and the room wins. Your job is to read what's actually happening, not what you scripted, and steer with small, specific moves. Hold the timer. Surface the unsaid. Cut what's not landing.
The hour after the workshop is when the value either compounds or evaporates. Capture what surfaced, send the artifacts before momentum dies, and write down the one thing you'd do differently. Run enough sessions and the patterns become a craft.
Workshop tips picked for the rooms you actually run. Three times a week. No "10 tricks for hybrid" listicles, no synergy slides, no hot takes dressed as frameworks.
Start the conversation
Be the first to share your thoughts, experiences, or questions!