the new manager's first month

The situation

Meghna had been a senior developer at a product company in Bengaluru for five years. When her lead moved to another group, she was asked to lead the six people she had worked alongside for years.

One of the six was Karthik. They had joined in the same month and shared lunch most days. Another, Sameer, had also been considered for the role and had not got it.

Her own manager, Ravi, ran four teams and spent most evenings on calls with the US. His advice was: "You'll figure it out."

At her Trial Class she described the problem simply: "I know how to build the product. I don't know how to talk to the same people now that I'm their lead."

What was getting in the way (observed in sessions)

The coach began with three short role-plays: announcing the change to the team, a first one-to-one with Sameer, and asking Karthik for a status update. Some patterns were clear.

Avoiding the change. In the team role-play, Meghna said, "Nothing will really change, I'm still one of you." That sounded friendly. It also left everyone unsure what her role now was.
Doing instead of asking. When a task was behind, her instinct was to fix it herself at night, rather than talk to the person who owned it.
Softening until the message vanished. With Karthik, her request for a date was buried under so many apologies that it never quite became a request.
Silence upward. She saw problems with the quarter's plan but assumed raising them with Ravi would look like she could not cope.

None of this was about language ability. Her English was precise in technical discussions. These were simply conversations she had never had to lead.

The coaching approach, session by session

Session 1: the map

A conversation about the lead she wanted to be, and what she feared.
One aim agreed for the month: name the change plainly, listen before deciding, and keep standards without losing the friendship.
Mission: list the four conversations she was most dreading. She wrote: the first team call, Sameer, Karthik, Ravi.

Session 2: the first team talk

The coach asked Meghna to drop "nothing will change" and say what would.

"As you know, I'm now leading this team. Some things will change. I'll be the one setting priorities with Ravi, and I'll have a one-to-one with each of you in the next two weeks. Some things won't: I still want the code reviews to be as honest as they've always been, including on my code."

"I know this is a bit strange for all of us. I'd rather we say that than pretend it isn't. If something about the way I'm doing this feels off, tell me."

The coach pointed out that naming the awkwardness took most of the awkwardness out of it.

Sessions 3 and 4: the first one-to-ones

Mostly questions, very little talking. Meghna built one set to use with everyone.

"What's going well for you right now? What's getting in your way? What would you like more of, or less of, from me as your lead?"

The hardest was Sameer, whom the coach played as polite and distant. Meghna's instinct was to over-explain the decision. Instead she practised acknowledging it briefly, then turning to his goals:

"I know you were in the running for this role too. I'm not going to pretend that doesn't matter. I'd like to understand what you want from the next year, and how I can help you get there."

Session 5: delegating

Meghna listed the tasks she was still doing herself at night. The coach asked one question about each: "Who on the team would grow by doing this?" Then she practised handing work over with three things spelled out: the outcome, the deadline, and how involved she wanted to be.

"I'd like you to own the payments migration. The outcome is zero failed transactions in the switchover, by the 20th. You decide the approach. I'd like a five-minute check-in each Thursday, and if you're stuck, tell me early."

Sessions 6 and 7: the friend who missed a deadline

In the third week, Karthik missed a release deadline without warning. Meghna found out from the QA lead. She was hurt as much as she was worried, and her first draft of a message to him was either a long apology or a cold one-liner.

The coach helped her separate the two relationships. As a friend, she could say she cared. As a lead, she still needed a plain conversation about what happened and what would change. They practised it until both were in the same sentence:

"Karthik, I want to talk about the release, and I want to do it as your lead, not around the friendship. I found out about the delay from QA, not from you. That put the team in a difficult spot. What happened?"

Then, after listening:

"Next time something slips, I need to hear it from you first, even if it's late at night. Can we agree on that?"

The coach also played Karthik saying, half joking, "So you're the boss now." Her reply: "On this, yes. And I'd still like lunch on Friday."

Session 8: speaking up to her own manager

The quarter's plan had three major features; the team had capacity for two. Meghna had planned to cover the gap with late nights. Instead, with the coach playing a busy Ravi, she practised raising it in under a minute.

"Ravi, a quick flag on the quarter. We have capacity for two of the three features at the quality we want. I'd recommend we ship search and payments, and move reporting to next quarter. If reporting has to happen now, I'd need one more developer from another team. Which would you prefer?"

Point first, a recommendation, and a choice. Not a complaint.

Sessions 9 and onward: the real month

From here, each session began with the week's real conversations, rehearsing one moment at a time: a tense code review, a question about a salary revision.

What changed, in her words (composite reflection)

The reflection below is written in the style of what new managers in this situation commonly tell their coaches. It is not a quote from one person.

"The first team talk was the turning point. Saying 'this is strange for all of us' out loud made it less strange.
"With Sameer, I stopped trying to justify the decision. I just asked about his goals. It's still a bit careful between us, but it's honest.
"The conversation with Karthik was the hardest one I've had at work. I was scared it would end the friendship. We still have lunch. But he tells me first now when something slips.
"And I've stopped fixing everything myself at midnight. That one surprised me most."

What the reflection does not claim: that the team's delivery improved, that every relationship settled, or that the month was smooth. What coaching can change is whether a capable new lead has the words ready for the conversations the role now requires.

Lessons anyone can use

Name the change out loud. "Some things will change, some won't" is clearer and kinder than "nothing will change".
Make the first one-to-ones mostly questions. Listen first; decide later.
Acknowledge the person who didn't get the role, briefly. Then turn to their goals, not your justification.
Delegate the outcome, not the steps. Say the result, the date, and how involved you want to be.
Separate the friendship from the standard, in one sentence. You can care about someone and still ask for what the team needs.
Take problems upward with a recommendation. Point first, a proposal, and a clear choice for your manager.

Published by The Full Stop, the journal of Brightside English. Composite case study; no real learner, employer or family is represented. Reviewed by a Brightside senior coach. Corrections: see our editorial standard.