Product Designer onboarding plan
Designers need to learn the design system, the product's history and how design work moves into engineering. A small shipped improvement early builds trust faster than a big redesign proposal.
What good onboarding achieves
Deliver design work that fits the design system and ships through the team's process, grounded in user evidence.
Week one example
- Day 1: Design tool and file access; meet PM, engineers and design peers.
- Day 2: Walk through the design system and component library.
- Day 3: Audit a key product flow and note inconsistencies.
- Day 4: Review recent research and how insights are stored.
- Day 5: Pick a small improvement and present an approach to the team.
30/60/90 progression
- Day 30: Ships a small design improvement within the design system.
- Day 60: Leads design for a scoped feature including usability testing.
- Day 90: Owns design for a product area and contributes to the design system.
People to meet (examples)
- Design lead
- Paired PM
- Front-end engineers
- Research contact
Systems to learn (examples)
- Design tool (for example Figma)
- Design system documentation
- Research repository
- Issue tracker
Manager checkpoints
- Week 1: product audit findings
- Day 30: first shipped design
- Day 60: usability test review
- Day 90: area ownership
Common mistakes
- Starting with a redesign before learning constraints
- Not explaining the design-to-engineering handoff
- No access to real users or research
- Ignoring the existing design system
Checklist
- Design tool access
- Design system reviewed
- Key flow audited
- Research repository access
- Handoff process explained
- First improvement chosen
- Design critique ritual joined
- 90-day goals agreed