How to Onboard a New Manager in the First 30 Days
Move the questions off your shoulder and onto paper. The new manager keeps a daily log of what puzzles them, you clear the backlog at one set time each day, and their authority grows week by week inside limits you name in advance. Tie the whole month to a date you'll be away, so the plan has an end.
A while back an owner told me about a Tuesday that went sideways in week two of his new operations manager's tenure. The new manager, sharp and eager, had noticed that a long-time dispatcher built the weekly route sheet in a way that wasted about forty minutes of drive time. So he rebuilt it. Nobody asked him to. The dispatcher, who had built that sheet for six years, walked out of the building at lunch and came back the next morning with her arms crossed.
The owner spent the next three days on the phone with both of them. Which is roughly what he'd hired a manager to avoid.
I hear a version of this often enough that I think the usual advice on onboarding is aimed at the wrong person. Most plans are written for the new hire: here's the handbook, shadow Sam for a week, we'll check in on Fridays. They quietly assume the owner will fill every gap in real time, which is how the new manager ends up asking you everything. You are the only one who knows the answers, so you become the manual.
What follows is a 30-day structure that moves the learning onto the new person, keeps them from doing damage while they're still reading the room, and leaves you with a finish line. I'll use that route-sheet owner's business as the frame, with the details changed: a $2.4M home services company, nine staff, one owner, and a new operations manager starting on a Monday.
If you haven't made the hire yet, hire an operations manager or fix your systems first is the question to settle before any of this.
What should a new manager keep instead of a binder?
Before day one, the owner created a single running document and told the new manager it was his to keep. Each day he adds entries under four headings: what I did, what I learned, what I couldn't answer, and what felt wrong or uncomfortable.
The first three are obvious. The last is the one that earns its place. A new person sees your business with fresh eyes for roughly three weeks, and then it starts to look normal to them, the same way it looks normal to you. If you don't capture what seemed strange on day four, it's gone by day twenty-five. "Why do we call the customer back before we confirm the parts are in stock?" is exactly the kind of line that shows up in a discomfort column and never gets said out loud in a meeting.
The "couldn't answer" column does a second job. It's your replacement for the shoulder tap. When he hits something he can't resolve, he writes it down with whatever he's already tried, and the owner goes through the list at one fixed time each day. In this case it was 12:15, fifteen minutes, no exceptions except anything that touched safety or a customer's money. Questions that arrive in a batch tend to answer each other. By Thursday of week one, the manager was crossing off about a third of his own list before the meeting, because writing the question out exposed the answer.
Should a new manager change things in the first two weeks?
This is the part owners resist, and it's where the route-sheet incident came from. For the first ten working days, the new manager changes nothing. No rebuilt spreadsheets, no reassigned tasks, no new rules. He can propose anything he likes, in the log, but he can't touch it.
It sounds wasteful to bring in someone experienced and tell them to sit on their hands. The reasoning is that existing staff are deciding in those first two weeks whether this person is a threat or a help, and they read changes to their own work as an answer.
The dispatcher's route sheet was inefficient, and she probably half knew that. But she also knew why it was built that way, including a customer with a gate code that only worked before 9 a.m., which no one had written down. Her reaction was partly pride, partly a reasonable worry that a stranger was editing something he didn't fully understand. She was right about the second part.
Ten days is a judgment call, not a law. For a very small team, a week is enough. For a company with long job cycles, such as construction or anything with a sales-to-delivery gap of months, I'd stretch it. What matters is that the restraint has an end date everyone knows about, so people read it as a plan and nobody feels leashed.
What does each week of the first 30 days involve?
Here is the schedule the owner used. It isn't fancy. The point is that every week has a different job for the new person and a different job for the owner.
- Weeks 1 and 2. New manager: Observe, ride along, sit in on every recurring meeting. Log daily. No changes. Owner: Introduce him, in person, with one sentence about what each person is great at. Answer the 12:15 list.
- Week 3. New manager: Pick two problems from the log and write a one-page proposal for each, including what could go wrong. Run one small fix with the person who owns that work, in their presence. Owner: Read the proposals. Say yes, no, or "show me the cost" within two working days.
- Week 4. New manager: Own the weekly operations meeting. Make the calls on anything under $500 or any schedule change inside a single day, and tell the owner afterward. Owner: Attend the meeting but don't run it. Hold your tongue on small things, and write down the ones you disagree with to review at the end of the week.
By week four he was making real decisions. The $500 line and the one-day line were the owner's numbers, picked because they matched the worst realistic mistake he could absorb without losing sleep. If you don't know yours, look at the last ten times someone asked you to approve something and see how many were under that number.
Handing over the meeting itself is covered in a weekly operating meeting that runs without you.
Where does new manager onboarding usually go wrong?
The weakest point is usually the owner, not the hire. Around day twelve or so, when the manager starts proposing things, the owner will see a better answer to a small question and quietly give it. Then the log stops being the place decisions are made, and the manager reverts to asking in the hallway. If you catch yourself doing this, say so plainly: "I jumped in on that, put it back on your list and we'll handle it at 12:15." It's a little embarrassing and it works.
The second failure is a hire who writes almost nothing. I've seen this with people who are good operators but treat documentation as paperwork. A thin log in week one is information. Either they don't see the log as theirs, or they aren't noticing much, and you want to find that out in week two, not week ten. Ask for a specific entry, such as "tell me three things about how dispatch really works that nobody told you," and see what comes back.
The third is subtler. Occasionally the new person is simply wrong for the role, and the structure makes that obvious fast: no proposals by day twenty, no questions that improve, defensive when asked about the log. Thirty days of watching someone operate with real latitude tells you more than any interview did. Having a clean point to step back and make a hard call at day 30 is kinder than finding out in month six.
Why does the plan need a deadline?
The owner in this story did one more thing, borrowed from a pattern I've seen work with several owners hiring a senior person. He booked a full week away about ten weeks after the start date, with no access to the business except for a short list of real emergencies, and he told the new manager about it in the first conversation.
That date does something a plan can't. It turns the log into a preparation list. The manager knew he'd be running the shop alone, so the entries under "couldn't answer" stopped being curiosities and became things to resolve. He asked for the gate-code history. He made the dispatcher his first real ally, because she was the one person who could keep the route sheet running when he was lost. He and the owner worked out, together, that purchasing approvals up to $750 were his, and anything above waited for a text only if a job was actually blocked.
The surprising result for the owner was how little of the onboarding turned out to be about training. He told me afterward that he'd expected to spend the month teaching the manager how things work. What he actually spent it on was deciding, out loud, what he'd let go of, which he hadn't done in years. Most of the questions a new manager asks you are really the same question, which is how much of this is mine. If you haven't answered it, no amount of shadowing will.
What if your manager started months ago?
Plenty of owners reading this have a manager who started three months ago and is still in the hallway every hour. You can still run the log and the daily list; just call it a reset and say why. Skip the no-changes rule, since the damage window has passed, and start at the week-three structure with a smaller decision limit. Give a date for the first week you'll be gone, even if it's four months out.
Frequently asked questions
Should the new manager's log be private?
Share it with you and keep it from the wider team at first. The discomfort column often names people and habits, and it only helps if it stays honest. Once a proposal comes out of the log, it goes to whoever owns that work, in person, the same way the week three fixes run.
What if the new manager knows operations better than I do?
Run the same structure anyway. Experience helps them read the business faster, but the gate codes, the customer history and your limits still have to be learned from scratch. Their experience shows up in the week three proposals, which tend to be sharper, and that is where you get the value you hired for.
What if the team resists the new manager?
Expect some of it, and treat it as information. Ask the people most affected what they would want the new manager to understand first, and put their answers in the log. Making a long-serving employee the manager's first source often turns the loudest doubter into an ally.
Would a second opinion on your 30 days help?
None of this requires software. A shared document, a recurring fifteen-minute slot, and a number you're willing to be wrong about will do it. If you'd rather build the structure with someone who has seen it go well and badly, that's what the Planning Call is for.
