30-60-90 Day Plan for New Hires: A Manager's Guide

What a 30-60-90 day plan is, and who writes it

Search for a 30-60-90 day plan and most results are written for job candidates who bring one to an interview. This guide covers the other version: the plan a manager prepares for someone who has already accepted the offer. The candidate's plan is a pitch. The manager's plan is a commitment about the first three months: what the new hire will learn, who they will meet and what they will deliver.

That makes the plan a realistic preview of the job, given after the hire rather than before it. A meta-analysis of 52 studies found that realistic job previews reduce voluntary turnover mainly by signalling that the organization is honest with its people, and that a written or spoken preview delivered after hiring may be the most effective design.^[1] A plan with concrete milestones is exactly that kind of preview.

Why the first 90 days carry so much weight

Research on how newcomers settle in points to three signs of a good start: the person knows what is expected of them (role clarity), believes they can do the work (self-efficacy) and feels accepted by the team (social acceptance). A meta-analysis of 70 samples found that these three measures carry the effect of onboarding practices through to job satisfaction, commitment, performance, intention to stay and turnover.^[2]

Expectations matter just as much. In a meta-analysis of 31 studies covering more than 17,000 people, the degree to which a job matched what new hires expected was related to their satisfaction, commitment and intention to leave.^[3] A manager who spells out the first three months leaves less room for a gap between the job people imagined and the one they found.

Practitioner data points the same way. In a 2025 survey of 1,000 HR leaders in the US, the UK and Australia by the onboarding software vendor Enboarder, one of the top reasons HR leaders gave for departures within 90 days was a mismatch between job expectations and reality (30.3%). The same survey found that 44.8% of organizations provide only general guidelines for a 30-60-90 day plan.^[4]

A 30-60-90 day plan works on all three signs at once: milestones make the role clear, early wins build confidence, and relationship milestones turn introductions into part of the job instead of a matter of luck.

Three phases: learn, contribute, own

The three phases are not equal blocks of work. The first is mostly input, the last is mostly output, and the balance shifts in the middle. The diagram shows how responsibility moves from the manager to the new hire across the 90 days.

The first 90 days

Responsibility moves from the manager to the new hire

Days 1-30: learn

The goal of the first month is context. The new hire learns the product, the customers, the tools and how decisions get made, and meets the people they will depend on. Delivery goals stay small and safe: one task that can be finished with help and that shows how work flows through the team. The manager is the most active person in this phase, opening doors and answering questions.

Days 31-60: contribute

In the second month the new hire takes on real work with support close at hand. They own tasks instead of shadowing them, ask for review before shipping and start to share their own observations. Someone new notices friction the team has stopped seeing, so this is a good moment to ask for a short written list of what looked odd.

Days 61-90: own

By the third month the new hire owns a defined piece of work end to end: a customer portfolio, a process or a component. Support moves from daily to weekly, and the conversation shifts from what they are learning to what they are delivering and what they would change. The day-90 review closes the onboarding plan and opens the person's regular goals.

Three kinds of milestones in every phase

Each phase needs milestones of three kinds. Learning milestones cover what the person has to understand, relationship milestones cover who they need to know and work with, and delivery milestones cover what they produce. A plan with only delivery goals turns onboarding into an exam. A plan with only learning goals leaves the new hire with nothing to show at day 60.

Every milestone needs an observable result (something a third person could check), an owner and a date. "Understands our pricing" is not observable. "Explains the three plans and their limits to a colleague without notes" is. The table shows an example plan for a customer success specialist.

The manager drafts the plan before day one. In the first week, the manager and the new hire go through it together and fix whatever is unrealistic or missing. The new hire should leave that meeting able to say, in their own words, what success at day 90 looks like.

Day zero: what has to be ready before the first morning

The plan starts before the new hire arrives. Anything that is not ready on the first morning eats into the first week, and the first week sets the tone for the ones after it.

• Accounts, equipment and access to every tool the plan mentions.
• A written draft of the 30-60-90 day plan, shared on day one.
• The first week's calendar, including the introductions from the relationship milestones.
• A buddy outside the reporting line who can answer the questions people hesitate to ask their manager.
• The weekly one-on-one booked for all 90 days.

Weekly one-on-ones and the day 30, 60 and 90 reviews

The plan moves forward in weekly one-on-ones. Half an hour is enough: which milestones are done, which are stuck, what the new hire needs and what they have noticed. As with OKR check-in meetings, the value comes from regularity, not from length.

At day 30, 60 and 90 the manager holds a longer review. The SHRM Foundation's onboarding guidelines recommend checking in on progress at milestones such as 30, 60, 90 and 120 days, and up to a year after the start date.^[5] Each review looks back at the milestones of the phase, agrees what carries over and sets the next phase's milestones in more detail. The day-90 conversation is not a formal performance review: it closes the onboarding plan and hands the person over to the regular goal and feedback cycle.

A short pulse survey alongside each review gives the new hire a second channel. Three to five questions are enough, for example:

• Did the training and information you received this month help you do your job?
• Are you getting the support you need from your manager?
• Do you feel part of the team?
• Can you see yourself working here a year from now?

The manager should not be the only voice. By day 60 a new hire has worked with several colleagues, and asking two or three of them for short feedback gives a fuller picture than one person's impression. This matters most when the review also decides whether the employment continues.

Line up the reviews with the probation period

Many contracts start with a probation period during which either side can end the employment on shorter notice. Its length depends on local law and the contract, and it often does not match 90 days.

Check the date before writing the plan. If the probation period ends before day 90, the review closest to that date becomes the probation decision, and it has to happen early enough to act on. Put that review in the plan with its real date, tell the new hire which conversation it is, and collect feedback from colleagues before it rather than after.

A 30-60-90 day plan is not an OKR

Both use goals and dates, so the two are easy to confuse. OKRs describe what the organization wants to change this quarter. Teams and individuals write their own OKRs too, and a good share of them come bottom-up, but they are all aligned by how they contribute to the company's strategy. A 30-60-90 day plan describes how one person becomes productive in a new role: it tracks getting up to speed, not a business outcome for the quarter. That is why most of its milestones, such as meeting the support lead or learning the pricing model, would make poor key results.

The two meet at the end of the plan. The delivery milestones of the third phase are often the new hire's first contribution to a team objective, and the day-90 review is a natural point to write their first OKRs together with the manager. From then on, the weekly one-on-ones that carried the onboarding plan carry the person's goals and feedback.

Where 30-60-90 day plans usually go wrong

• Copying a generic template. A plan that would fit any role makes no role clear. Write milestones for this job, this team and this quarter.
• Only delivery goals. Without learning and relationship milestones, the plan becomes a performance test from the first day.
• Milestones nobody can check. "Gets familiar with the codebase" cannot be reviewed. "Ships one small fix through code review" can.
• Writing it alone. A plan the new hire has never discussed is the manager's expectation, not a shared one.
• Letting the reviews slip. When the day-30 review moves to day 45, the plan loses its dates and turns into a wish list.
• Stopping at day 90 with nothing next. The plan should end with the person's regular goals in place, not with silence.

A good 30-60-90 day plan is short, specific and shared. It tells the new hire what the first three months hold, gives the manager a reason to talk every week, and turns the first quarter in a new job into something both sides can see and adjust.