A 30-60-90 plan tells a new hire what to do and when it's due. It doesn't explain why anything is the way it is: who owns what, why decisions were made, or what's already in motion. Keep the plan. Add the context beside it. That context is already written down, mostly in Slack.

What does a 30-60-90 plan actually tell a new hire?

Three things, and it tells them well.

  1. What to do. Meet these people. Finish this training. Shadow these calls. Ship one small thing.
  2. When. By day 30, by day 60, by day 90.
  3. How they'll be judged. A set of milestones a manager can check at each mark.

That's useful. A new hire with a 30-60-90 plan knows what a good first quarter looks like, and a manager has something to hold the conversation around. Nobody should throw the plan away.

Look at the verbs, though. Meet. Review. Shadow. Learn. Understand. Every line is an instruction to go and find something out. The plan is a list of research assignments with due dates.

What can't it tell them?

Anything they'd find out by doing the assignments.

"Review your accounts" doesn't say which account is fragile or why. "Meet the engineering leads" doesn't say which of them owns the service that keeps breaking. "Understand our pricing" doesn't say that pricing changed last spring, that two customers were grandfathered, and that the reason is in a thread.

So the new hire does what the plan says. They review, meet and ask. Each answer comes from a person who stops what they're doing to give it. The plan has turned one person's onboarding into a small tax on the people around them.

Gallup found that 29% of new hires say they feel fully prepared and supported to excel in their role after their onboarding experience. Most of the rest had a plan. They finished it on time.

That isn't a failure of the template. A template can only hold what's the same for every hire. The why is different for every team, and it changes every quarter.

Keep the plan, add the context

The plan is the schedule. What's missing is the reading that should come with it. That reading has three layers.

Put the two side by side and each line of the plan gets easier. "Review your accounts" becomes a check on something they've already read, not a dig. "Meet the engineering leads" becomes a conversation, not an interview.

Keep the checklist too. The checklist makes sure nothing is missed, the plan sets the pace, and the context explains what any of it is for. Firstweek vs. an onboarding checklist covers that pairing.

What does a better 30-60-90 look like?

The same plan, with one section finished that is usually left blank.

Every 30-60-90 template has a role-specific part: the context for this team and this job. It's the manager's to fill in. Here is what doing it properly involves:

  1. Read back through the team's channel for the decisions that still matter.
  2. Pull the history on each account or system the new hire inherits.
  3. Work out who really owns what, as opposed to who is listed.
  4. Write it up so someone new can follow it.
  5. Check it's still true.

That is three hours for a manager who knows the team well, and they don't have three hours. So the section gets a few bullet points the night before, or the note "we'll cover this in our 1:1s".

A manager approves it in ten minutes, instead of the three hours they were never going to spend. That's the version worth aiming for: the manager's knowledge is still what makes the document right, but their part is reading and correcting, not researching and writing.

If you're doing it by hand, the onboarding document template gives you the headings. Fill in the team and role layers for your next hire and attach it to the plan.

Where does the missing context already live?

In the tools the team uses every day.

Nothing needs to be invented. It needs to be read in order and written up for one person.

That is what Firstweek does. It reads those tools through read-only connections and writes each new hire one onboarding artifact covering the company, the team and the role. Every claim links to the thread, page or record it came from. The hiring manager approves it before day one. The 30-60-90 plan stays as it is, and the new hire arrives having read what the plan assumed someone would tell them.

Until then, the new hire is on payroll asking. The onboarding cost calculator puts your own numbers on those months, and the sample artifact shows what the reading looks like.

FAQ

Is a 30-60-90 plan enough to onboard a new hire?

It covers what to do and when. It doesn't cover who owns what or why things work the way they do, so new hires get that by asking. Keep the plan and add written context beside it.

Which HR tools include a 30-60-90 template?

Many HR platforms include one alongside their checklists. Rippling, for example, produces a checklist and a generic 30-60-90 template. That's the right tool for the schedule.

What should a manager add to a 30-60-90 plan?

The team and role context: who owns what, the decisions behind how the team works, and the history of whatever the new hire is inheriting.

Does Firstweek replace the 30-60-90 plan?

No. Keep the plan and the checklist. Firstweek writes the context they don't hold.

Sources: Gallup, 8 Practical Tips for Leaders for a Better Onboarding Process (2021), listed with its link on the onboarding statistics page.

Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.