Prepare before day one
- Access to design files, code repositories, analytics, and the issue tracker.
- A short brief: product, users, goals, and the current top priorities.
- Links to past research, brand and design system guidelines, and key decisions.
- A named contact who can answer questions quickly.
A five-day plan
Context
Product walkthrough, goals, and introductions. Share the roadmap.
Users and data
Review research and analytics. Watch a few recorded sessions or calls.
Systems and process
Learn the design system, the handoff process, and engineering conventions.
A first small task
Take a real ticket. Pair with an engineer or designer.
Review and adjust
Demo the work, collect feedback, and agree how to work together.
Set the working rhythm
| Ritual | Purpose |
|---|---|
| Daily standup or async update | Keep work visible and unblock quickly |
| Weekly design review | Give feedback early and align with product and engineering |
| Shared channel | Fast questions and decisions |
| Monthly retro | Improve how the team works together |
Remove friction
Common blockers include slow access requests, unclear ownership, and missing documentation. Treat the first week as a test of your own onboarding. Every question the new team asks tells you something you should write down.
Treat them as part of the team
Invite them to planning, demos, and customer calls where possible. Context is what lets an external designer make good decisions on their own, which is what you hired them for.



