When Leadership Promises Don't Survive the Reorg

Someone on your team was told they were next in line. They got the expanded scope, the stretch assignments, the responsibilities that come with the next level. They were introduced internally as the interim for that role. Then the role went to an external hire, and nobody explained why.

If you’ve managed engineers in enterprise organizations, you’ve seen some version of this. The specifics vary: sometimes it’s a promotion that evaporated after a budget freeze, sometimes it’s headcount that was approved and then quietly pulled back, sometimes it’s a project direction that leadership championed until they didn’t. The pattern is the same. A commitment was made, the team reorganized their effort around that commitment, and then the commitment disappeared without acknowledgment.

Why this pattern is the hardest to repair

Broken promises create a specific kind of damage that the other trust patterns don’t. Information hoarding makes people feel excluded. Credit theft makes people feel invisible. Micromanagement makes people feel undervalued. But broken promises make people feel foolish. They believed something, reorganized their lives and careers around it, and it wasn’t real. The emotional residue isn’t anger at the institution. It’s embarrassment at themselves for trusting.

That’s why the standard “I’m going to be more transparent” fix doesn’t work here. The team’s problem isn’t that they lacked information. It’s that they had information, they believed it was a commitment, and it turned out to be aspirational at best. More transparency doesn’t address the core wound, which is: how do I know the difference between a real commitment and a hopeful statement?

The promise lifecycle: why commitments break

Before you can repair this, it helps to understand the mechanics of how promises break in large organizations. It’s rarely malice. It’s a chain of good intentions meeting structural reality.

A VP tells a director they can promote someone next cycle. The director tells the EM. The EM tells the engineer. Each handoff adds confidence. The VP said “if budget allows,” the director heard “we’re planning to,” the EM communicated “you’re getting promoted,” and the engineer heard “it’s done.” By the time the budget freeze hits or the reorg reshuffles priorities, the engineer has been operating as if the promotion is certain for months. And no one in the chain explicitly lied.

The second common pattern is the external hire override. A team member is told they’re being developed for a role, does the work at that level for six months or more, and then the organization decides they need someone with a different background. Maybe it’s a strategic pivot, maybe it’s a new VP who wants their own people, maybe it’s a genuine skills gap. The reason doesn’t matter to the person who spent six months proving themselves for a role that was never actually theirs to earn.

Understanding this isn’t about making excuses for leadership. It’s about knowing what you’re actually repairing. If the team thinks management deliberately deceived them, your approach needs to address betrayal. If the team understands the mechanics but is frustrated by the silence afterward, your approach needs to address the gap between what was intended and what was communicated.

The repair

Week 1: Acknowledge the specific promise, not just “the situation.” The worst thing you can do is speak in abstractions. “I know things have been difficult” tells the team nothing. If the team was promised a promotion that didn’t happen, name it: “I understand that [person] was expected to move into [role], that didn’t happen, and the reasoning was never communicated clearly.” You don’t need to assign blame. You need to demonstrate that you know exactly what happened, not a vague summary of it.

Week 2: Explain the constraint system, not just the outcome. What the team actually needs isn’t an apology for the broken promise. They need a mental model for how commitments work in this organization so they can protect themselves in the future. I’d share something like this: “Here’s what I’ve learned about how promotion decisions work here. The EM recommends, the director approves, and finance has a veto based on budget. That means any commitment that hasn’t cleared all three gates is a forecast, not a guarantee. Going forward, I’ll always tell you which gate we’re at.”

This does two things. It gives the team agency by helping them evaluate future promises themselves rather than depending on management to be honest. And it signals that you’re not going to pretend the system is simpler or more fair than it is.

Weeks 3-4: Create a visible artifact that tracks commitments. This is where the repair becomes structural, not just conversational. I’ve done this as a simple table in a team wiki: commitment, current status, last updated, gates cleared. It lists active commitments the team is operating under: promotion timelines, headcount plans, project priorities, technology investments. Next to each one, I’d note the current status and which approval gates it has cleared.

This feels uncomfortably exposing the first time you do it. You’re essentially saying “here are the promises I’m making and here’s how certain I am about each one.” But that exposure is exactly the point. It makes it impossible for commitments to quietly disappear. If something changes, the team sees it change, and you have to explain why.

The person who was passed over

There’s almost always one person at the center of the broken promise. They’re the one who was told they were getting promoted, or who was doing the work at the next level. And they’re the one watching you most carefully.

If I were inheriting this situation, I’d have a direct 1:1 with that person within the first week. Not to relitigate the decision, because I probably can’t reverse it. But to acknowledge what happened, ask what they want now, and be honest about what I can and can’t influence. “I can’t undo what happened. I can make sure it doesn’t happen again on my watch, and I can advocate for you in the next cycle with specific evidence. But I want to know: is that enough, or have you already decided this organization can’t give you what you need?”

That last question is hard to ask, but it’s respectful. Some people will stay and rebuild trust. Some have already decided to leave and are just waiting for the right offer. Pretending the second group doesn’t exist wastes both your time and theirs.

This framework assumes the broken promises were organizational failures, not deliberate manipulation. If the previous manager was actively using false promises as a retention tool, knowing they couldn’t deliver, the team didn’t just lose trust in the system. They lost trust in the act of being managed. That’s a harder repair, and the commitment tracking artifact becomes even more important because it’s proof that your commitments are falsifiable, not just words.

This is Part 2 of a series on trust repair for engineering managers. Part 3 covers the second pattern: when a reorg happens and nobody tells the team. Have you ever used something like the “promise lifecycle” framing to explain to a team why a commitment fell apart? What landed and what didn’t?