Product Manager onboarding plan
A new PM's credibility depends on understanding customers and the team's constraints before proposing anything. Onboarding should front-load customer exposure and stakeholder context.
What good onboarding achieves
Own a product area's roadmap with a clear view of customer problems, engineering constraints and business goals.
Week one example
- Day 1: Meet the team, manager and engineering lead; access product tools.
- Day 2: Use the product as a customer would; note friction.
- Day 3: Read recent customer research and support themes.
- Day 4: Review current roadmap, metrics and recent decisions.
- Day 5: Join customer calls and the team's planning ritual.
30/60/90 progression
- Day 30: Can explain the area's customers, metrics and current priorities.
- Day 60: Runs discovery on one problem and writes a first spec with the team.
- Day 90: Owns the area roadmap and stakeholder communication.
People to meet (examples)
- Head of product
- Engineering and design leads
- Sales and customer success contacts
- Data or analytics contact
Systems to learn (examples)
- Product analytics tool
- Issue tracker or roadmap tool
- Research repository
- Design tool
Manager checkpoints
- Week 1: product walkthrough notes
- Day 30: customer and metrics summary
- Day 60: first spec review
- Day 90: roadmap review
Common mistakes
- Proposing roadmap changes before talking to customers
- Not learning past decisions and why they were made
- Skipping relationships with sales and support
- No access to data in the first weeks
Checklist
- Product tools access
- Product used end-to-end
- Research and support themes reviewed
- Roadmap and metrics reviewed
- Three customer calls joined
- Stakeholder intros done
- First discovery problem chosen
- 90-day goals agreed