You’ve just been named team lead. Alongside the news, you’ve been told that the person you’ve worked beside for five years, who you’ve always gone to for a straight answer, now reports directly to you. That first moment after the announcement, the glance across the office, the team watching to see how both of you handle it: that’s the thing that tells the room what kind of manager you’re going to be.
The practical playbook for this is simpler than the emotional reality of that moment. But only if you act on it early.
What does leading former peers actually involve?
Moving from peer to manager is less about authority than about clarity. You need three things: explicit boundaries around who decides what, a way to separate friendship from management decisions, and standards that are visible to the whole team. Leadership advisers consistently flag this as one of the hardest first-line moves, because it asks you to change the relationship’s operating rules while the relationship itself continues.
The key distinction is that the authority is now real, even if the friendship hasn’t changed in other ways. Without a deliberate reset, the team defaults to how things were before. You can spend months correcting drift that one early conversation could have prevented.
The reset conversation is a clear exchange about what has changed: who makes decisions on client allocation, how feedback will work, and what the formal channel looks like for performance issues. The social side of the relationship can stay largely intact. What has to change is the operating layer underneath it.
Why does this matter for your business?
In a firm of 5 to 50 people, every staffing decision is visible to the whole team. Who gets which client, who covers a difficult account, who takes time off during a busy period: all of it is watched. When a manager is also a friend to one team member, the team’s tolerance for inconsistency drops sharply. A decision that looks like a favour can destabilise a group that was otherwise working well.
The Equality Act 2010 adds a practical edge to this. Biased treatment, even when well-intentioned, can become an HR or employment tribunal issue if it falls along a protected characteristic: gender, age, disability, or similar grounds. A consistent pattern of exceptions that benefits one person is enough. Bad faith has nothing to do with it.
The ICO’s guidance on fairness and transparency under UK GDPR adds another layer. If you know personal things about a colleague’s health, finances, or family situation because you were friends before you became their manager, those facts cannot travel into management decisions without appropriate grounds. Friendship does not create a licence to act on private information in a work context.
Where does the relationship tend to break down?
Three patterns cause the most damage in practice. First, feedback that only ever arrives as banter: the colleague who has always taken your criticism as a joke no longer knows when you are serious. Second, switching between friend and manager in the same conversation without saying which mode you are in. Third, making one exception for someone you know well, then finding that three others had the same need and said nothing.
Each has a direct fix. For feedback: make the shift explicit. Saying “I’m talking to you as your manager now, not as a colleague” feels awkward the first time. Say it anyway. The alternative is months of ambiguity that the team member reads as inconsistency and the rest of the team reads as favouritism.
For the mode problem, Odgers’ guidance on managing former peers recommends explicitly signalling which hat you are wearing before a difficult conversation. The shorthand matters: “manager hat on” changes the frame immediately and reduces the chance of the feedback being received as a personal comment from a friend.
For exceptions: use process language consistently. “I’m allocating this based on workload and deadlines, not on who asked.” Saying that once to the team member resets the expectation. Saying it to the whole team, when the context invites it, stops speculation before it starts.
One background pattern worth addressing at the same time: the NCSC flags informal access-sharing habits as a common security risk in close-knit small firms. Shared passwords and everyone using the same admin login tend to persist in teams built on friendship. The UK Government’s Cyber Security Breaches Survey 2025 found that 43% of UK businesses reported a breach or attack in the preceding year. Tidying up access habits alongside the management reset sends a clear signal that the operating layer has changed.
When do you act quickly, and when do you hold back?
The reset conversation should happen in the first week, not the first month. Every day without it, the team is reading the dynamic and drawing conclusions. Documentation of performance issues starts from day one: “we’ve been friends for years” should never be the reason a pattern went unrecorded. Outside that, much of the early awkwardness resolves on its own, and acting on every uncomfortable moment creates more tension than it resolves.
The things that warrant fast action: anything that looks like favouritism (correct it privately if it hasn’t been noticed, openly if it has), any performance pattern that affects other team members, and any time the friendship is being used as grounds to push back on a clear management decision. If someone says “but we’re mates” when you give them feedback, that is the signal to have the explicit conversation rather than waiting.
The things that don’t need a reaction: a slightly cooler tone for the first few weeks, a joke that used to land and now doesn’t, the natural recalibration that happens when any relationship changes. Leadership sources including Odgers, Let’s Grow Leaders, and Robert Half note that the first few months are predictably bumpy and that a manager who stays consistent through that period generally finds the relationship adjusts.
One situation that does require fast action: if the friendship is close enough that you genuinely cannot make hard calls, adjust the reporting line. The FCA’s position on non-financial misconduct reinforces the broader UK governance norm that leadership behaviour must support accountability, and that informal relationships cannot override standards or proper escalation. Handing over line management to someone better placed to hold it is the right move, not a weakness.
What concepts sit alongside this challenge?
Three ideas run underneath the practical advice. Role clarity covers who decides what in a given situation, and it matters because ambiguity is where friendship fills the gap in ways that can look like favouritism. Escalation discipline covers knowing when to hand a reporting relationship to someone better placed to manage it. Sounding board practice covers getting candid conversations outside the team, so you stop pressure-testing management decisions on the people you now manage.
On role clarity: write down the decision rights for the most common calls, even informally. A shared note on who decides client allocation, leave approval, and workload distribution removes ambiguity before it turns into an accusation. If everyone can see the criteria, the decision is less personal.
On sounding boards: several leadership sources, including Odgers and Let’s Grow Leaders, recommend that a new manager actively builds a non-team peer group, whether a mentor, a coach, or a board adviser. The purpose is to have somewhere to put the candid conversations that the team can no longer carry. Use it before decisions, not just after things have gone wrong.
The transition from peer to manager asks you to change the operating rules around a relationship that matters. The more explicit you are, the sooner you act, and the more consistently you hold the same line across the whole team, the better the outcome tends to be for everyone involved. If you’d like to think through how this fits your specific situation, book a conversation.
