Designer onboarding

A skill for creating a practical onboarding guide for a designer joining a team that uses a design system. Output covers system philosophy, tooling setup, contribution norms, and a first contribution path — structured so a new team member can follow it without additional help.

Context

Onboarding documentation has a failure mode: it gets written for the person creating it, not the person reading it. It assumes context, skips steps that feel obvious to anyone who already knows the system, and leaves the new team member with a list of things to read rather than a path to follow.

The goal is an onboarding guide that a new designer could follow alone on their first day and feel oriented rather than overwhelmed. That means it has to be honest about what the system is and what it is not, explicit about where to get help, and structured so that early wins come before deep context.

Step 1: Gather the system context

Ask for or confirm:

• The design system name and the organisation or product context it serves
• The tooling stack: Figma library, documentation platform, component package, contribution tools
• The team structure: who owns the system, who the new designer's main contacts are
• The key contribution norms: what the process is for using components, raising gaps, and contributing new work
• Any known rough edges or caveats a new designer should know upfront