Your Manager Changed. Your Coach Didn't.
A re-org. A one-month deadline. And two direct reports who needed to move to a different manager. What I said to them, and what I kept doing afterward.
The re-org needed to be done in a month. About a hundred engineers, organized by function, were moving to product-aligned teams. Ownership was unclear everywhere. The goal was to fix that.
The hardest part of the re-org
Designing the new structure, defining ownership boundaries, and setting up new reporting lines was hard enough. The conversations I remember most were the ones I had with two of my direct reports.
One was a high performer on the backend side. The other was a recent graduate, still early in their career. Both were moving to a different manager.
For the high performer, the decision was straightforward in reasoning: the product team being formed needed someone with their technical depth, and the new domain was the right fit for their strengths. That didn’t make the conversation easy. You don’t move a high performer without a credible explanation for why it’s good for them.
For the new graduate, my concern was different. They were still developing. A reporting change at that stage could disrupt their trajectory if nobody stayed accountable for their growth.
What I said to both of them
I used the same line with both of them: “Your manager changed, but your coach didn’t.”
To make that real without cutting across the new manager, I took on the Vice-Manager post for the new group as a second role alongside my own. That gave me the standing to continue regular 1:1s and check-ins in a formal capacity, not as an outsider reaching back in.
My focus during the re-org was to communicate with all affected team members before the rumors could fill the gap. People needed to understand the rationale before the questions built up.
What I'd do again in the same situation
-
Have the direct conversation before the announcement
Affected people should hear the news from their current manager first, not through an org chart update or a team-wide email. The personal conversation needs to happen before anything else is communicated.
-
Explain the reasoning, not just the decision
People don't need to agree with the re-org to accept it. But they need to understand why. For the high performer, the new domain needed their depth. For the new graduate, the new structure had better context for their growth track. Both deserved a real reason, not a talking point.
-
Make a commitment you will actually keep
I told both of them: your manager changed, but your coach didn't. To back that up without overstepping, I volunteered to take on a secondary manager role for the group. If you say you'll stay involved, create the structure that makes it legitimate.
-
Get ahead of the rumor timeline
Uncertainty fills fast. Transparent communication with affected team members, before the questions start piling up, is what keeps trust intact. Rumors form in the gap between a decision and an explanation.
What came of it
The re-org completed within the one-month timeline. The new structure created clearer ownership across teams. One of the earliest signs it was working: incoming requests from other teams started landing with whoever owned that domain, rather than bouncing between groups with overlapping responsibilities.
Both direct reports transitioned well. The high performer began mentoring others in the new group, multiplying their impact well beyond their own output. The new graduate continued developing through the reporting change.
Reorgs don’t succeed because of org charts. They succeed because people trust the process.
That trust comes from how you handle the individuals most affected. The people being moved, the people losing direct reports, the people who don’t understand why their team looks different: they’re all watching how the transitions are handled. What they see in those conversations is what they’ll carry about how the organization treats people.
Those conversations are the job.