Engineering Leadership Transition Coaching Before Month Nine
Promoted ICs need two to three quarters to find footing. Wash-outs turn terminal around month nine. We work the gap in between.
Two clocks, one promotion
Same Monday, same scale. The bad clock finishes first, which is why the coaching window is month three and not month nine.
Engineering leadership transition coaching is structured support for a newly promoted engineering manager, usually 90 days of focused work. It exists because footing takes two to three quarters while washing out turns terminal by month nine.
Directors rarely call us the week they hand somebody the title. They call at month four, voice a little tight, asking a version of the same question. Is this normal? Fair question. Also the wrong one, because it assumes there is a single clock.
There are two. Finding footing is slow and quiet and easy to misread as failure while it is happening. Washing out is fast, also quiet, and easy to misread as somebody working hard. They start on the same Monday and they do not finish anywhere near each other. Not close.
That framework belongs to Kris Drouet, who spent 25 years running engineering organizations, most of it in regulated industries where a sloppy quarter eventually lands on somebody’s compliance report. KORE1 built an advisory engagement around it because our engineering staffing team kept getting called at month ten, when the only option left on the table was a search.
The research agrees on the shape. Michael Watkins asked more than two hundred CEOs how long a newly promoted mid-level leader takes to reach break-even, the moment they have finally contributed as much value as they have consumed, and the average answer was about six months. Linda Hill tracked nineteen brand-new managers through their entire first year for Harvard Business Review’s Becoming the Boss, and what she found was not a skills gap you close with a course. It was a person slowly rebuilding their idea of what the job even is. That takes a year.
A Coaching Conversation Is Not a Postmortem
A coaching conversation happens while the outcome can still change. You name one specific behavior, hand back the decision the person has been avoiding, and set a date to check on it. A postmortem explains a result that already landed. Too late by design. Both meetings feel productive, and only one of them changes anything.
The gap between those two meetings is about five weeks, and most directors spend it waiting. Not out of neglect. They wait because a wobble produces almost no signal, and every reporting line in the company is tuned to surface failure rather than drift. A slightly quieter standup is not failure. Neither is a manager writing code at 11pm because that is the only stretch of the day that felt like competence, which is exactly why that one is the tell.
Kris has heard the same sentence something like forty times, always around week six. “I don’t know what I did today.” Said flatly, the way you report a build failure you have not diagnosed yet. Flat is the tone worth worrying about. The full version of that meeting, in order, is in the coaching conversation that salvages a promoted IC.
None of it shows up in a status report either. Gallup’s State of the Global Workplace puts daily stress at 45% for managers against 39% for individual contributors, with 57% of managers saying it is a good time to be looking for a job. Your wobbling new manager is stressed and quietly browsing. Both at once.
The Two Tracks, Checkpoint by Checkpoint
This is the diagnostic we walk directors through when they ask what normal looks like. Read the two columns at month two and you cannot tell them apart. Read them at month nine and a child could. The whole art sits in the middle, where the gap opens quietly and most directors have already turned their attention back to the roadmap.
Overwhelmed, over-scheduled, still coding at night. Looks rough.
Overwhelmed, over-scheduled, still coding at night. Looks identical.
What coaching does at this checkpoint
Nothing diagnostic, and that is the point. Month two tells you nothing, so the work here is scaffolding. Calendar defense, one written page describing what the manager’s job now is, and an honest conversation about what they are allowed to stop doing.
Most new managers are still holding the IC role in their left hand. Nobody has told them yet that they can put it down.
The team starts bringing them decisions to settle, not just code to review.
The team starts routing around them. Quietly. Nobody names it in a meeting.
What coaching does at this checkpoint
This is the cheap meeting. Open with one specific, dated, observable thing. “Last Thursday the schema change went out and I found out from the incident channel,” not “I have been hearing some concerns.” Vague openers make people defend everything, and a person defending everything cannot hear anything.
Then stop talking and let the silence sit. Nine times out of ten the reasoning holds up and you learn something. The tenth time is the coaching conversation, and running it here costs a lunch hour instead of a quarter.
First genuinely hard conversation handled without you in the room. Velocity recovering.
Velocity still sagging. They grade themselves on their old output and keep failing their own test.
What coaching does at this checkpoint
Separate the two things that get tangled together here. Either they did not know the decision was theirs, which is a clarity problem and it belongs to you, or they knew and avoided it, which is the coaching problem and it belongs to them.
Opposite treatments. Directors who skip this step reliably fix the wrong one, then wonder why month nine still arrives on schedule. It always does.
Engineers defend their own calls in the room. Footing is visible to everybody.
The strongest engineer has quietly started interviewing.
What coaching does at this checkpoint
Past this line you are not coaching anybody. You are documenting. When an engineer skips their manager to reach you and does not even register it as skipping, the org has already re-routed itself, and a re-route is a rebuild.
Rebuilds take a quarter nobody budgeted. This is also, almost always, the week our phone rings.
A manager. Nobody calls it a promotion anymore. They call it their job.
Two seats to backfill and a year of roadmap gone.
What coaching does at this checkpoint
Two seats, not one. Losing a manager at month nine rarely costs a single person, because a senior engineer usually follows within a quarter. They trusted her judgment more than they trusted the leadership team’s, and watching her leave answered a question they had been sitting on.
The month-by-month version, with the reasoning behind every checkpoint, is in how long the IC-to-manager transition actually takes. Read it before you decide a month-four manager is failing.
What the Clocks Actually Cost
Six months to net zero. Not six months to good.
The manager feels solid at months six to nine. The team lags by three.
The distance between the meeting that changes an outcome and the one that explains it.
Trailing 12-month average, with 92% retention at the one-year mark.
Break-even is Michael Watkins, from the CEO survey behind The First 90 Days. Footing and coaching windows are Kris Drouet’s, drawn from 25 years of engineering leadership. Time-to-hire and retention are KORE1’s own placement numbers.
Three Ways This Shows Up
Most engagements start with the first one. Some need two. Plenty never need the third, and we would rather tell you that early than bill you for a search you did not need.
Transition coaching
Ninety days with the newly promoted manager, biweekly. One named behavior at a time, with a check-in date on every one.
Leadership advisory
Monthly work with the director or VP above them, because half of what looks like a manager problem is an unwritten mandate.
Search, when it is a seat
Sometimes the honest answer is that the role needs somebody who has held it before. We say so, in writing.
Good Leaders Do Not Outgrow the Code
The most expensive career advice in this field says the higher you go, the further you should drift from the build. It sounds mature. It is mostly wrong, and it makes transitions worse, because a new manager who believes it stops attending architecture reviews in month two and spends month eight nodding along to things they no longer follow.
Staying technical does not mean reviewing every pull request. Kris worked for a leader who did exactly that, down to variable names and brace placement, and watched three excellent engineers leave inside eighteen months because they were tired of executing somebody else’s vision all day. That is not staying technical. That is being a bottleneck with a title.
The real bar is narrower. Read your team’s code and follow it. Sit in the design review and ask the question that makes the room uncomfortable. Know roughly what the stack costs to run, and when an engineer says six weeks, know whether that is an estimate or breathing room. Stay fluent, stay out of the way. Kris calls the full shape of it the Builder-Leader-Advisor arc, and the argument in full sits in why the best engineering leaders stay technical.
When Coaching Is the Wrong Tool
Coaching fixes a person who can hold the seat and has not learned it yet. It does not fix a seat that was never right for them, and it will not fix a mandate nobody bothered to write down. That part is a search.
Both real paths work. Build means training a senior engineer into leadership over eighteen months, with a coach and an honest way back into IC work if the role does not fit. Buy means hiring somebody who has held the seat before, then giving them a named sponsor and enough internal context that they do not spend their first quarter guessing at how decisions get made here. Promote and hope is the only version that reliably fails, and it is still the most common one in the market. By a distance. Gallup has a number for this one. Not a flattering one. Companies pick the right talent for a manager role only 18% of the time, which is a large part of why great managers are so rare. Handing the team to your best builder and hoping is that same coin flip, except you are betting your roadmap, your best engineer, and the trust of everybody who watches how it turns out.
KORE1 places engineering leaders down both paths, through direct hire searches and fractional or interim VP of engineering engagements, and we fill engineering manager seats when the gap sits one layer below that. If the promotion has not happened yet, that decision has a checklist of its own.
Common Questions
What does engineering leadership transition coaching actually include?
Ninety days of structured work with a newly promoted engineering manager, usually biweekly, with a parallel track for the leader above them. Each session names one specific behavior, hands back a decision the manager has been avoiding, and sets a check-in date. The parallel track exists because roughly half of what looks like a manager problem turns out to be an unwritten mandate. That is the whole engagement.
When should we start coaching a newly promoted manager?
Month one, before anything looks wrong. Waiting for something to look wrong means starting around month five, and by then you are coaching against a team that has already adjusted its behavior. Month three is the last genuinely cheap window. Month nine is a rebuild.
How do we tell a wobble from a wash-out?
Watch where your name shows up. A wobbling manager loops you into threads they could have closed themselves, which is a confidence problem you can coach. A washing-out manager’s engineers start threads without them on it at all, which means the org already re-routed. Same week, same team, completely different meeting.
Isn’t six to nine months a long time to wait for a new manager to work?
It is, and the research says wait anyway. Michael Watkins found the average newly promoted mid-level leader needs roughly six months just to reach break-even, and Linda Hill’s year-long study of nineteen new managers describes something closer to rebuilding an identity than closing a skills gap. Grading a normal transition as a disaster at month four is the most expensive common mistake we see, because directors who do it start a search they did not need and lose the manager they already had.
Can you coach someone who is already past month nine?
Sometimes, but the work changes shape. Past the point where engineers route around their manager you are rebuilding trust rather than adjusting a trajectory, and that takes a quarter you probably did not budget. Kris can count on one hand the managers he has seen genuinely drowning at month nine and swimming by month fifteen. It happens. Plan for it not to.
Do we need coaching or do we need to hire?
Ask whether the person can hold the seat and has not learned it, or was never right for it. Coaching fixes the first and only a search fixes the second. If the layer above the manager is also unclear, fix that first, and the free engineering velocity assessment is the fastest way to check whether you are looking at one struggling manager or the operating system around them.
Tell Us Which Month You Are In
Month three and month nine are different conversations. Tell us which one you are having and we will tell you honestly whether it reads as coaching or a search, in writing, before you commit to anything or spend a dollar.
