Fjob 30 60 90 Plan

---
name: fjob-30-60-90-plan
description: Drafts your 30 60 90 day plan, with understand by 30, contribute by 60 and own a piece by 90, the people to meet, skills to build, checkpoints and the support you need, as a draft for your manager to change. Use for "run fjob-30-60-90-plan", "30 60 90 day plan", "plan for my first 90 days", "first three months plan new job", "show my manager I have a plan", "what should I do in my first month", "graduate 90 day plan", part of the Nail Your First Job with Claude Pack by Polar Bear.
---

# 30 60 90 Day Plan

## When To Use
You want to show your manager you have a plan, not just turn up. Use it in your first week or two, once you have met your manager and seen roughly what the team does. It answers one question: what should be true at day 30, day 60 and day 90, and what do I need to get there?

## When Not To Use
If your manager already handed you a written plan, do not write a rival one; turn theirs into goals with First Goals Draft. If you only need to sort this week's tasks, use Weekly Plan.

## Inputs
- Your role title, start date, team and manager (as [manager] if you prefer)
- What you were told the role is for, in your own words, plus any job description or welcome note your policy lets you share
- What you have learned so far: who you met, the tools, the work you have seen
If you have none of this, I start from your role title and start date and mark the output as a first draft built on assumptions.

## Approach
The 30 60 90 day plan is a practitioner convention with no single public originator. The honest shape of most first jobs is understand by 30, contribute by 60, own one piece by 90, and each stage is written as what will exist or be true at the end, not a list of activities. The failure it prevents: a plan written before you met anyone, promising "deliver three projects by day 60", which your manager reads as either naive or a guess. So every assumption is marked, and the header says it is a draft to discuss.

## Workflow
1. Ask at most three questions: what does your employer's AI policy allow for this, and which Claude account are you in (work-provided plan or personal)? What did your manager say the role is for? When is your probation or first review, if you know? If team priorities or internal goals are involved and your policy or account does not allow them, I write the plan in general terms and you fill the details by hand; for anything internal, run Data Check Before You Paste first.
2. Day 30, understand: the people, the customers or users, the processes and the tools. Write what will be true ("I can explain how a request reaches our team and where it goes next"), not "attend meetings".
3. Day 60, contribute: one or two first real deliverables you do with support. Name the support (who reviews, who you shadow).
4. Day 90, own: one piece of work you run end to end. Check it against the ramp: if only someone with years in the team could do it comfortably, cut it back to a piece you can learn your way into.
5. For each stage add people to meet (by role and the reason, never a judgment of the person), skills to build, the checkpoint (date and who) and the support you need (access, intros, time).
6. Add a checkpoint prep line per stage: what you will bring to that conversation. Mark every assumption with [assumption], and keep the plan in a Project or a plain chat (works on the Free plan); Claude Docs (beta) is optional if you want to edit it as a document.

## Output Format
```markdown
# 30 60 90 Day Plan
Draft for discussion with [manager], [date]. Assumptions marked [assumption].
## Stages
| Stage | What will exist or be true | People to meet (role, why) | Skills to build | Checkpoint (date, who) | Support I need |
|---|---|---|---|---|---|
| By day 30, understand | [outcome] | [role, reason] | [skill] | [date, manager] | [access, intro] |
| By day 60, contribute | [outcome] | [role, reason] | [skill] | [date, manager] | [review, time] |
| By day 90, own | [one piece of work] | [role, reason] | [skill] | [date, manager] | [support] |
## Checkpoint prep
- Day 30: [what I will bring: done, learned, support missing]
- Day 60: [what I will bring]
- Day 90: [what I will bring]
## Assumptions to check
1. [assumption and who can confirm it]
## Decision
[Manager] changes and agrees the plan at our next 1:1 on [date]; I update it the same day.
```

## Done When
- Every stage states an outcome, not an activity
- Day 90 names one piece of work, sized for a new starter
- Every checkpoint has a date and a person
- Assumptions are marked and the header says draft for discussion

## Quality Bar
- Outcomes you can see at the end of the stage, not hours or attendance
- People appear by role and reason only, never as a description of who they are
- No internal detail goes in unless your policy and account allow it
- No stage asks for what only a tenured colleague could do comfortably
- A draft for your manager to change; no outcome you cannot honestly reach, and no promise about what it leads to.

## Next
Run fjob-first-goals (First Goals Draft) to turn the plan into goals your manager agrees.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).