Promoted on Friday, managing on Monday: the first 90 days

A senior engineer was promoted to team lead on a Friday. On Monday she had six people, three of whom had been her peers the week before, and a calendar that still had her name on every technical task from the previous sprint. Nobody had told her what the job was. Nobody had told the team either. Her manager's entire handover was a message saying congratulations and that they would catch up properly at some point.

Four months later she asked to go back to her old role. She was not a bad manager. She had simply been asked to learn the hardest job in the organisation by guessing, in public, while still delivering her previous one.

This is the single most common failure in Indian businesses that promote from within, and it is entirely preventable. The promotion is not the development. The promotion is the moment development becomes urgent.

What actually changes on Monday

It helps to be blunt with a new manager about what has changed, because the announcement rarely says it.

BEFORE                        AFTER
Your output is the work        Your output is the team's work
You are measured on delivery   You are measured on the team's delivery
Being right wins the argument  Being right is not enough; you have to
                               carry people to the same conclusion
Information is something you   Information is something you distribute
  receive
You solve the problem          You decide who solves the problem, and
                               resist solving it yourself

The last line is where most new managers struggle. The behaviour that earned them the promotion — stepping in, fixing it personally, being the one who knows — is now the behaviour that limits the team. Nobody tells them this, so they do more of what worked and wonder why it is going badly.

Days 1 to 30: listen, and resist the urge to change anything

The instinct on day one is to demonstrate that the promotion was deserved. That usually means announcing changes. It is almost always the wrong move, because at day one the new manager knows the work but not the team's view of the work, and those are different things.

1. 1

   One conversation with every person, individually, in the first two weeks

   Not a review. Three questions: what is working, what is getting in your way, and what would you want me to know that you would not say in a group. Write the answers down. The value is in the pattern across six conversations, not in any one of them.

2. 2

   Ask the team what they expect from you

   Uncomfortable, and worth it. Most teams have a clear view and have never been asked. It also establishes early that the job is a two-way arrangement rather than an announcement.

3. 3

   Find out what your own manager actually wants

   New managers routinely operate on an assumed remit for months. Ask directly: what does good look like at ninety days, what decisions are mine, and what should never reach you without warning.

4. 4

   Change nothing structural

   One exception: anything actively harmful. Otherwise the first month is for understanding why things are the way they are. Half of what looks broken is a reasonable response to a constraint you have not found yet.

Days 31 to 60: the first hard conversation

Somewhere in month two, the first real test arrives. Usually it is a performance conversation with a former peer, or a decision that will disappoint someone. How it is handled sets the tone for everything after.

The common failure is delay. A new manager who is worried about the relationship postpones the conversation, hopes it resolves itself, and ends up having it three months later when it has become a much larger problem and the person can reasonably ask why nobody said anything sooner.

The second failure is the opposite: overcorrecting into formality, because the manager has been told to be firm and does not yet know the difference between firm and cold. A first-time manager who opens with a written warning where a ten-minute conversation would have done has usually been badly briefed rather than badly intentioned.

Both failures come from the same gap — nobody has shown them what a normal corrective conversation sounds like. It is a teachable skill and it takes about half a day to teach, which is a large part of what leadership and people management training exists to cover for exactly this population.

Days 61 to 90: stop doing your old job

By month three the new manager is usually doing both jobs. They have kept their technical work because it is what they are good at and because handing it over feels like an imposition on a team that is already busy. The result is a manager who is behind on both.

• Name the handover explicitly. Which specific pieces of previous work move, to whom, by when. Left implicit, it never happens.
• Accept the first handover will be done worse than you did it. It will improve. A manager who takes work back the first time it is imperfect will never hand anything over again.
• Protect time for the management work. It has no deadline, so it loses every scheduling contest against work that does. One-to-ones that get cancelled twice stop being a thing the team believes in.
• Keep a small amount of hands-on work if it helps credibility — but choose it deliberately rather than keeping whatever you did not manage to hand over.

What the business owes them

Most of the burden in these ninety days is placed on the individual, which is convenient and unfair. Three things are the employer's job, not the new manager's.

A defined remit. What they decide, what they recommend, what they escalate. Written down, in a paragraph. Without it they will either overstep and be corrected in public, or under-reach and be told they lack initiative — and both outcomes look like the individual failing when they are a briefing failure. This is the same clarity that role design and job descriptions work produces for any role; managers are not an exception.

A sponsor who is not their line manager. Someone a level up or sideways they can ask a stupid question without it becoming a performance signal. New managers have many stupid questions and nowhere safe to put them, so they guess instead.

Training that arrives before the crisis, not after. The common pattern is to send someone on a leadership programme in year two, after the first difficult year has already shaped how the team sees them. Reversing a reputation is far harder than forming a good one, which is why the timing of leadership and people management development matters as much as its content.

The ninety-day review that is worth doing

Not a performance review. A short conversation, with the new manager and their manager, on four questions: what surprised you, what are you avoiding, what does the team need that you cannot give them, and what would you do differently if you started again on Monday.

The second question is the one that matters. Every new manager is avoiding something at day ninety — a conversation, a decision, a person. Naming it is usually enough to get it moving, and it is the cheapest intervention available.

If several new managers in the same business are avoiding the same thing, that is not ninety-day nerves. It is a signal about what the organisation makes difficult — and a pattern across a cohort is worth more diagnostic attention than any individual case. Where that pattern keeps repeating, an HR process audit of how people reach the manager role in the first place usually finds the cause upstream of the training.