What I Learned From Managing Former Peers

Engineering management guide · Updated October 2026

The promotion email goes out on a Tuesday. By Wednesday, the people who reviewed my pull requests last week report to me. Nothing has changed about the people, yet everything has changed about the structure around them, and about how my words land in the room.

In this guide I share what managing former peers taught me: how to hold authority without arrogance, how to handle the friend and the rival, where to draw boundaries, and how to resist the pull back to the individual work that got me promoted.

Name the shiftAmbiguity is worse than awkwardness, so say the change out loud
Earn it quietlyAuthority announced is authority you do not have yet
Do the new jobManagerial work first, individual contribution around it
01 · The reframe

The title is the easy part

The org chart hands you decision rights instantly. Legitimacy arrives slowly, and former peers make it harder in one specific way: they have a finely tuned detector for posturing.

Here is the asymmetry nobody mentions: I had weeks to get used to the idea, through conversations with my manager and private deliberation. My team got one announcement. I processed the transition alone, while they had to process it in front of me. Their awkwardness was not rejection. It was the adjustment I had already finished.

I also learned that the relationship did not move up a level. It gained an axis. Peer relationships are symmetric: either side can say no to the other. A reporting line is not, and no amount of friendliness removes that. Pretending nothing has changed is not kind. It is confusing for everyone involved, because people notice when authority has shifted, and if I refuse to name it, they are left to interpret the new boundaries for themselves.

02 · Authority without arrogance

Decisiveness with transparency beats ceremony

My first instinct was to reassure everyone that nothing changes. That instinct creates ambiguity, and ambiguity is worse than awkwardness. My second instinct was to perform authority: speaking last but always, invoking my title in disagreements, making small decisions slowly and visibly so everyone knew who decided. What actually worked was almost the opposite.

What earned legitimacy instead

  • Name the shift out loud. A two-minute opening in every 1:1, how I plan to work and what I need from them, removes months of guessing
  • Make decision-making visible. Here is what I heard, the trade-off I weighed, why I am choosing this, and what would change my mind
  • Admit gaps early. People forgive a manager who is learning. They do not forgive one who bluffs
  • Speak last, ask first. My take now carries title weight, so I downgrade it explicitly when it is just an engineering opinion, not a decision
  • Never borrow authority from the title. If I need the phrase “as your manager” to win an argument, I have already lost the argument I should have been having

A casual offhand comment from a manager reads as a directive, so I learned to label my words: thinking out loud versus this is a decision. Ambiguity from the boss is never neutral.

03 · The awkward relationships

Every former peer is a different situation

Not every relationship changed in the same direction. Some stayed almost exactly the same. Others developed a strange new static: jokes that landed differently, candor that got filtered, boundary-testing in small ways. Naming each dynamic once, in private, gave us language to navigate it instead of acting it out.

PersonWhat I learned
The friendRenegotiate explicitly, not with fake distance. When we hang out we are friends. Anything touching work decisions moves into the daylight of a 1:1
The rivalNeither appease nor marginalize. Acknowledge the disappointment once, then offer real scope and real visibility. Respect without capitulation
The better engineerThis is not a problem, it is the job. Ask for their recommendation and mean it. Proving technical dominance in reviews is insecurity, not leadership
The flatterersAgreement that arrived with the org chart is the title talking, not the idea winning. Watch for it and discount accordingly
The quiet skepticDo not treat it as a contest. Do what I said, when I said it, the same way for everyone. Consistency beats confrontation every time

One more thing about the friend: everyone watches for favoritism, including me. I found it worked to be slightly more careful with friends, not less: same standards, same feedback, same process for assignments, said out loud so it never reads as distance.

And the unexpected gift: because they knew me before, some reports will tell me things new reports never would, including when I am posturing. The people willing to call me on my nonsense are the most valuable ones I have. I protect them by never punishing candor.

04 · Boundaries

Boundaries protect both sides

Boundaries as a new manager from within feel selfish. They are not. Without them, former peers end up acting simultaneously as friends, advisers, and direct reports, which is an uncomfortable position I put them in, not one they chose.

Four boundaries I set explicitly

  • Information. Comp, performance, and reorg news stay above the line. When I cannot discuss something I say so plainly. Half-sharing to buy goodwill always costs more than it earns
  • Social. Lunches and coffee are fine. The venting channel about leadership is not, because I am now part of it. I still get drinks with the team, but I attend, I do not instigate
  • Time. 1:1s can drift into catch-ups with old friends. I protect the time for growth, feedback, and blockers, and keep the friendship for other hours
  • Emotional. My reports can no longer be my confidants about work. I found a new peer group in other engineering managers instead

When a former peer pings me to vent, I ask one question first: do you want me to just listen, or is this something you want me to act on. A complaint to a friend was just a complaint. A complaint to a manager might be a request, and my silence could be read as a decision.

05 · The prove-it trap

Two failure modes, one test

I have been guilty of both opposite failures. Overcorrecting: sudden formality, new rules without context, overruling decisions where I am not the expert, micromanaging whoever challenges me most. Undercorrecting: staying one of the team, avoiding hard calls, taking the toughest tickets myself, never saying no. The first is insecurity dressed up as authority. The second is avoidance wearing humility’s clothes.

The test I use now

Before a decision or a policy change I ask: is this for the team, or is this for my status. If it is the second, I stop. And when challenged publicly, I get curious first. Talk me through your thinking beats I already decided almost every time.

One hard truth underneath: I will lose likability, and some of it is permanent. Someone gets the mediocre review, someone never forgives a call, someone leaves. Trying to buy likability back with favors or softened feedback does far more damage than the distance it was meant to prevent.

06 · What peers taught me

Managerial work is the job, not the interruption

My real struggle was not with former peers at all. It was with my own habits. Technical work gives instant feedback: the pipeline turns green, the outage ends, the ticket closes. Management work gives slow, ambiguous feedback. A good 1:1 might prevent a resignation six months from now, and I will never see the resignation that did not happen. So I drifted back to the work I knew, and stayed on the critical path just this once, week after week.

What changed my behavior was watching other engineering managers and asking how they spent their time. They treated the calendar as a statement of priorities, delegated the interesting work instead of only the chores, refused to be the escalation path, and used technical credibility selectively: designs, sharp questions, risk spotting, but no code on the critical path.

What I changed in my own weeks

  • People work first. The first block of the day goes to 1:1s, feedback, and decisions waiting on me. Technical work comes after
  • No critical-path tickets. If someone is blocked on my individual work, I have put the team in the wrong shape
  • A weekly calendar audit. Hours on people, planning, and unblocking versus hands-on work shows what I really prioritized
  • Delegation as development. Handing interesting work to former peers is respect, not dumping, and I say that out loud
  • Count the invisible. A blocker cleared, a conflict defused, a person who stayed. I write them down, because they are real results

The question that reframed my days: if I am the one fixing this, who is doing my job. The honest answer was usually nobody. For the full version of this discipline, my guide on how I balance technical work and management covers leverage, calendar design, and escalation rules.

07 · 90-day playbook

What I would do in the first three months

Week 1

Name the change with every former peer

Explain how I will work, what I now own, and what I need from them. Decide information rules on day one and keep them, especially for confidential topics.

Month 1

Give the first small critical feedback early

Do not let it slide into month three. Early, small, specific, and clearly about the work sets the precedent for everything after. Talk privately to anyone who wanted the role and agree one concrete growth step.

Month 2

Audit the calendar and leave the critical path

Remove myself from every project where delivery waits on my individual work. Delegate one meaningful piece of work per person and say why I chose them.

Month 3

Ask the team how I am doing

Ask reports for feedback on my management directly, and ask a peer manager to sanity-check my read. Find the management peer circle early so reports never become my support group.

08 · FAQ

Popular questions about managing former peers

Q1Should I tell former peers that things will change?

Yes, and early. Silence leaves them to guess, and they will usually guess the worst. One explicit conversation about what changes and what does not replaces months of decoding behavior shifts.

Q2Can I stay friends with people who now report to me?

Often yes, on new terms. Be honest about what you cannot discuss, keep standards identical for everyone, and never ask a friend to protect you from the consequences of your own decisions.

Q3What if a former peer undermines me?

Address it directly and privately with specific examples. Do not escalate on the first incident, and do not wait for the tenth. If it continues, document it and involve your own manager.

Q4How much hands-on work should a new manager keep?

Enough to stay credible, not so much that the team depends on it. The test I use: could I drop it tomorrow without hurting delivery. Architecture reviews, risk spotting, and standards count. Feature ownership does not.

Q5How do I give hard feedback to someone who used to be my peer?

Early, small, specific, and private, clearly about the work and not the person. The first one sets the precedent, so do not let it slide. Withholding feedback to preserve a friendship betrays the rest of the team.

Q6What if someone on the team wanted my role?

Have the conversation early and in private. Acknowledge the disappointment without gloating or consoling, then make it practical with real scope and a growth path. If they would rather not report to me long term, I help make that move happen well.

Q7Should I still socialize with the team?

Yes, with adjusted presence. Lunches and coffee are fine. I attend team socials but do not instigate the late-night ones, because my presence changes what people feel free to say, and protecting their candor is part of the job.

Q8Is it easier to manage a brand-new team instead?

It might feel easier at first, but the skills built here carry into every team afterwards: naming the shift, setting boundaries, and delegating. You rarely get to choose the team anyway, so the former-peer transition is worth learning well.

Authority is not something you assert. It is something you earn by being clear, consistent, and useful.

The promotion changed my function, not my worth. The old relationships do not get restored. They get rebuilt on foundations that can hold the asymmetry: candor without venting, warmth without favoritism, care without being the buddy.

And the people who knew me before are the ones best positioned to keep me honest about the difference. At first I worried that was a boundary problem. Now I think it is the opposite.

Keep reading

Related guides on Sypalo.com