5 Practical Ways to Navigate the Peer-to-Manager Shift

When "We" Becomes "Me"

In previous pieces with Jennifer Houle and Colette Molteni, we watched Rahul navigate ambiguity with his team and learn the difference between inquiry and interrogation. But those situations assumed something stable underneath: Rahul’s role. He knew where he sat in the room and who he could be honest with over lunch.

In this piece, that foundation moves. Rahul gets promoted, and overnight the people he used to work alongside become the people he’s responsible for. The job title changes in a day. The relationships take much longer to catch up, and the gap between the two is where many new managers come undone.

This matters because the peer-to-manager transition is one of the most common leadership shifts in professional life, and one of the least supported. Organisations announce the promotion and assume the rest will follow. But it usually doesn’t. What follows instead is a series of small, disorienting moments where the rules you relied on no longer apply, and no one tells you what the new ones are.

The story below tracks five of those moments. After it, we’ll unpack what each one teaches and what you can do about it.

If you want to go further, there’s a companion toolkit that turns each moment into a structured action plan - more on that at the end.

---

The announcement had been met with a raucous chorus of cheers and whistles. When the CEO stood up in the middle of the open-plan office to announce Rahul’s promotion to Team Lead, the applause wasn’t just polite; it was warm. Rahul’s colleagues were clearly happy for him, and Sarah, who had started the same week as Rahul three years ago, had even given him a card congratulating him on the promotion.

But that was four weeks ago, back when Rahul was still part of the “we.”

Now, he sat at the head of the small conference room table, flanked by “his” team. Even though it was the same group, he felt stiff and awkward addressing them, like he was playing the part of a manager in a play he hadn’t rehearsed for.

“So, the Q3 targets are pretty aggressive, but I think if we distribute the load early, we won’t have a repeat of what happened last month,” Rahul said, trying to strike a tone that was firm but friendly.

Marcus, a senior dev about ten years older than Rahul, leaned towards a few colleagues, muttering something under his breath. A quick, stifled burst of laughter rippled around the left side of the room.

“What was that?” Rahul asked, leaning in with a smile, ready to join the moment.

The laughter immediately stopped. Marcus looked down, flipping his pen between his fingers.

“Nothing,” he said, his voice flat. “Ready when you are, boss.”

Sarah looked up at Rahul, smiling, encouragingly.

In that moment, Rahul realized he was no longer part of the collective “we” that got to complain about everything; he was now the “me” representing the “why.”

After that first meeting, Rahul started doing something he’d never done before: rehearsing. Not the content - he knew the work - but the delivery. He’d run sentences back in his head before saying them out loud, checking for anything that might land wrong, scanning the room before he spoke the way you’d scan a road before pulling out. He stopped leaning in when people laughed. He stopped assuming the laughter was something he was part of.

So when Marcus stopped by his desk two months in, Rahul noticed immediately that he didn’t pull over a chair. He stayed standing.

“That new workflow you proposed,” Marcus began, “I’ve seen three versions of that in my fifteen years here. It usually falls apart at the integration stage.”

Rahul felt a flush of defensiveness. He knew the tech, but Marcus knew the history. He needed Marcus’s buy-in, but he wasn’t sure how to lead someone who had a decade more context without pulling the “Because I said so” card.

Rahul gave Marcus the space to disagree, and in the end, they found a workable compromise on the integration sequencing. But walking back to his desk afterwards, Rahul felt the peculiar exhaustion of a conversation where you win the point but lose something else - some ease, some shorthand, some willingness to just say what you think without weighing it first. He was learning to lead Marcus, but the cost was a kind of permanent diplomatic vigilance that left him drained by mid-afternoon.

It was in that state, already tired of choosing his words carefully, that Rahul realised his relationship with Divi had changed too, just in the opposite direction.

“I noticed I didn’t get the lead on the Smith account,” Divi said to Rahul, her voice low. “Is it because of that mistake I made last week?”

Previously, Rahul would have told her over coffee not to worry about it…just a quick tip between peers on how to smooth things over. But now, he had to resolve the error differently.

He explained the decision, noting that, yes, partly it was due to the mistake she had made, which meant he couldn’t justify putting her in the lead role just yet. As he spoke, he saw the confusion in her eyes. She was used to his casual, helpful shortcuts, and she wasn’t prepared for this version of him, the one who had to prioritize professional accountability over their usual “don’t-worry-about-it” shorthand.

He thought about that conversation for the rest of the day. He knew the decision was right, but the look on Divi’s face when she realised he wasn’t going to make it okay the way he used to stayed with him. He’d been her informal safety net, and he’d just told her the net had rules now. The right call, but it sat in his chest like a stone.

Later that week, still carrying the weight of it, Rahul stepped out of a late-running budget meeting, tired and hungry. But as he rounded the corner, he saw that everyone had already left.

He walked to the window and saw a group of colleagues making their way to their favourite deli. He stood there longer than he needed to, watching the group disappear around the corner. Three months ago, someone in that pack would have texted him: where are you, we’re starving. Now there was no text. It wasn’t cruelty. It was simply that the person they used to text had been replaced by someone they reported to, and that person, apparently, made his own lunch plans.

He ate a sandwich at his desk that day, and again the next day, and by Friday he’d stopped noticing. Which is probably why, when a resource conflict between Sarah and Marcus landed in his inbox at the end of the week, it felt heavier than it should have. There was no one to think it through with over food. No one to say honestly, they’re both being ridiculous before helping him figure out who was right. The email thread sat on his screen, and it was just him and the cursor.

Rahul didn’t leave his desk until the office was empty. He looked at his old workstation, taken over by a new hire whose name he kept forgetting. There was a plant on the desk now, and a framed photo angled away from him. The monitor had a sticky note on it, something about a password reset, in handwriting he didn’t recognise. Someone else’s routine had already settled into the space, as if Rahul had never sat there at all.

He picked up his bag and wondered at what point the promotion had started to feel less like a step up and more like a step away.

Rahul is discovering that it’s lonely at the top.

---

Rahul’s experience is ordinary, which is exactly what makes it useful. He isn’t failing spectacularly or isn’t managing a crisis. He is dealing with the slow, accumulating challenges of a role change that no one prepared him for.

Most advice on the peer-to-manager shift focuses on authority: how to delegate, how to set expectations, how to give feedback. That matters, of course, but it skips the part that trips people up first, which is the social and emotional recalibration.

You have to let go of a version of yourself that your colleagues liked, and replace it with one they haven’t decided about yet. That process is uncomfortable, and it doesn’t resolve in a week.

The five practical recommendations below are drawn from the moments in Rahul’s story. They won’t make the transition painless, but they’ll help you see what’s happening while it’s happening, which is usually enough to stop it from going sideways.

1. The identity shift

The hardest part of the first few weeks isn’t the workload or the meetings - that’s remarkably likely to stay very similar, especially if you have transitioned naturally in the new role. The hardest part is the moment you realise you’re still performing your old role socially (leaning in to laugh, assuming you’re part of the joke, waiting for someone to include you) when the dynamics have already changed. Everyone else felt the shift on day one, and you’re the last to catch up.

The practical move is unglamorous: you have to stop waiting for the group to signal where you fit. You just don’t fit where you used to, and that’s not a problem to solve but a fact to absorb. The sooner you stop testing whether the old dynamic still works the sooner your team can settle into the new arrangement. They’re watching you to figure out what the new normal looks like. If you keep acting like a peer who happens to have a title, you’ll confuse them, and the confusion will eventually curdle into resentment.

2. The senior peer bridge

At some point, you will need to manage someone who has been doing this longer than you. They know things you don’t, including a mix of corporate history and deeper subject matter knowledge. Pulling rank on that person is a losing strategy. You might win the immediate argument, but you’ll lose their willingness to tell you things you need to hear.

The better approach is to treat their seniority as an asset you can use. When they push back, ask them to walk you through what happened last time or what are the technical reasons behind their position. Get specific: what broke, at what stage, and what would need to be different now? This does two things: it gives you information you genuinely need, and it signals that you’re asking for their judgment, which is a fundamentally different position from aking for compliance. The goal is a joint decision that draws on their experience and your authority. If you can get there, you won’t need to use the “because I said so” card, and they won’t need to keep testing whether you’ll play it.

This is one of the five scenarios covered in depth in the Peer-to-Manager Toolkit, with diagnostic questions, AI prompts, and common variants on each scenario. Get your copy on Gumroad - the first five to press buy get it for free!

Paid subscribers get this 70% off forever - find your discount code in the Members area!

3. The accountability conversation

If you were the kind of colleague who smoothed things over, you need to recognise that this register is no longer available to you. What used to be peer-to-peer kindness now reads as the boss making exceptions, and the people around you will notice the inconsistency before you do.

This doesn’t mean becoming cold or withholding. It means being direct, and doing so earlier. When someone you used to mentor makes a mistake, explain the consequences clearly and explain your reasoning. Don’t dress it up or soften it with the old shorthand. The discomfort you feel in that conversation is the price of the transition, and it’s worth paying upfront.

The alternative just creates ambiguity that will erode trust on both sides, as well as putting you into trouble with your own manager. The people who report to you deserve to know where they stand, even if the old version of you would have handled it differently.

4. The missing sounding board

One of the least discussed costs of the peer-to-manager shift is the loss of your informal thinking partners. The people you used to hash things out with over lunch are now your direct reports, so you can’t use them for that any more.

You need to fill this gap deliberately. Ideally, you would find other managers at your level within your organisation, people going through the same transition. If your organisation doesn’t have a natural peer group for new managers, look outside it: a mentor, a coach, a former colleague who’s been through this.

The specific format matters less than the function: you need someone you can think out loud with, someone who isn’t in your reporting line and doesn’t need you to perform confidence. Without that outlet, every difficult decision will feel heavier than it needs to, and you’ll start making choices in isolation that would have been better with a second perspective.

5. The first ruling

Eventually, a conflict will land in your lap that you can’t defer, delegate or wait out. Two people on your team will disagree, both will escalate to you, and both will expect a ruling. In your old role, you could have stayed out of it or offered a sympathetic ear. But that option is gone.

The only sensible option here is having a process. Gather the facts from both sides separately; identify the actual resource or priority question underneath the interpersonal friction; make the call, then explain your reasoning to both parties individually (not in an email).

The explanation matters as much as the decision, because what your team is really evaluating is whether you have a coherent basis for making these calls at all. If you sit on it, you lose credibility with both sides. If you decide without explaining, you’ll be seen as arbitrary. The goal is to be transparent enough that even the person who didn’t get what they wanted understands why.

The shift no one prepares you for

The peer-to-manager transition announces itself through a series of small moments. A meeting where the laughter stops. A colleague who stays standing. A lunch group that forgets to text. Individually, none of these are crises. Together, they reshape how you experience your own team. If you don’t recognise the pattern, the isolation adds up until every small decision feels disproportionately heavy.

Rahul’s story doesn’t end with a resolution, because there isn’t one. Not in the neat sense. The transition just levels out.

At some point, you stop expecting the old dynamic to return, you build new sources of support, and you develop a working rhythm with the authority you’ve been given. It gets easier, but only if you see what’s happening clearly enough to respond to it rather than endure it.

The five recommendations above are a starting point. If you want to go further, the toolkit below turns each of Rahul’s scenarios into something you can act on this week.

---

The toolkit behind this article

Everything above is free, and it’s enough to recognise what’s happening to you. But recognition and action are different things, and the gap between them is where most new managers get stuck: they can see the problem, but they don’t know what to say in the meeting, how to open the conversation or what to do the morning after it goes badly.

The Peer-to-Manager Toolkit is a structured companion for the first 90 days. It covers the five scenarios in Rahul’s story, each one built as a five-stage module:

1. Diagnose the situation

2. Understand why your default instinct will probably backfire

3. Prepare the conversation using AI prompts tailored to your specifics

4. Debrief afterwards with a second prompt that catches what you missed

5. Adjust for the version of the problem you’re actually facing.

It’s designed to replace the thinking partner you lost when you got promoted.

Here’s what Stage 1 and Stage 2 look like for one of the five modules, so you can see how it works in practice:

---

Module 3: The Accountability Conversation (sample)

Stage 1: Recognise it

The accountability conversation is one of the most common things new managers get wrong, usually because they misdiagnose the situation and prepare for the wrong version of it.

Is this a mistake or a pattern?

A single error requires a different conversation from a recurring issue. If someone missed a detail on one deliverable, the conversation is short and specific: here’s what happened, here’s the impact, here’s what I need next time. If the same kind of error has shown up three times in six weeks, you’re looking at something structural (e.g. a skills gap, a workload problem or a misunderstanding of expectations) and the conversation needs to go deeper. Don’t treat a pattern as a one-off, and don’t escalate a genuine one-off into a performance discussion.

Did you contribute to the mistake?

This is the question most new managers skip. Was the brief clear? Were the expectations explicit, or were they the kind of unspoken understanding that works between peers but breaks down when one person is now evaluating the other? If your instructions were ambiguous and the person made a reasonable interpretation that happened to be wrong, the conversation isn’t really about their mistake. It’s about a gap in how you communicated, and the honest move is to own your part before addressing theirs.

What was the relationship before the promotion?

If this person was a close colleague, a mentee or someone you regularly reassured in your old role, they are going to experience this conversation as a change in the relationship, not just as feedback on their work. You need to know that going in, because it will shape how they hear everything you say. They’re not just processing the feedback, but also the fact that you’re the one delivering it, and that the delivery is different from what they’re used to.

What outcome do you actually need?

Be specific with yourself. Do you need the error corrected? Do you need a change in approach going forward? Do you need to understand what went wrong so you can fix a process problem? Or do you need to establish, for the first time, that you will hold this person to a standard they weren’t expecting? Sometimes the accountability conversation isn’t really about the mistake at all, but about setting a precedent. Know which one you’re in, because it changes what you say and how much time you spend on it.

---

Stage 2: Understand why your instinct is probably wrong

New managers in this situation default to one of two patterns, and both create problems that outlast the conversation itself.

The first instinct is to soften. You lead with reassurance, bury the critical point inside encouragement and leave the conversation feeling like you’ve addressed it when you haven’t. The person walks away thinking everything is fine, because your tone told them it was, even if your words technically said otherwise. This is the most common failure mode for managers who were previously well-liked peers, because the softening reflex is exactly what made them good colleagues. The problem is that it doesn’t work from a position of authority. When your peer says “don’t worry about it,” it’s a kindness. When your manager says it, it’s a signal that mistakes don’t have consequences, and the rest of the team notices.

The second instinct is to over-formalise. You’ve read somewhere that feedback should be structured, so you go in with a framework, a documented example, and a tone that sounds like it belongs in a performance review. The person, who last week was getting casual advice from you over coffee, is now sitting across from someone speaking in HR cadences. The message lands, but the cost is disproportionate. They don’t just hear the feedback; they hear that the relationship has been replaced by a process. For a first accountability conversation, that’s usually more damage than the situation warrants.

The move that works is direct and human. You name the issue, explain the consequence, explain your reasoning and then give them space to respond. It’s uncomfortable for about five minutes, and then it’s done clearly, which is better than the weeks of ambiguity that the other two approaches create.

The full module continues with Stage 3 (the AI prompt that prepares the actual conversation, tailored to your situation), Stage 4 (the debrief prompt for after it’s happened), and Stage 5 (how to adjust when the person cries, gets defensive, goes silent, or when the mistake was partly your fault).

---

👇 Steal My Toolkit

The newsletter covers ideas, frameworks and honest takes on consulting practice. The paid tier is where those ideas become usable: you get templates you can open in a project, prompts you can run today, and research tools built from over a decade of fieldwork.

Paid members get instant access to:

• Consulting with AI Series: the custom AI prompts I use in my own management consulting work, explained and ready to adapt.

• Full Course: Asking Questions Like a Pro - A Practitioner’s Guide to Mixed Methods Research ($199 value): practical research techniques refined across 10+ years of consulting engagements, covering design, facilitation and analysis.

• Practical Guides, Handbooks, Workbooks and Templates: premium resources from paid posts or 70% off discounts for my Gumroad assets.

• Cozora discount (up to $360 off): up to 50% off a Cozora subscription to learn AI from practitioners who use it in real work.

Free subscribers aren’t left out either.

• Leader Tools Cards: 10% off with code ANDREA10 at leadertools.co/ANDREA10

• Cozora welcome discount: 10% off with code WELCOME10 at cozora.org

• Demystifying Academic Research - A practical guide for navigating academic research without a PhD: Available for free (pay what you can, $0+) via Gumroad

Disclosure: I earn a referral fee if you purchase through my links, at no extra cost to you.