Skill: onboarding-plan

Skill: onboarding-plan

Purpose

Create a structured 30/60/90-day onboarding plan for a new team member joining a delivery team — so they ramp up fast and contribute confidently.

When to Use

• New developer, QA, designer, or PDM joining the team
• Contractor or vendor resource starting
• New PDM inheriting an existing programme

Framework: 30/60/90-Day Onboarding Plan

Step 1 — Gather Context

Ask for:

• Role and seniority
• Current project / release state
• Key people they need to know
• Tools and systems they need access to

Day 1–5: Access and Orientation

Goals: Set up, oriented, and welcomed

• Accounts created: Jira, Confluence, Slack, GitHub, etc.
• Intro meetings: Team, PDM, Tech Lead, QA Lead
• Read: Team charter, working agreements, DoD
• Shadowed: one standup, one sprint planning or sync meeting
• Assigned: one low-complexity buddy task

---

30-Day Goals: Learn the System

Goal	How	Done By
Understand current release scope	Read release plan + dependency map	Day 10
Know the tech stack	Tech Lead walkthrough	Day 15
Contribute first task independently	Low-complexity story	Day 20
Know who to go to for what	RACI + 1:1s with key people	Day 30

---

60-Day Goals: Contribute Reliably

Goal	How	Done By
Own a sprint story end-to-end	Sprint assignment	Day 45
Participate in Three Amigos	Join session	Day 50
Flag blockers independently	Daily standup	Ongoing
Complete onboarding feedback	Survey	Day 60

---

90-Day Goals: Operate Independently

Goal	How	Done By
Contribute to sprint planning	Active participant	Day 75
Identify one process improvement	Retrospective	Day 90
1:1 progress check with PDM	Review goals	Day 90

Check-In Questions (30/60/90 Reviews)

1. What's going well?
2. What's unclear or confusing?
3. Where do you feel least confident?
4. What would help you most right now?

Output Format

1. Day 1–5 checklist
2. 30/60/90-day goal table
3. Check-in question set
4. Suggested next command: /working-agreements or /raci-matrix