Free Template · 4 Weeks
30-Day PM
Onboarding.
Week-by-week activities for a PM joining a product team. Don’t propose changes in week one.
PM Name: ______
Start Date: ______
Manager: ______
Start Date: ______
Manager: ______
Most PM onboarding plans waste week 1 on tools and overload week 4 with deliverables. Flip it: weeks 1–2 are listening, weeks 3–4 are proposing.
Week 1
Listen. Read. Map.
- Read every customer signal from the last 30 days. Don’t skim — read.
- Map who owns what: who triages support? who reads sales calls? who reviews app reviews?
- Sit in on 3 customer calls (sales, CS, support). Take notes. No meetings.
- Read every PRD shipped in the last 6 months. Note patterns.
- Set up access: Slack, Jira, MindBacklog, Linear, support tools. Don’t configure — observe.
Week 2
Stakeholders. Constraints. Customers.
- 1:1 with engineering lead, design lead, CS lead, sales lead, founder. Ask: "what frustrates you about how product decisions get made?"
- Talk to 3 customers (different segments). Ask what they’d give us money to fix.
- Document the 5 biggest constraints (budget, headcount, tech debt, deadlines, dependencies).
- Identify the 3 product hypotheses everyone disagrees about.
- Don’t propose anything yet.
Week 3
Form a thesis. Stress-test it.
- Write a 1-page document: "What I’m hearing." Themes from signals + stakeholders + customers.
- Form 3 product hypotheses. Each must be falsifiable.
- Stress-test with each stakeholder individually. Update.
- Identify the 2 priorities you’d defend with evidence at a board meeting.
- Begin writing the first PRD — but don’t ship it yet.
Week 4
Propose. Commit. Ship the smallest thing.
- Present "What I’m hearing" to the team. Disagree-and-commit on direction.
- Pick the smallest thing to ship that proves a hypothesis. Ship it.
- Set up your weekly cadence: signal review, roadmap update, stakeholder briefing.
- Identify one process change you want to make. Discuss with manager. Don’t implement until day 60.
- Write a "Day 30" reflection: what you learned, what you got wrong, what you commit to.
The trap: proposing changes in week 1. New PMs do this to feel productive. It poisons trust. Listen first — for 14 days minimum — before you propose anything.