Managing former peers at Google fails when you keep behaving like a teammate with a title upgrade. Your first job is not to prove authority, but to make decisions legible, predictable, and fair enough that former peers stop negotiating the basics with you. The managers who survive this transition do not become harsher; they become more explicit about standards, feedback, and the boundary between friendship and management.
Managing Former Peers at Google: A First-Time Manager's Survival Guide
TL;DR
Managing former peers at Google fails when you keep behaving like a teammate with a title upgrade. Your first job is not to prove authority, but to make decisions legible, predictable, and fair enough that former peers stop negotiating the basics with you. The managers who survive this transition do not become harsher; they become more explicit about standards, feedback, and the boundary between friendship and management.
Not sure what to bring up in your next 1:1? The Resume Starter Templates has 30+ high-signal questions organized by goal.
Who This Is For
This is for the engineer or PM who just moved from contributor to manager inside the same Google team, is now running 1:1s with people who used to challenge them in docs, and has already heard some version of "this feels different" in a skip-level or private chat. It also fits the manager who inherited former peers through a reorg and now has to reset expectations without making the team feel punished for knowing them well.
Why does managing former peers at Google feel harder than other first-time manager transitions?
This transition is hard because status changes before habits do. Former peers still remember how you argued, how fast you replied, and which battles you used to avoid. The problem is not trust. The problem is role confusion, and role confusion gets interpreted as favoritism, indecision, or theater.
In a manager calibration, I once watched a director stop the room on a newly promoted manager and ask, "If she were out tomorrow, who would own the call?" The room had no answer because everyone still expected the old peer to behave like an individual contributor with extra meetings. That is the real fracture. A first-time manager is not being tested on charm. They are being tested on whether the team can function without translating every decision through the old relationship.
Not being liked, but being legible, is the bar. Google's doc culture makes this sharper because every fuzzy choice comes back in writing later, where the emotional tone has been stripped away and only the ambiguity remains. If you try to preserve old-peer equality in the room, you create an invisible hierarchy outside it. The team feels that gap immediately.
The counter-intuitive part is that the team does not need you to become more distant. It needs you to become more consistent. Former peers can tolerate a changed relationship. They cannot tolerate a manager whose standards change with mood, audience, or who is asking. That inconsistency is what turns a normal transition into politics.
> 📖 Related: 1:1 Framework vs OKR Review for Google PMs: Integrating Career Growth
What should the first 30, 60, and 90 days actually accomplish?
The first 90 days should make your authority predictable, not impressive. By day 7, each former peer should know what you own and what you will no longer negotiate in corridor conversation. By day 30, the team should be able to say, in plain language, how you decide, how you give feedback, and what escalation looks like. By day 60, at least one real disagreement should have been handled cleanly in public and one correction privately. By day 90, the group should stop treating your role as a trial balloon.
In practice, the first 30 days are mostly about removing ambiguity. The temptation is to prove yourself by adding meetings, listening harder, or acting like the most collaborative person in the room. That is the wrong instinct. Not more meetings, but fewer ambiguous ones. Not more consensus, but clearer ownership. The better signal is a short decision note, a written norm, or a clean end to a discussion with one owner named.
I have seen this go wrong in a planning meeting where the new manager kept asking for more opinions after the decision was already obvious. The former peers were polite, but they were reading the room: if the manager cannot close a decision in a small group, they will not be trusted in a hard one. One decisive sentence would have done more than twenty minutes of consultative theater. Authority at this stage is not volume. It is consistency.
There is also a structural lesson here. The first 30 days are not for proving that you understand every detail. They are for proving that the team can predict what happens next. That is a managerial skill, not a social one. People who confuse the two usually become performative listeners and unreliable deciders.
How do I give feedback to someone who used to be my equal?
Feedback lands as a status event before it lands as content. That is the part many first-time managers miss, and it is why their first corrections sound apologetic or overbuilt. The former peer is not only hearing what changed. They are hearing that the social contract changed. If you avoid that reality, the conversation gets slippery and fake.
In a 1:1, I once heard a former peer say, "You never used to talk to me like this." That sentence is not a complaint about tone. It is a protest against the loss of symmetry. The right response is not a speech about leadership growth. It is a precise statement of the behavior, the impact, and the next standard. The issue is not honesty, but delayed honesty. Delayed honesty always gets paid back with resentment.
Not vague empathy, but specific respect. People do not need you to soften the bar so they can stay comfortable. They need you to make the bar visible early enough that they can meet it or argue with it on substance. A former peer who was once your dinner companion can still receive hard feedback cleanly if the rules are explicit. The manager who survives this transition knows that friendliness is not the same thing as leniency.
A useful frame is that feedback should describe the work, not the relationship. If you talk as if the relationship itself is broken, the other person will defend the relationship and ignore the work. If you talk about the work with a stable tone, the relationship has a chance to absorb the change. That is the difference between a manager and a frustrated peer with access to a 1:1 calendar.
> 📖 Related: 1on1 Tool vs Google Doc for New Manager Meetings: Which Boosts Productivity?
What do I do when a former peer challenges me in public?
Do not litigate status in the room. Public pushback from a former peer is usually a test of decision rights, not a revolt. If you answer emotionally, you teach the team that disagreement now carries a social penalty. That is how managers turn small disagreements into political weather.
In a staff meeting, a teammate who had been equal to the new manager for years pushed back hard on a roadmap call. The worst response would have been a defensive debate in front of the group, because it makes the room about the relationship instead of the decision. The better response was shorter: acknowledge the concern, restate who owns the call, and move the disagreement into the right forum. The team does not need a performance. It needs containment.
Not dominance, but bounded authority. The best managers at Google do not win every public exchange. They keep the room usable. They know when to say, "I hear the risk, I will take this into the doc and close it by 3 p.m." That sentence does three things at once: it respects challenge, it reasserts ownership, and it removes the audience from the argument. The room watches that move carefully. If you can contain conflict without performing it, people start trusting the role, not just the person.
This is where first-time managers often mistake speed for strength. Fast replies are not the same as firm decisions. The point is not to shut people up. The point is to stop the room from turning every disagreement into a referendum on whether you deserve the chair.
How do I handle promotions, compensation, and fairness without losing credibility?
This is where vague managers lose the room. Former peers do not just watch how you give feedback. They watch whether you apply standards the same way when scope, promotion, or compensation enters the picture. The judgment is not whether everyone gets the same outcome. The judgment is whether everyone can see the criteria.
In a promo debrief, the hardest question is rarely about raw performance. It is whether the newly promoted manager can evaluate friends without flinching and disagree without hiding. A director in one of those rooms will not say that out loud, but the room knows it. If you overcorrect by treating everyone identically, you create a different lie. Fairness is not sameness. Fairness is consistency plus explanation.
The practical test is whether your team can repeat the bar without you in the room. If the answer changes depending on who is asking, you have not built a system. You have built a mood. Not secrecy, but visible standards. Not personal loyalty, but reusable criteria. That is what keeps former peers from assuming favoritism when decisions do not go their way. The more senior the team becomes, the less patience it has for improvisation dressed up as empathy.
Comp conversations are especially sensitive because they expose whether your management style is real or decorative. If you avoid the topic until review season, the silence gets interpreted as cowardice or favoritism. If you explain the criteria early and keep the bar stable, people may still disagree with the outcome, but they will not confuse disagreement with unfairness.
Preparation Checklist
The only useful preparation is to make your authority visible before people start testing it.
- Write down the three decisions that are now yours alone, then stop pretending they are still group decisions.
- Reset every 1:1 with a sentence about role, expectations, and cadence.
- Publish your working norms for docs, meetings, and escalation by day 30.
- Give one correction privately within a week instead of waiting for review season.
- Keep friendship out of decision rooms and keep decision language out of friendship rooms.
- Work through a structured preparation system (the PM Interview Playbook covers first-90-day narratives and conflict examples with real debrief examples).
Mistakes to Avoid
The wrong moves are obvious once you watch the room react.
- Pretending the promotion changed nothing. BAD: "We're the same as before, so just keep doing what you do." GOOD: "We're still close, but decision rights changed and I will be explicit when I am deciding."
- Using consensus to avoid ownership. BAD: "What does everyone think?" when the answer is already set. GOOD: "I am deciding X, I need challenge on Y, and I will close it by Thursday."
- Delaying correction because the relationship feels fragile. BAD: letting a problem sit until review season. GOOD: raising it in the next 1:1 with one concrete example and one new bar.
FAQ
The short answers are blunt because the same mistakes repeat.
- Should I tell former peers I feel awkward?
No. Say the role changed and you will be explicit. Do not ask them to carry your discomfort. They already know the situation is different.
- Can I stay friends with former peers?
Yes, but not in the room where you manage them. Friendship survives when boundaries are clear. It fails when you use closeness to avoid hard calls.
- What if one former peer never accepts me as manager?
If they cannot work inside the contract after clear expectations, the problem is not chemistry. It is fit, and fit has to be managed directly. Waiting usually just spreads the damage.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.