Most companies either don't have one (the new hire is just expected to figure it out) or have one that's actually a job description in disguise. Neither works. The first leaves new hires drifting for weeks. The second turns the plan into a checkbox exercise that nobody references after week two.

A good 30-60-90 day plan is something different. It's a working document that defines what success looks like, sequences the new hire's ramp deliberately, and creates the structure for honest conversations between manager and report in the first quarter. Done well, it's the difference between a new hire who's contributing at month three and one who's still finding their feet at month six.

This article gives you the template and how to use it.

What a 30-60-90 day plan should do

Three jobs.

Set clear expectations for what success looks like. A new hire shouldn't have to guess. By the end of week one, they should know what their manager will use to evaluate them at 30, 60, and 90 days.

Sequence the ramp deliberately. New hires can't do everything at once. The plan should be explicit about what to focus on first, what to defer, and how the focus shifts over time.

Create structure for ongoing conversations. The plan isn't a contract. It's a basis for check-ins. Both sides reference it in 1:1s, surface concerns early, and adjust as new information emerges.

If your current 30-60-90 plans aren't doing these three things, the template below will help.

When to build the plan

Build it before the new hire starts. Share a draft in their first week. Finalize it together by end of week two.

A common mistake: building the plan after the new hire starts, in response to what they end up doing. That's not a plan, that's a record. The point of building it before they start is to be deliberate about what they should do, not retrospective about what they did.

A second common mistake: building the plan, sharing it once, and never referring to it again. The plan only works if it's a living document used in regular check-ins.

The template

Here's the structure to use. Keep it to one document, no more than two pages.

1. The role summary (5 lines)

A short summary at the top:

Role title
Reporting line
The outcome this role exists to drive
The 1-3 most important things about this role that the new hire should keep in mind from day one
Where their work sits in the broader team or company

This section connects to the job description and the requisition that opened the search. The plan shouldn't repeat the JD, it should distill it down to what matters most for ramping.

2. The 30-day plan: orientation

The first 30 days are about understanding the context. The new hire isn't expected to be productive in the conventional sense yet. They're expected to be absorbing.

What to focus on:

Meet [specific people] across the team, the company, and customer-facing functions
Understand [specific systems or processes] the role will operate within
Read [specific documents, repos, customer transcripts, or other context]
Shadow [specific work] before being asked to own it
Complete [any required training or compliance]

What success looks like at day 30:

The new hire can describe the team's current state, the most important active projects, and the key people involved
They have a working understanding of the tools, processes, and operating cadence
They've started forming a point of view about what could be done differently

What to NOT expect at day 30:

Significant independent output
Major changes proposed
Mastery of the role

A common mistake: filling the 30-day plan with deliverables. The first 30 days shouldn't have many deliverables. Loading them with outputs creates the wrong incentive: the new hire focuses on appearing productive instead of actually learning the context. Real productivity comes faster when the learning is solid.

3. The 60-day plan: early ownership

By day 60, the new hire should be starting to own specific things and contribute substantively, though still with active manager support.

What to focus on:

Take ownership of [specific projects or workstreams]
Build [specific relationships or working rhythms]
Begin [specific recurring work the role will own]
Start making proposals for [specific areas where their judgment will eventually drive decisions]

What success looks like at day 60:

The new hire is producing meaningful work output
They've established working relationships with the people they need
They've started forming and sharing opinions on the function or team
They're flagging questions and surfacing tensions to their manager regularly

What to NOT expect at day 60:

Full ownership of the role
Major strategic decisions
Major changes to processes or systems

4. The 90-day plan: full contribution

By day 90, the new hire should be operating at full contribution, with the work and decisions of the role fully theirs.

What to focus on:

Own [the full scope of the role]
Drive [specific outcomes the role exists to drive]
Build [a perspective on what should be different and a plan to do it]

What success looks like at day 90:

The new hire is fully ramped into the role
They're producing output at the level expected for the seniority
They've earned the trust to make decisions in their area without escalation
They've started identifying opportunities to improve the function

5. The check-in cadence

A short section defining how manager and new hire will use the plan.

A workable cadence:

Weekly 1:1, with the first 5 minutes referencing the plan: how's it going against this week's expectations?
Formal review at day 30 (30 minutes, structured)
Formal review at day 60 (30 minutes, structured)
Formal review at day 90 (60 minutes, structured)

The formal reviews are where you have honest conversations: what's working, what's not, what needs to change. Without these, the plan becomes background noise.

6. The early-warning section

Optional but useful. A short section naming what would constitute concerns at each stage.

Examples:

At day 30: significant gaps in understanding of the team or role that aren't closing
At day 60: persistent inability to execute on the work the role requires
At day 90: difficulty with the working relationships the role depends on

Writing these down doesn't mean they'll happen. It makes them easier to talk about if they do.

A complete example

Here's what the structure looks like in practice, for a hypothetical role.

30-60-90 Day Plan: Senior Product Marketing Manager

Reporting to: Alex Just, Head of Growth
Outcome this role exists to drive: Own product marketing across launches, positioning, and sales enablement, supporting our move from product-led to a more enterprise-aware GTM motion.
Most important things to keep in mind: We're a small team, so ownership matters more than process. Sales relies heavily on marketing-built collateral. Our customer base is in transition (SMB to mid-market) and our messaging has to keep pace.

30 days: orientation

Focus:

Meet all customer-facing leaders, three top customers (intro arranged), all engineering leads
Read all customer interview notes from the last six months
Shadow three sales calls, three customer success calls
Audit current marketing collateral and positioning materials
Sit in on weekly product roadmap meetings

Success at day 30:

Clear picture of current customers, ideal customers, and how the two compare
Working knowledge of the product roadmap
Initial perspective on what's working in current positioning and what isn't

60 days: early ownership

Focus:

Own positioning for our Q2 product launch
Build sales enablement for the launch (decks, one-pagers, FAQ)
Begin running weekly sync with sales leadership
Propose changes to our overall positioning, in writing

Success at day 60:

Launch positioning shipped on time, sales actively using the materials
Sales leadership rates the partnership as productive
Has a clear point of view on positioning evolution, ready to lead the conversation

90 days: full contribution

Focus:

Own the full product marketing function
Drive positioning evolution for the move upmarket
Build a 12-month roadmap for product marketing
Hire or contract for additional capacity if needed

Success at day 90:

Product marketing is a defined function with a clear owner, plan, and operating rhythm
Sales and product partner with product marketing as a peer function
A 12-month plan is approved and in execution

Check-in cadence:

Weekly 1:1 with Alex (Mondays, 30 min)
30/60/90 day formal reviews on calendar
Quarterly review at the 90-day mark

Early-warning indicators:

At day 30: no clear understanding of the customer transition, low engagement with cross-functional partners
At day 60: launch slipping, positioning work not landing with sales
At day 90: no clear plan or function, or relationships not in place to execute

How to use the plan well

Three habits.

Use it in 1:1s. Reference the plan in weekly 1:1s. Not as a checklist, but as a structure. "How are you tracking against what you'd expected by now?" or "I noticed [X] is harder than we'd assumed, do we need to adjust?"

Update it as you learn. The plan is a hypothesis, not a contract. If reality diverges from the plan in important ways, update the plan. Don't pretend it still applies.

Be honest in the formal reviews. The 30/60/90 reviews are the most valuable part. Treat them seriously. If the new hire is off track, say so directly. If they're crushing it, say that too. Vague positivity in the formal reviews is the single biggest reason 30-60-90 plans don't work.

What to do if the plan isn't working

Sometimes the plan reveals problems early. Take them seriously.

If the new hire is significantly behind by day 30: Have a direct conversation. Is the plan too ambitious? Are there gaps in onboarding support? Is the new hire struggling with something specific you can help with? Adjust and reset.

If the new hire is significantly behind by day 60: This is harder. Sometimes it's still recoverable with a clearer plan and direct conversation. Sometimes it's an early signal that the hire isn't going to work. Both are possible. Don't pretend you don't see what you're seeing.

If the new hire is significantly behind by day 90: Time for a hard conversation. Decisions about whether the role is the right fit are typically clearer by now. Acting on what you know early is better than dragging it out.

The plan doesn't cause problems. It just makes existing problems visible earlier, when they're easier to address.