The Inflationary Trap: Why Your Reorg Is Already Doomed
Reorganizations don't eliminate friction—they inflate it across larger structures, making coordination harder to manage.
Leaders attempting to break down silos often fail because reorganizations don't resolve underlying dependencies. Like cosmic inflation stretching quantum fluctuations, rapid scaling amplifies small friction points into permanent structural features that outlast the org chart. Before restructuring, teams must decouple dependencies or explicitly plan for coordination costs.
by Felix Diallo In 2014, the BICEP2 experiment announced a discovery: primordial gravitational waves, the imprint of cosmic inflation on the early universe. A year later, the signal was retracted. What they’d measured wasn’t the birth of structure but dust in our own galaxy—a local contaminant that looked, from a distance, like a clean cosmic story. Leaders make a similar misreading during reorganizations. They spot friction between teams, label it “silos,” and redraw the org chart to break them apart. Six months on, the same tensions are back—only now they span larger groups, with more budget lines and more distance between decision and work. The reorg didn’t remove the friction. It inflated the underlying dependencies across a bigger canvas, locking them into something harder to undo. The mechanism isn’t personality or politics. It’s what happens when you scale without first decoupling the threads that force teams to collide. Think of a design group where one art director must approve every visual output. Before a growth spurt, that dependency causes daily negotiation among a few small teams. After a restructure, those teams become separate departments with their own roadmaps. The approval bottleneck now sits at a higher level, with more stakeholders and less tolerance for compromise. The original friction point didn’t disappear—it expanded, structuring the entire org chart just like cosmic inflation stretched tiny quantum fluctuations into the large-scale web of the universe. The pattern is this: rapid scaling acts as an inflationary epoch, taking manageable interdependencies and blowing them up into permanent structural features. Leaders then blame “silos,” but the silo is only the visible shape of a dependency that should have been resolved before the lines were redrawn. So what do you do instead? Before a restructure, map the informal handoffs, shared resources, and unwritten approval paths that currently generate friction. For each one, ask whether it can be decoupled—give each team its own dedicated resource, or define a clean interface that doesn’t require escalations. If decoupling isn’t possible, acknowledge that the reorg will make that dependency larger, not smaller, and plan for the coordination cost explicitly. Don’t let a restructuring freeze today’s workarounds into tomorrow’s hierarchy. The boxes you draw will outlast the conversations you skip—so have the hard ones first, when the dependencies are still small enough to untangle.