Leading a Team You Didn't Hire: Lessons From My First Reorg
The first time I inherited a team through a reorg, I made a mistake that's common enough to have a shape you can recognize: I led it the way I'd have led a team I'd built myself, assuming the trust and shared context that comes from that was already there. It wasn't, and pretending otherwise cost me the first two months.
A team you build hires people who already buy into your working style, because they chose to join it. A team you inherit didn't choose you, has its own established norms, and is, reasonably, evaluating whether you understand and respect what already worked before you arrived. Coming in with a strong point of view about what needed to change, before I'd earned any credibility with that group, read as dismissive of everything they'd built, even when I didn't mean it that way.
What actually worked, once I recognized the mistake: spending the first few weeks almost entirely in listening mode, one-on-ones asking what was working, what wasn't, and what they wished a new lead would understand before making any changes. Not performative listening before implementing a plan I'd already made, but genuinely letting what I heard shape the plan.
The second lesson: inherited teams are watching closely for whether you'll dismiss their prior leadership to make yourself look better. I made a point of publicly crediting decisions and processes that were already working well, even ones I might have done differently, because undermining the previous structure to elevate myself would have cost trust I hadn't earned the right to spend.
Leading a team you built is about casting a vision and finding people who share it. Leading a team you inherited is about earning the right to cast a vision at all, first. Skipping that step doesn't save time, it just moves the cost to later, when it's harder to recover from.
Related articles
Enjoyed this? Get more like it.
Weekly insights on delivery, leadership, and AI — straight to your inbox.