Episode 026 – 3 Signs You Never Renamed the Relationship With Your Former Peer

Summary

Getting promoted over a former peer is a structural event. The relationship isn’t. When the structural authority shifts and the relational contract doesn’t get updated, both parties default to the old agreement while the new one is in force, and that gap is where every managing-former-peers failure mode lives. Using a university friendship that unraveled after a promotion, and a company president who kept showing up to peer-level beer and wings long after the gap had widened, Chris names the mechanism and the fix: a deliberate, plain-language renaming that has to happen before the first hard ask. Three observable signs tell you whether the renaming actually happened or whether the old contract is still running the show.

Takeaways

• A promotion is a structural event. A relationship is not. One updates on a specific date; the other only updates when you explicitly rename it.
• If you don’t rename the relationship out loud, both parties default to the old contract while the new contract is in force. That gap is where the friend card gets played and feedback gets soft-pedaled.
• A deliberate renaming has three pieces: what stays the same, what doesn’t, and how you will handle the collision when it shows up. Without all three, the contract hasn’t actually changed.
• The renaming conversation is not a sit-down with HR language. It is a five-minute plain-language exchange that happens once, before the first hard ask, not after.
• Renaming is not a one-time event at the promotion point. It is a recurring calibration as the structural reality keeps moving forward.
• Three signs the old contract is still running: you soften requests for former peers that you would sharpen for new hires, you let feedback slide with one person that you would address with another, and you justify your authority instead of exercising it.

Transcript

This transcript was produced by robots and left as-is. Accuracy and elegance are not guaranteed.

I’d rather piss you off than my wife. That’s what one of my employees told me early in my management career.

 

Don had been a university friend. We’d hung out, we’d partied, we’d worked side by side for a few years. Then I got promoted to be his manager. And the bad part is neither one of us recognized what that actually meant. And I never renamed the relationship. Now Don wasn’t being unreasonable. He was operating on the contract he and I had implicitly maintained.

 

The contract said friends first, asks are negotiable.

 

The structural shift was instant, but the relationship contract wasn’t. And only one person could drive that renaming. That was me. It was my job and I didn’t do it.

 

A promotion is a structural event. It happens on a specific date. New authority, new accountability, new scope, done. A relationship is not a structural event. It’s a running contract built out of prior context, shared norms, and unspoken expectations. It doesn’t update on its own. If you don’t rename the relationship out loud,

 

Both parties default to the old contract even when the new contract is in force. That gap is where every managing former peers failure mode lives. The friend card, the soft pedaled feedback, the beer on Saturday, and the performance review on Monday colliding, with no one having named exactly what that collision looks like.

 

A deliberate renaming has three pieces. What stays the same, what doesn’t, how you’ll handle the collision when it shows up. So what stays? The respect, the history, the willingness to keep the friendship outside of work. That part doesn’t need to die. It just needs to be named so it’s not load-bearing for the work relationship. What doesn’t?

 

Asks are no longer negotiable in the same way. Feedback is no longer optional. Performance reviews are now structural, not social. And how you’ll handle it. When you have to make an ask that the friendship would resist, you name it as the manager asking, not the friend asking. That clarity is what makes both relationships viable. This conversation happens once.

 

Deliberately before the first ask that requires the new authority, not after.

 

People here rename the relationship and assume it means a serious sit-down with HR language. It doesn’t. It’s a five-minute conversation, and the words can and should be plain. Here’s roughly what I’d say now if I were back at that promotion point with Don. Look, we’ve been working side by side for a few years. We’ve gone for beer, we’ve vented about projects.

 

And bosses and clients. None of that changes. But starting Monday, I’m running this group. And that shifts a couple of things. When I come to you with an ask, it’s not me asking you for a favor anymore. It’s me asking as the manager. When something needs to change in your work, I’m going to tell you directly. Not because I’m being a hard ass, but because that’s

 

the job now. And if I don’t do it, neither of us is doing ours. The friendship stays, the contract changes. I wanted to name it out loud before we hit our first hard conversation. Because I’d rather we both know what we’re dealing with. That’s it. No HR script, no formal language. What makes it work is that you set it before the first hard ask. Not after. And that you said it at all.

 

Now there’s another way this plays out, and I saw it early in my career. The company was small, less than 10 of us. The president was very close to peers. We’d hang out, we’d go for beers and wings. It was pretty normal peer behavior, and it worked because the structural distance was small. As the years went on, the company grew. The president grew with it.

 

He’d show up to the same beer and wings in his tailored jacket, pulling up in his Porsche. The structural reality had kept moving. The social performance had not. The disconnect was loud. Not because he was a bad guy, and not because employees were resentful of the success. The disconnect was loud because the behavior pretended the gap wasn’t there.

 

We’d moved from peers to a very solid I’m your boss and you’re one of my employees. The performance of peer dynamics over that widened gap, it read as forced, even when the intent was generous.

 

The same mechanism as my Don story, just on a longer time scale. The structural reality moved, the relational contract didn’t get updated, and the cost showed up in the gap. The lesson? Renaming the relationship isn’t a one-time conversation at the promotion point. It’s a recurring calibration as the structural reality keeps moving forward.

 

If you’re wondering whether you’ve actually done this renaming or just assumed it happened on its own, here are three signs you haven’t. Sign one, you find yourself softening direct requests with someone you used to be peers with. The ask comes out as: Hey, do you think you could maybe instead of, I need this by Friday?

 

If you’d phrase it sharper with someone you didn’t have history with, you’re operating on the old contract.

 

Sign number two. The same issue gets a different response depending on the person. You’ll address a feedback gap directly with a newer team member and quietly let it slide with the former peer. The work is the same. The relationship is unfortunately doing the filtering.

 

Sign three, you find yourself explaining your authority instead of exercising it. You justify the ask. You add context, the structural reality doesn’t require. If you’re catching yourself building a case for why you can ask for something, the contract has not been renamed.

 

Back in episode 11, I talked about the calibration window. The conversation I should have had with Don fell squarely inside that window. But I waited. By the time push came to shove, it wasn’t a calibration anymore. It was a corrective action against a friendship.

 

The cost of descent had migrated entirely to Don. He was carrying all of the discomfort because I had structured the relationship so the discomfort had nowhere else to go.

 

The same logic applies to that slow burn version. If the president had named the changed reality earlier, the recalibration would have been small. He let it run, and the gap eventually had to be carried by everyone in the room at Beer and Wings.

 

So the question to leave with where is the structural reality of one of your relationships ahead of the contract you’re operating on? Specifically, what conversation are you avoiding because it would mean naming a change you’ve been pretending didn’t happen? That conversation is the work. Skipping it isn’t generous. It’s just deferring the bill until it’s much bigger.

No Comments

Sorry, the comment form is closed at this time.