There’s a conversation I haven’t had to have yet, and I think about it more than any conversation I’ve actually had.
It goes like this: someone on my team — someone I eat lunch with, joke with, genuinely like — isn’t performing. And I have to sit down across from them, as the person who writes their performance review, and say so. The friendship and the role collide in one meeting, and whatever I’ve built up until that moment determines whether both survive.
Five months into managing, this is the tension I find least discussed and most real: you are a colleague and a manager at the same time, and the standard advice for handling that is, I think, wrong.
The standard advice is distance #
Almost everything written for new managers says some version of: create separation. Don’t get too close. You can’t be their friend anymore. Professional distance protects your objectivity and their clarity about the hierarchy.
I understand where it comes from. Distance does make the hard conversations mechanically easier — it’s simpler to deliver bad news to someone you’ve kept at arm’s length. Favouritism is a real failure mode, and distance is a blunt but working defence against it.
But look at what distance actually optimises for: it makes the manager’s worst days easier by making the team’s ordinary days worse. Every day that people work for someone deliberately unknowable, they hold back a little. They polish their status updates. They stop saying “I’m stuck” early, which is the only time “I’m stuck” is cheap to fix. Distance buys you comfortable authority and pays for it with signal — and signal is the thing a manager can least afford to lose.
Distance is the lazy version of authority. It substitutes hierarchy for trust because hierarchy comes free with the org chart.
Where authority actually comes from #
The Sinek line I keep returning to says leadership is not about being in charge, it’s about taking care of those in your charge. I’d add the operational version: authority is granted by the org chart, but it’s only honoured because of how you behave.
People don’t follow the title. They comply with the title. What they follow — what makes them accept a hard decision, take critical feedback seriously, tell you the truth when it’s expensive — is a track record. Fair calls, made consistently. Credit pushed down, pressure absorbed. Feedback given early and privately, not stored up for the review. Saying “I got that wrong” in front of everyone when you did.
None of that requires distance. All of it requires closeness — you cannot take care of people you’ve decided not to know. That’s what I mean by authority through companionship: not authority despite being close to the team, but authority built out of being close to the team. The trust you accumulate as a colleague is the only currency that makes the manager moments work.
The boundaries that actually matter #
Companionship without boundaries is just favouritism with better vibes. The line has to exist — I’ve just stopped believing it’s a line of distance. It’s a line of role clarity. The rules I’m holding myself to:
Name the mode. Most of the week I’m a colleague: in the code review, in the banter, in the “this vendor is driving me insane” venting. Sometimes I’m the manager: comp, feedback, priorities, the calls only I can make. The failure isn’t having both modes — it’s letting people guess which one is speaking. “I’m putting the manager hat on for a minute” is a clumsy sentence that does a lot of work.
Friendship can’t buy anything. The moment liking someone gets them the better project, the softer feedback, the benefit of the doubt someone else wouldn’t get, the whole structure is rotten — and the team knows before you do. Teams have perfect telemetry for fairness. The closer I am to someone, the more deliberately boring I have to be about the decisions that touch them.
Hard conversations are mine and they happen early. The real test of the friendship-authority balance isn’t the review meeting. It’s whether I flag the pattern in week two, as a colleague who’s paying attention — or sit on it until it’s a formal problem, because raising it felt awkward. Deferred feedback is where companionship curdles into cowardice. I wrote in month one that I was afraid of softening things I shouldn’t soften. Five months in: still the thing I check myself on most.
Some loneliness is the job. There are things I can’t share — comp discussions, org changes, who’s struggling. Carrying those alone isn’t distance from the team; it’s the fee for being trusted with them. I’d rather absorb that quietly than spread it as ambient anxiety.
The test I’m holding myself to #
Here’s how I’ll know if any of this is working, when the conversation I opened with finally arrives:
If I’ve done the colleague part right, the feedback won’t be a surprise — they’ll have heard the early, informal versions of it from me already. If I’ve done the manager part right, they’ll trust that the assessment is fair even while they hate hearing it. And if both hold, the friendship survives the meeting. Not unchanged, maybe. But intact, because it was never resting on me pretending everything was fine.
If the friendship can’t survive honest feedback, then it wasn’t companionship — it was mutual comfort, and it was always going to break at the first real test of the role.
I haven’t had to run this test yet. That’s the honest caveat on everything above: it’s a framework I believe and haven’t fully paid for. People who’ve been both the friend and the manager in that meeting — I want to know what actually happened. Find me on LinkedIn.