PM First 90 Days Template

A free first-90-days template for product managers starting a new role — week-by-week structure, stakeholder map, and an early-wins log built in.

A week-by-week structure for starting a new PM role — learn, align, deliver — with a stakeholder map and an early-wins log built in.

Preview of the first 90 days template showing the three-phase structure with stakeholder map and early wins log
Three phases — learn (0–30), align (30–60), deliver (60–90) — with the stakeholder map and early-wins log that make each phase concrete.
Download the PM First 90 Days Template

Week-by-week checklists, stakeholder map, point-of-view worksheet, early-wins log. No email required.

What's inside

The failure mode in a new PM role isn't moving too slowly — it's shipping opinions before earning context. The counter-failure is staying in "listening mode" so long you become furniture. The template splits the difference across three phases:

  • Days 0–30: Learn. Stakeholder interviews (same three questions each: what's working, what's broken, what should I not break), raw customer exposure, and a one-page "what I've learned" memo that shows momentum without shipping anything.
  • Days 30–60: Align. A point-of-view worksheet — the top 3 problems worth solving and the 2–3 things you're deliberately not touching yet — socialized 1:1 before any group setting.
  • Days 60–90: Deliver. Ship one real deliverable, close the loop with every week-1 interviewee ("here's what happened with what you told me" — nobody does this, everybody remembers it), and review the early-wins log with your manager.

Plus two structural tools that persist beyond the 90 days: a stakeholder map (who owns what, what they told you, what they need from you) and an early-wins log with a "who can confirm it" column.

How to use it

  1. Start the impact log on day one, not day ninety. The habits you set in the first two weeks are the ones that survive — and your first review cycle will be built from this record. The early-wins log uses the same structure as a brag document, so it graduates directly into your permanent one.
  2. Do the stakeholder interviews before forming opinions. The map isn't a formality — the "what they need from me" column is your first-quarter roadmap of relationships.
  3. Write the day-30 memo even if nobody asked for it. It forces synthesis, and it's the cheapest credibility you'll ever buy.
  4. Log the win with its collaborators while it's fresh. Day-45 details are gone by day-120.

New role, new system

A new job is the one moment your documentation habits reset — for better or worse. Most PMs restart the doc, keep it for three weeks, and lose it by month two.

Prodlog is built for exactly this moment: log from Slack or the browser as things happen, get early wins verified by your new collaborators (which doubles as relationship-building), and walk into your first review with a complete, confirmed record. See a sample or start free at prodlog.app.

Get the template

Free download — three phases, stakeholder map, early-wins log.