When something fails, the boxes move. The sentence “I got this wrong” stays where it was, unsaid.
You know the email. It lands late on a Thursday from someone senior, under a subject line about evolving our structure. From Monday this team reports over there. Two functions are combining. A new role has been created to drive alignment. There’s a diagram, and a closing line about being excited for the next chapter.
People read it twice. The new structure won’t make sense for months anyway, so that isn’t what they’re looking for. They’re looking for the one sentence that would explain why any of this is happening, something like “we got this wrong,” and it’s never in there.
That gap is the point of the email. A reorg is the one response to failure that requires nobody to admit anything. The team that owned the failure stops existing, and its people are spread across three new boxes, so the failure now belongs to no one. The leader who designed the old structure is the one announcing the new one, which turns the author of the problem into the architect of the fix in a single send. And the new structure gets a grace period, because everyone agrees a reorg needs six months to bed in. By the time anyone could measure it, the original failure is old news, and whoever brings it up is told to stop living in the past.
From the outside it reads as decisive leadership. Inside, people watch it change everything except the decision that went wrong.
The habit is older than org chart software. In 1957 Charlton Ogburn, who had served with Merrill’s Marauders in Burma during the Second World War, wrote in Harper’s that his unit kept being reorganized just as it began to work as a team. He called reorganizing “a wonderful method it can be for creating the illusion of progress while producing confusion, inefficiency, and demoralization.” The line gets passed around online as the words of the Roman writer Petronius, because it sounds that old. Ogburn wrote it, and the Thursday emails keep proving him right.
The person who pays first is usually whoever saw it coming. In most failed initiatives someone said early that it would fail, and was told to be a team player. When the answer to the failure is a reorg, the decision that caused it never gets examined, so their warning never gets vindicated either. Often their role is the one that quietly disappears from the new chart. Everyone notices, and the next time something is about to go wrong, nobody says so.
The people who stay pay more slowly. They learn that failure is survivable as long as nobody names it, so they hide the next one earlier and for longer. What they took from the reorg was never “fix what broke.” It was “don’t be standing where the blame lands when the boxes move.” The leader pays as well, mostly without noticing, because people can tell a structure that changed because someone learned something from one that changed so nobody had to.
Some reorgs are honest. Strategy really does change, and sometimes the old structure was built for a world that has gone. Redesigning the structure that produced a failure is one of the most useful things a leader can do, which is exactly why it is so easy to fake.
You can tell which one you’re looking at in under a minute. Does the announcement name what failed? Does it say whose decision caused it? And does the person who designed the old structure hold the same job in the new one? If the answers come back no, no and yes, you’re looking at a reshuffle. Real structural reform goes after whatever produced the failure. A reshuffle leaves that untouched and gives it a new reporting line.
The honest version takes four sentences. “We built this wrong. I approved it. Here’s what we learned and exactly what changes. Here’s what I’ll do differently.” Saying that out loud costs the person who says it, which is why you so rarely hear it, and why people follow the leaders who do. Any leader with authority can redraw the chart on a Thursday afternoon. The harder job is writing the sentence the email always leaves out.
Your turn. Think about the last reorg where you work. Did anyone ever say what had actually failed? Tell me in the comments.
This is a field note from Trust Architecture, a framework for building organizations where the truth survives contact with power. New here? Start with The Framework.
Free to read and share under CC BY-NC-ND 4.0. © 2026 Ankush Chowdhary. See Ethics and Transparency for how this work is produced.

