The 30-60-90 Day Plan for a New Manager (With the Handoff Built In)

A new manager's first 90 days usually generate a lot of meetings and move almost no work. A 30-60-90 day plan fixes that when you write it as a handoff schedule instead of an activity list: 30 days to learn how the work runs, 60 to run one process, 90 to own it outright. Most 30-60-90 day plan templates track what the new manager reads. The one that works names the processes changing hands and when.

What Is a 30-60-90 Day Plan?

A 30-60-90 day plan is a written schedule of what a new manager learns, runs, and owns across their first three months, with a checkpoint at each 30-day mark. Written that way it is a transfer document: which work leaves whose desk, in what order, and the test at each gate.

Most versions are not that. They are activity lists: meet the team, review the numbers, build relationships, propose improvements. Every line is defensible and none proves anything moved. If your plan does not name a process that changes hands, it is a calendar with three headings.

Day-one logistics belong elsewhere: access, equipment, payroll, and the company card new hires sometimes wait three weeks for all run on a 90-day new hire onboarding checklist. This plan assumes the laptop already works.

Write It With the Owner, Not for the Owner

The plan gets written by two people in one sitting: the one handing work off and the one receiving it.

Owners tend to write it alone and present it, which is how a good plan lands badly. An electrical contractor's board advisor called that an operating system arriving like Moses down from the mountain. His fix was a sticky pad: everyone writes one idea, the room keeps, kills, and combines, and the owner leaves with the team's fingerprints on his plan.

The rule we use with clients is the one we use on documentation: one person drafts the first 80 percent, then the people who do the work tear it apart. Committees draft badly and correct well. The owner drafts the handoff list, the new manager rewrites it in week one, and both sign the same page.

If the owner has already run the Delegate and Elevate exercise, the bottom two quadrants are your first draft.

Days 1 to 30: Learn the Real Process, Not the Org Chart

The first 30 days are for finding out how the work is really done, which is rarely what the org chart says.

A residential cleaning COO asked us early on whether we needed her org chart, because she had built her documentation around it and that was not how the company worked. Months lost.

So month one is spent beside the people doing the work, not the people describing it. Watch a real run, ask what gets in the way, and treat frustration as data.

What month one produces is not a report. It is a list: every process the role touches, who really runs each, and which ones live only in somebody's head.

A manager who has not sat beside a practitioner by day 30 is behind, whatever the calendar says.

Days 31 to 60: Run One Process End to End

In month two the manager stops watching and runs one process, with the current owner watching.

For every process we capture three things: the purpose (why it exists and who it affects), the decision points (the forks where the right call depends on context), and the step-by-step from the person doing the work. Those three double as a transfer test: the manager owns it once they can state the purpose, name the decision points, and run the steps unaided.

A manager who can run the steps but cannot name the decision points has memorized a job, not learned one.

Every correction that surfaces this month goes into the document, not into a verbal aside, and in a form the next person can use: training documentation written for the person on day three, not notes only their author can read.

Processes are bigger than they look: one outgoing bookkeeper needed 85 minutes just to describe a single weekly commission run. Budget two to four hours per process.

Pick one process for month two, not five.

Days 61 to 90: Take the First Thing Off the Owner's Plate

Month three has one job: one process leaves the owner permanently.

The hard part is not the manager's. A board advisor at an electrical contracting firm described his own first turnaround CEO job: one night he typed a long message explaining exactly how a subordinate should handle something, then deleted it and typed three words instead. Whatever you think. That was the moment the employee started owning the work.

Order matters. Say those three words before the process is documented and you have abandoned it, not delegated it. Say them after month two, with everything written down, and the transfer holds.

That is the way out of the delegation paradox of having no time to train: the training happened in months one and two, so month three costs only restraint.

By day 90, the owner's default answer to a how-should-I-handle-this question is whatever you think.

---

The Handoff List: What Most 30-60-90 Day Plan Templates Leave Out

The center of the plan is an ordered list of the processes changing hands and the date each moves. Five rules set the order.

1. Start with frequency. A weekly task proves the transfer in a week; a quarterly one proves nothing until month four.
2. Take the interruption first. Move what people interrupt the owner about most, not the biggest thing on their plate.
3. Move whole processes. Half a process leaves the owner stuck in the middle of it, still answering.
4. Put a date on every line. A handoff without a date is still a wish at day 90.
5. Name one owner. One person per process, never a committee, named in writing.

The list usually includes training delivery, since a new manager inherits onboarding along with the work. That goes badly when the material is a binder nobody opens, so check first that your team is handed training they actually finish.

What Should You Measure at Each Gate?

Measure one thing at each gate: whether the work moved. Attendance, attitude, and hours are not gates.

The third column is the one owners skip: a gate met by a reassuring conversation is not a gate.

The failure, when nobody measures, is quiet rather than loud. One electrical contractor carried a coordinator who had gone quiet for years, kept partly because the company feared turnover. The fix that finally reached the table was not discipline but structure: post the update in the channel on a schedule, news or not.

A new manager who has gone quiet is not settling in, they are stuck, and nobody set a date to find out.

The strongest 90-day measurement is the owner's absence. One contractor scheduled two weeks away as a test, expecting honest feedback once nobody was waiting in his doorway. If the plan worked, the calls do not come. It is the plan for getting out of day-to-day operations on a single role.

When Should the Plan Be Rewritten Instead of Extended?

Rewrite the plan when the work turned out to be different from what you scoped. Extend it when the work is right and just slower than you hoped. Owners routinely apply the wrong one.

Rewrite when the role you hired for is not the role that exists. Rewrite when the processes turn out to be undocumented at a depth nobody scoped: across 16 businesses, 68 roles and 461 process areas we studied, 27 percent of the work was documented and half the areas had nothing. And rewrite when the owner cannot stop answering, because that is a handoff nobody made.

Extending without changing anything is the common mistake: add 30 days to a failing plan and you have made a temporary assistant role permanent. Extend a plan that is on track and slow; rewrite one that turned out to be different.

At The Systems Effect we build these handoff schedules from recorded sessions with the people doing the work, and the pattern holds: the processes an owner swears cannot move are the ones nobody wrote down. Write the three you want off your plate by day 90, with a date beside each.

Frequently Asked Questions

What should a 30-60-90 day plan include?

Name three things per block: what the manager learns, what they run, and what they own outright. The core is a handoff list of the processes leaving somebody else's plate, one owner and one date per line. Anything that cannot be tested at a gate belongs in the notes.

How is a 30-60-90 day plan different from an onboarding checklist?

An onboarding checklist is what the company owes a new hire: access, equipment, payroll, policies, first-week training. A 30-60-90 day plan is the leader's own document, and it tracks work changing hands rather than tasks provisioned. Run both at once; the checklist finishes by week two.

What should a new operations manager do in the first 30 days?

Sit with the people doing the work instead of the people describing it, and watch at least one real run of every process the role touches. Hold off on proposing changes until month two, because a manager who starts fixing in week two is fixing the process they were told about, not the one that runs. Interview a veteran and a recent hire; the two notice different problems.

Who writes the 30-60-90 day plan?

Both do. The person handing off the work drafts the first 80 percent, and the new manager rewrites it in week one. A plan the owner writes alone gets nodded at rather than run, and one the new manager writes alone misses the processes nobody has mentioned.

What if the new manager misses the 60 day gate?

Work out whether the work is on track and slow, or different from what you scoped. If it is on track, extend by 30 days and change nothing else. If the process turned out to be undocumented, far larger than anyone scoped, or still routed through the owner daily, rewrite instead, because adding time to a failing plan is how a 90-day handoff becomes a permanent assistant role.