Using the System helps people understand how to work with the design system in practice. It provides orientation, sets expectations, and routes different roles to the right level of guidance so they can start using the system with confidence.
This is a people-facing entry point. It does not explain how the system is built. It helps people understand what the system does, how it supports their work, and where to go next.
Steps
-
Define the orientation goal
Decide what someone should understand after their first interaction with the system. Focus on clarity, context, and expectations rather than completeness.
-
Explain what the system is and is not
Provide a short overview of the system's purpose, scope, and boundaries so people form the right mental model before going deeper.
-
Set expectations for usage
Clarify how opinionated the system is, what people are expected to follow, and where flexibility exists. Keep this high level and role-agnostic.
-
Route people to the right depth
From this entry point, route people based on how they interact with the system:
- Designers → Interactive Designer Onboarding for hands-on, example-led learning
- Engineers → Developer Onboarding for implementation guidance, behaviour, and constraints
- Other roles → integrate guidance directly into the Getting Started content, such as a documentation page, internal wiki, Slack bookmark, or short video with links
-
Signpost support and next steps
Make it clear where people can find documentation, guidance, or help if they get stuck, and how learning continues as the system evolves.
-
Review and refine
Use feedback and recurring questions to improve clarity, routing, and expectations over time.