A 30-60-90 day plan is worth writing for one reason: it forces you to decide what each phase is for. Most of the ones people produce are lists of activities with dates attached, which is why they get written once, sent to a manager, and never opened again.
A plan that survives contact with the job has one property. Each phase ends in a decision, not an activity.
Days 1 to 30: understand, change nothing
The objective of the first month is information, not impact.
- A conversation with every person on the team, and with the people your team depends on.
- The expectations of your own manager, written down and confirmed back.
- A map of the work: what comes in, what goes out, where it queues.
- Your first impressions on paper, dated, so you can check them later.
Decision at day 30: what is the one constraint that limits this team, and is it a person, a process or a resource.
Days 31 to 60: install the basics
Now you act, but only on the operating system of the team, not on its content.
- Expectations stated explicitly: what good looks like, by when, for each role.
- A weekly rhythm that is predictable: one-on-ones, a team check, a closing point on Friday.
- The first real delegation, with the result specified and the method left alone.
- The first uncomfortable conversation, whichever one you have been postponing.
Decision at day 60: what am I still doing myself that somebody else should own, and who is going to own it.
Days 61 to 90: own the output
In the last phase you stop being assessed on how well you are adapting and start being assessed on what the team produces.
- The changes you wanted to make in week one, now that you know which were real.
- A view on each person that you could defend: strong, developing, or a problem you are going to have to address.
- Something delivered that would not have happened without you.
Decision at day 90: what does this team need in the next six months that it does not have today, and what are you asking for.
If you are writing it for an interview
A 30-60-90 plan asked for during hiring is a different document. You do not know the team, so specifics are guesses and interviewers can tell. What works there is showing the shape of your thinking: what you would want to learn first, what would make you act early, and what you would refuse to decide before day 60.
Confidence about a team you have not met is the most common way to fail that exercise.
Two failure modes
The plan that is all activity. Meetings scheduled, documents read, systems accessed. All of it can be completed without you learning anything. If a phase can be finished without a decision coming out of it, it is a schedule, not a plan.
The plan with a big win at day 30. Tempting, and it is how new managers end up fixing something that was not broken. The credible early win is a decision, not a launch.
Frequently asked questions
What is a 30-60-90 day plan for a new manager?
A plan for the first three months in a management role, split into three phases. A useful one ends each phase with a decision rather than a list of activities.
What goes in the first 30 days of a manager plan?
Information rather than impact: a conversation with every team member, your own manager’s expectations confirmed in writing, a map of how work moves through the team, and your first impressions recorded so you can check them later.
What decisions should each phase of the plan produce?
At day 30, the one constraint that limits the team. At day 60, what you are still doing yourself and who should own it. At day 90, what the team needs in the next six months and what you are asking for.
How is a 30-60-90 plan for an interview different?
You do not know the team yet, so specific actions are guesses and interviewers can tell. Show the shape of your thinking instead: what you would want to learn first, what would make you act early and what you would refuse to decide before day 60.
More on the phases themselves: your first 90 days as a manager.