The 30/60/90 Plan That Doesn't Make You Look Like a Try-Hard

New hire shows up Day 1 with a twelve-tab spreadsheet titled “30/60/90 Day Plan.”

Their manager reads it politely, says “great initiative,” and then spends the rest of the week quietly resetting expectations with the team.

The intent is good. The effect is usually not. A 30/60/90 written with zero context tells your manager three things, none of them flattering: you don’t know what matters yet, you’re optimizing for looking impressive, and you’re about to burn cycles on the wrong work.

A good 30/60/90 does the opposite. It’s short, drafted out loud, and built to be corrected. It’s an alignment doc, not a thesis.

What it’s actually for

One page. Four questions:

• What should I learn first?
• What does “good” look like by Day 30, 60, and 90?
• What work is valuable to this team right now?
• What do I need from my manager so I’m not blocked for three weeks?

Most onboarding is vibes-based. If your training so far has been a Slack channel and a prayer, you’re not imagining it. The 30/60/90 is how you make the implicit explicit before you waste a month.

Six rules that keep it from sounding try-hard

1. One page. Scrolling means you’ve drifted into thesis territory.
2. Ask for input. Don’t announce. Your plan is a draft. Say so.
3. Plain language. “Leveraging cross-functional synergies” is how you signal you’ve spent a year reading McKinsey decks. Don’t.
4. Tie it to team outcomes. Your manager cares what the team ships, not your self-improvement arc.
5. Include the help you need. Assumptions, tools, intros, approvals. The doc gets useful here.
6. Make learning a deliverable. “I can do X without hand-holding” counts.

The one-page template

Copy this. Fill in placeholders. Send.

**Role:** ___

**Team goal(s) this supports:** ___

**Manager's definition of success by Day 90:** ___

**Assumptions:** access, training time, approvals — ___

**Support I need:** tools, intros, data, examples — ___

**Check-in cadence:** ___

### Days 0–30: learn and de-risk
- Learn: onboarding, product, customers; "how we work" notes started
- Relationships: manager, buddy, key partners — each asked: "what does success look like at Day 30/60/90?"
- Deliver: one small useful output. One reference artifact.
- Signals of progress: fewer basic questions, faster turnaround, clear status

### Days 31–60: contribute, own a slice
- Learn: deeper domain knowledge in the two most relevant areas
- Deliver: one recurring task owned. One scoped project shipped with review.
- Risks: what might slow me down, and how I'll mitigate

### Days 61–90: operate and improve
- Deliver: one initiative led end-to-end. One proposed improvement with an ROI estimate.
- Quality bar: definition of "done," review steps
- Next: what I should own after Day 90

The email that gets a real answer

Yes, you have to send this. No, your manager is not going to spontaneously start coaching you.

Subject: Quick draft: 30/60/90 alignment (happy to adjust)

Hi [Manager],

I put together a one-page draft so I’m aiming at the right target early. Starting point, not a finished plan.

If you have a few minutes, could you tell me:

1. What should I change based on team priorities?
2. Anything here that’s not important right now, or wrong timing?
3. What would make you say “they’re ramping well” by Day 30?

Happy to revise after our next 1:1.

Thanks, [You]

On posture

Your plan is allowed to be wrong. Your job is to make it easy for your manager to correct it. That’s the whole game.

—

I’ve watched new hires sweat over a 30/60/90 for three days and produce a doc their manager skims for 90 seconds. The lesson isn’t that the doc doesn’t matter — it’s that the manager’s reaction is the actual artifact you’re trying to produce. Optimize the doc for the reaction, not the page.

For the Week 1 version of this, see the Week 1 Checklist. For the weekly rhythm that sustains it, steal the Status update template.