The 30-60-90 day plan for new roles

A 30-60-90 day plan sounds like the kind of thing you hand to HR during onboarding and never look at again. That version is mostly for show. The version that actually helps is the one you build for yourself in week one and update every two to three weeks as you learn what’s actually true.

Most people start a new job and operate on vibes for the first three months. The 30-60-90 plan is vibes with structure. It forces you to make explicit decisions about where you’re going to put your energy, and it gives you something concrete to evaluate against when the inevitable reorientation happens in week six.

What a 30-60-90 plan actually is

A 30-60-90 plan is a prioritized list of what you’re trying to accomplish in each of the three phases of a new role. Day 30 is usually about orientation: learning the landscape, the people, the tools, the norms. Day 60 is about starting to contribute: understanding the problems deeply enough to start working on them. Day 90 is about demonstrating impact: shipping something, earning trust, starting to own a domain.

Each phase builds on the last. If you skip the orientation phase and jump to contribution too fast, you’ll contribute in the wrong direction and have to redo work. If you stay in orientation too long, you’ll seem passive and your manager will start to wonder when you’re going to be useful.

What your manager is trying to do with this plan

Your manager wants to know you’re oriented. They want to trust that you have a plan for your own ramp. A well-constructed 30-60-90 tells them you’ve thought about the structure of the first three months and you’re not going to need their hand on your back through every decision.

The managers who get frustrated with new hires in the first 90 days are usually frustrated because they don’t know what the new hire is doing or where they’re going. A visible plan removes that ambiguity. Even if the plan changes (and it will), having one signals that you’re managing your own onboarding.

What a strong plan looks like vs. a weak one

A weak 30-60-90 is a list of tasks: “Schedule 1:1s with team, complete onboarding modules, review the product roadmap.” These are things you’d do regardless. They’re not goals. They’re minimum viable activities.

A strong 30-60-90 has goals, not tasks, at each phase. The goal for day 30 isn’t “schedule coffee chats.” It’s “understand the three biggest open questions on the team and know who’s working on each.” The goal for day 60 isn’t “start contributing.” It’s “have a first draft of the [specific thing] ready for review.” The goal for day 90 isn’t “feel settled.” It’s “have shipped or substantially driven [specific outcome].”

The test: would your manager be surprised if you said you’d achieved this goal at the end of the phase? If the goal is so easy it’s just assumed, it’s a task, not a goal.

The template

Share this with your manager at the end of week one. Not as a finished document, as a starting point for a conversation. “Here’s my current thinking on my first 90 days, does this match your expectations?” is a better opener than “I made a plan,” because it invites correction, which you want early.

The thing that will definitely change

The day-60 and day-90 sections will be wrong. You’ll learn something in week three that changes your priorities in month two. That’s expected. The plan is a calibration tool, not a contract.

What you should update every two to three weeks: the “questions to answer” list and the “success signals.” Cross off the questions you’ve answered. Add the new ones that appeared. As the plan changes, you’re building a record of how your understanding evolved, which becomes useful when your first performance cycle comes around and you need to reconstruct the arc of your first quarter.

Further reading

• First 90 days boot sequence
• The first 90 days OS: your boot sequence and why day 1 is already late
• 30-60-90 plan: not try-hard