# Pmjob 30 60 90 Plan

> Draft a first 30-60-90 day plan for a new product role, producing the people to meet and the three questions for each, what to learn before changing anything, one modest early result by day sixty, the proposal you will bring by day ninety, and week one questions for your manager, with every assumption tagged by source. Use for "run pmjob-30-60-90-plan", "write my 30-60-90 day plan", "first ninety days in a new role", "what would you do in your first 90 days", "I start in three weeks", "onboarding plan for a new product role", "one page plan for the final round", part of the Claude Guide for Product Interviews Pack by 90n.

- Skill: `polar-bear-org/pmjob-30-60-90-plan` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/pmjob-30-60-90-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/pmjob-30-60-90-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/pmjob-30-60-90-plan

---


# 30-60-90 Day Plan

## When To Use
You start in three weeks and want to arrive with a plan instead of a blank calendar. Or a final round asks what you would do in your first ninety days. This answers the question: what will I learn first, from whom, and what can I honestly commit to before I have seen the inside?

## When Not To Use
Not for gathering facts about the employer: Company Research Brief does that, and this plan reads it. Not for the questions you put to interviewers: Questions to Ask covers those. If the role is not yet agreed, a one page version is enough.

## Inputs
- The job ad and what you heard in the loop about the role, the team and the first priorities
- Your Company Research Brief, if you have one
- The start date, who your manager will be by role, and whether this is for your first day or a final round
If you have none of this, I start from the role title and what you were told in your last conversation, and mark the output as a first draft.

## Approach
Listen, then contribute, then propose: a common onboarding order with no single originator. The judgment is that an experienced hire is trusted faster for what they asked in month one than for what they changed in month one. So the first thirty days are built around people and definitions, the early result is chosen with the manager, and a point of view arrives only when it has something to rest on. The failure this prevents is the confident ninety day plan written from outside, which tells a team what is wrong with a product before its author has met a single user of it.

## Workflow
1. I ask up to three questions: is this for the first day or for a final round; what you were told about the role's first priorities, and by whom; and what you already know about the team and the product against what you are guessing.
2. Days 1 to 30, listen. A list of people to meet by role: your manager, peers in product, design, engineering and data, and a few users or the people closest to them. Each gets the same three questions: what is working, what is not, what would you want from this role. Asking everyone the same three makes the answers comparable.
3. What to learn before changing anything: the users, the product as it is, the numbers and how each one is defined, and how decisions get made. Each line names where you will find it out.
4. Days 31 to 60, contribute. One modest early result, chosen with your manager, small enough to finish and useful to someone else. Not a reorganisation and not a new process.
5. Days 61 to 90, propose. A point of view on your area, what it rests on, and a first proposal for the next quarter.
6. Tag every assumption about the company with its source (the ad, the loop, the Company Research Brief) or "guess", and add the week one questions for your manager: what a good first ninety days looks like to them, what to leave alone, who to meet first, how they like to be kept informed.
7. For a final round I cut it to one page that leads with what you would learn first and why, and says plainly what you cannot know yet. Claude Docs can hold the plan as a document you keep editing.

## Output Format
```markdown
# 30-60-90 Day Plan
Draft, revise after week two. Role: [role]. Start date: [date]. Version: [first day or final round]
## Assumptions
| Assumption about the company or role | Source (ad, loop, research brief) or guess |
|---|---|
| [assumption] | [source, or guess] |
## Days 1 to 30: listen
| Who (by role) | What is working | What is not | What they want from this role | Met on |
|---|---|---|---|---|
| [role] | [to ask] | [to ask] | [to ask] | [date] |
Learn before changing anything: [users, the product as it is, the numbers and their definitions, how decisions are made], each with [where you will find it out].
## Days 31 to 60: contribute
[One modest early result, agreed with your manager on [date]: what it is, who it helps, how you will know it is finished.]
## Days 61 to 90: propose
[Your point of view on the area, what it rests on, and the first proposal for the next quarter.]
## Week one questions for your manager
[What a good first ninety days looks like to them; what to leave alone; who to meet first; how they like to be kept informed.]
## Decision
You decide [what to share with your manager, or which version to take into the final round] by [date], and you revise the plan on [date after week two].
```

## Done When
- The plan is marked "draft, revise after week two" at the top
- Every assumption about the company has a source or the word "guess"
- The first thirty days hold more questions than actions, and the early result is one thing, small enough to finish
- The final round version fits one page and says what you cannot know yet

## Quality Bar
- Future colleagues appear by role, and nothing judges the current team or the person who held the role before you.
- No metric, target or finding about the company is filled in; unknown values stay as [placeholders].
- In a final round you present and defend the plan yourself, and you say what you used AI for if asked.
- The plan is your draft from what you really know: guesses are marked as guesses and nothing about the company is invented.

## Next
Run pmjob-experience-inventory (Career Evidence Inventory) to keep the evidence rows going in the new role.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

