How Long It Actually Takes a Promoted IC to Find Their Footing as a Leader (Or Wash Out)

Last updated: July 8, 2026

By Kris Drouet, Engineering Executive, in partnership with KORE1

Directors do not call me the day they promote someone. They call me at month four, voices a little tight, asking a version of the same question. Is this normal? The engineer they promoted is working harder than they ever worked as an IC, and something still feels off, and the director cannot tell whether they are watching a leader being born or a good career quietly coming apart.

Fair question. Also the wrong one, because it assumes there is a single clock.

There are two. Finding footing and washing out do not run at the same speed, and they are not mirror images. One is slow. Quiet. Easy to mistake for failure while it is happening. The other is fast. Also quiet, and easy to mistake for success. Own one number as a director and make it this one. Winning a team takes the better part of a year. Losing one takes a quarter. Sometimes less.

Whether to make the promotion at all is a separate decision, and I wrote the plan for that in promoting your best IC to engineering manager. This piece assumes the signature already happened. The title is real, the calendar is filling, and now you need to know what the next twelve to eighteen months are actually supposed to look like, so you stop grading a normal transition as a disaster and stop grading a slow disaster as fine.

The Two Clocks Run at Different Speeds

Here is the part nobody tells a new manager, or the director who signed the form. The job takes months to even start working. By design. The research backs this up in a way that should make you breathe easier and worry harder at once.

Michael Watkins asked more than two hundred CEOs how long a newly promoted or hired mid-level leader takes to reach the break-even point, the moment they have finally contributed as much value as they have consumed. The answer, on average, was about six months. Watkins wrote it up in The First 90 Days, and the number has held up for two decades. Six months to net zero. Not six months to great. Six months before they stop being a drain.

Linda Hill went further and slower. She tracked nineteen brand-new managers across their whole first year for Harvard Business Review’s Becoming the Boss. What she found was not a skills gap you close with a course. It was a transformation. A person slowly reconceiving what the job even is, and it took most of a year. The ones who made it quit trying to be the best engineer in the room. They became the person responsible for the room. Different work entirely.

So footing is a two-to-three-quarter project on the good path. That matches what I have watched for twenty-five years. First faint signal around the end of quarter one. The manager usually feels solid somewhere in months six to nine. The team does not feel it until months nine to twelve, because trust lags competence. By a lot.

Now the other clock. Washing out does not wait for anybody’s break-even point. The cracks are visible to a watchful director by month three or four. The team feels it by month five or six. And by roughly month nine, without a hard reset, it is terminal. I can count on one hand the managers I have seen who were genuinely drowning at month nine and swimming by month fifteen. The slow clock and the fast clock start on the same Monday. They just do not finish anywhere near each other.

The Benchmark: What Each Trajectory Looks Like, Month by Month

Finding footing means the shift is finished: the manager grades themselves on the team’s output instead of their own, and the work keeps moving when they leave the room. The engineers bring them judgment calls now, not code to fix. The title changed months ago. This is the part where the person catches up to it.

Below is the benchmark I walk directors through when they ask me what normal looks like. It is not a plan. It is a diagnostic. The two columns start out looking almost identical on purpose, because that is the honest truth of the first ninety days, and the whole skill is in reading which column you are actually in.

Read the two columns at month two and you cannot tell them apart. Read them at month nine and a child could. The entire art of setting expectations is knowing that the gap between those columns opens slowly, invisibly, in the middle, exactly where most directors stop paying close attention because the crisis of the first month has passed and the roadmap is screaming for their time.

Why Month Three Fools Almost Everyone

Look at the first quarter of a promotion under the hood and the two trajectories share nearly every visible symptom. Velocity dips in both, because a strong builder just stopped building and the team is absorbing the loss. The new manager is coding at midnight in both, because the calendar ate their day and the only place left to feel competent is the codebase they just left. Grumbling in both. Impostor syndrome in both. Watch the sprint burndown for your answer and both look like a bad bet.

The sprint numbers are the wrong instrument. The tell is not in the velocity. It is in the direction of what the team carries to the new manager’s desk. Look there.

A few years ago I watched a C# engineer, call her Dana, take over a mortgage-servicing team she had been the strongest builder on. Three months in, she looked like a mistake. Velocity had dipped. She was rewriting other people’s pull requests at eleven at night because letting them ship felt like malpractice. Her director asked me, quietly, whether they had ruined her. I told him to wait one more quarter and watch one thing, and not the velocity. Watch what the team brought her. By month eight it had changed. Her engineers had stopped bringing her code to fix and started bringing her trade-offs to settle. Which retry policy. Which deadline to defend to the product org. Which corner was safe to cut before the next servicing audit. That is the sound of footing, and it does not show up in the sprint report first. It shows up in the questions.

When a struggling new manager is actually on the footing path, the team leans in. They test whether the new authority is real by bringing it real problems. When a new manager is washing out, the team leans away. They stop bringing the hard stuff, not out of cruelty, but out of self-preservation, because they have already privately concluded the answer will not come from that chair. Same quarter. Same velocity dip. Opposite direction of travel. If you only measure one thing at month three, measure that.

What Washing Out Actually Looks Like, and Why It Is So Quiet

Washing out is almost never a dramatic collapse. That is the myth, and it costs teams a fortune. People picture a tyrant. A screamer. Someone obviously drowning. The washouts I have watched were none of that. They were competent, well-meaning, often very likable, and quietly failing at a job nobody had defined for them.

The opposite of Dana’s story fooled me once, and I should have known better. Call him Theo. Warm, funny, the most-liked person in the org, promoted over a small platform team. Month three looked great. Standups were cheerful. Nobody complained. What I missed was that nobody brought him anything hard, either. By month seven the two senior engineers had built a quiet back channel to route the real decisions past him, without the friction of ever saying so. Theo was not incompetent. He was not a jerk. He was a likable placeholder, and likability buys a washout time. That is the cruelest thing it can do, because it lets the erosion run two extra quarters before anyone is willing to say the word out loud.

The numbers on this are grim and worth sitting with. CEB Global found that about 60 percent of new managers underperform or fail inside their first two years. Sixty percent. That is not a talent shortage. That is an industry that keeps handing people a job and forgetting to teach it. The same body of Gartner research found that when a transitioning leader is struggling, their direct reports perform about 15 percent worse than the people under a strong manager, and they are roughly 20 percent likelier to leave or check out entirely. The washout does not stay contained to the one career. It taxes everyone standing near it, and it starts taxing them months before anyone files a complaint.

This is the part that turns quiet erosion into a real emergency. When the strongest engineer on a slowly failing team decides to leave, they have usually been interviewing for weeks before you hear about it. Weeks. The team that gets routed around a stuck leader loses its best people first, because the best people are the ones with the most options. Month nine is not the month the problem starts. It is the month it becomes visible to you, which is a very different thing, and by then the fast clock has almost run out.

Setting Expectations Before the Clock Starts

If you are the director, most of what you actually control happens before day one. Before the title, even. It lives in the expectations you set out loud. The transitions that go sideways are rarely the ones where the person could not do the job. They are the ones where nobody agreed on what the job was, or how long it would take to look like anything.

Tell the new manager the timeline honestly. All of it. Tell them month three will feel like failure. That feeling is not data. Tell them the goal for the first two quarters is not velocity, it is the slow handoff of decisions out of their head and into the team’s hands. A promoted IC who stays close to the craft while they learn to lead is following the same builder to leader arc that produces the most credible engineering leaders, and the ones who stay technical without becoming the bottleneck are the ones whose teams stop bluffing them. Say all of that in week one, not month nine.

Then put one thing on the calendar the day the title changes. A real checkpoint at month nine, scheduled up front, not improvised mid-crisis. Both of you already know the honest question you will ask at that meeting. Would you take this job again, knowing now what it actually contains? The point of scheduling it early is that the answer stops being an emergency scrawled into a Slack thread at midnight and becomes a normal conversation two adults planned to have, on a date they both circled months ago, with nothing currently on fire and no ultimatum in the room. Give the person a written path back to a senior IC seat at the same pay, and the month-nine conversation gets honest in a way it never can when swinging back feels like a demotion.

When the Clock Runs Out

Sometimes the verdict is washout, the reset came too late, and no amount of coaching is going to rebuild the trust the team already spent. That is not a failure of character. It is a promotion made without a real transition plan, running the exact course the odds predicted. So stop trying to save the seat. Start solving the actual problem. Which is now a hiring problem.

An external first-line manager who has already made their beginner mistakes on someone else’s team ramps on a different clock. They still need a quarter to learn your context, your stack, your politics. But not the job itself. They are not learning how to be a manager at the same time, so the people part works from week one. When the internal path has run out, that pattern recognition is what you are buying. Vetting for it is its own discipline, and it is nothing like interviewing an engineer, which is why I helped KORE1 put together their engineering manager interview questions. Their direct hire recruiters run this search constantly, average more than fifteen years in the business, and 92 percent of the people KORE1 places are still in the seat a year later. In a decision where the failure mode costs you two careers and a roadmap, that retention number is the one I would anchor on.

One more thing to check before you promote or hire again. Make sure your ladder is not manufacturing washouts on purpose. If the only way to give a great engineer a raise is to hand them direct reports, you are pushing people onto the fast clock who never wanted to be there. Keep the senior IC band overlapping the manager band, confirm it against a real engineering manager salary guide and your own market with the salary benchmark assistant, and a lot of the accidental promotions simply stop happening. Fix the ladder once. The best fix for a bad transition is the one you make before it starts. That is the whole argument behind how KORE1’s engineering staffing team thinks about these seats.

Where to Start This Week

If you promoted someone in the last few months and you are reading the sprint burndown for reassurance, stop. Look at what the team carries to their desk instead. Watch which direction it moves. Then put the month-nine checkpoint on the calendar today, while it is still early enough to matter. The clock is already running. Both of them are.

Staring at one of these right now and not sure which column you are in? Connect with me on LinkedIn and tell me what you are seeing at month three or month six. I read those. And if the honest read is that the clock has run out and the right manager is not on your team, talk to KORE1’s engineering hiring team before you talk yourself into a second promotion to fix the first one.

The Questions Directors Actually Ask Me About the Clock

Is a velocity drop in the first quarter a red flag or just part of it?

Just part of it. A velocity dip in the first quarter is expected, because your strongest builder stopped building and the team is absorbing that loss while learning a new decision-maker. The dip alone tells you nothing.

What tells you something is whether the dip recovers by month six and, long before that, which direction the team is carrying problems. Toward the new manager is footing. Around them is washout. Watch the questions, not the burndown, for the first two quarters.

My new manager still codes every night at month five. Should I make them stop?

At month five, more curious than alarmed. Some night coding is a healthy way to stay sharp. It becomes a warning sign only when it is where the sprint depends on them, or when it is clearly an escape from the parts of the job they are avoiding.

Ask what they are coding. It matters. A prototype or an internal tool nobody prioritized is fine and keeps their instincts warm. A sprint-blocking feature the team is waiting on means they have not actually handed off the work yet, and the transition has stalled under the disguise of hard effort.

How fast can a team actually turn on a new manager?

Faster than the manager can win them. Trust erodes in a single quarter and rebuilds over three or four, which is the core asymmetry. A team can privately write someone off by month three while it takes until month nine or twelve to earn genuine footing.

That gap is why the quiet washouts are so expensive, because the team reaches its private verdict months before the org ever does, and every single week of that lag is another week your best engineers spend quietly updating their own plans, refreshing their own resumes, and weighing whether the options outside are better than the chair they cannot trust inside. Speed of trust loss is the number directors most consistently underestimate.

We are at month nine and it is not working. Is it too late to save it?

Usually, for that placement in that seat, yes. In twenty-five years I have seen very few managers who were genuinely drowning at month nine recover into strong leaders by month fifteen. The honest move is a reset, not another quarter of hoping.

Resetting is not firing. Move the person back to a senior IC role at full pay, treat it out loud as a mismatch of role and timing rather than a failure of the person, and protect their standing on the way. Handled well, you keep a strong engineer. Handled as a punishment, you lose them and teach everyone watching to never swing back.

How long should I give an external manager hire compared to a promoted IC?

Give an external hire one quarter to learn context and hold them to the people part almost immediately. Give a promoted IC two to three quarters, because they are learning the context they already have plus the entire job of management at the same time.

The clocks are different because the learning is different. An external first-line manager already knows how to manage. They just need your stack, your history, and your politics. A promoted IC has all of that and is missing the one thing the external hire walked in with. Two different gaps. Judge each against the clock that fits it, not a single shared stopwatch.

Related reading: Promoting Your Best IC to Engineering Manager Without Ruining Two Careers, Why the Best Engineering Leaders Stay Technical, and When You Are the Bottleneck.