The genie is out of the bottle. What to do after you flatten.
The genie is out of the bottle. You can't put it back, nor should you.
This is part three of a series I've been writing on flattening. If you're just joining, the short version: flattening isn't the problem, doing it without a plan is.
You already flattened. Reversing it isn't realistic, and honestly, admitting the org chart was wrong isn't the point anymore. It wasn't a bad or wrong idea, just not planned properly. The point is what you do from here.
Does this sound like your company after a major flattening? Decisions stalling, quiet overload on your best people, cracks nobody's catching... If so, here's where to actually start:
- Name the gap out loud before you try to fix it. If quality control, coordination, assignments, or decision rights disappeared with the layer you removed, say so directly instead of letting people quietly absorb it and burn out guessing
- Push decision rights down, not just the work. If your teams are smaller and tighter now, the people on them need to actually be senior enough, and trusted enough, to make the call themselves and know when to escalate. Flattening without that shift just moves the bottleneck up to you
- Reassign ownership deliberately, not by default. Whoever picked up the slack informally is probably overloaded and under-recognized. Make it official, adjust their role, title, or comp to match what they're actually doing, or redistribute it
- Rebuild the T-shape you skipped. If your team is still mostly "I" shaped, invest now in cross-training and broader ownership, even though it's slower and less satisfying than it would have been to do before you flattened
- Reintroduce a checkpoint, not a layer. You don't need to rehire management to get review and quality control back. You need a defined moment, weekly, biweekly, wherever work is riskiest, where someone is explicitly responsible for catching what's slipping
- Watch your strongest people first. If attrition risk shows up anywhere, it's with the people absorbing the most. Address their load before it becomes a resignation
- If AI was part of the original plan, revisit it honestly. Is it actually doing what was promised, is it taking longer to implement (likely), or did the plan stall after the announcement
None of this undoes the flattening. But it's the difference between an org that stays flat and functional, and one that stays flat and slowly falls apart.
Flattening isn't inherently bad. Flattening without a plan is.