Splitting innovation from upkeep is clean on a whiteboard and quietly corrosive on a team.
A reorganization idea came across my desk this week that’s clean on a whiteboard and quietly dangerous on a team. The idea is to split a domain in two. One team keeps the core running, the part hundreds of thousands of people depend on every day. Another team gets chartered for the new, ambitious work, the bets, the things that show up in a vision deck. On paper it’s tidy: clear ownership and fewer collisions.
The trouble is that the moment you draw that line, you’ve drawn a second line you didn’t mean to draw. A status line. The people on the “keep it running” side don’t just hear a different scope. They hear where the exciting work went, and it went somewhere else. They hear that they’re the ones holding the thing together while other people get to invent. Say nothing to correct it and that reading hardens over months into “I’m on the maintenance team,” which in most people’s ears is one step from “I’m on the team that didn’t make the cut.”
An org chart is a status signal whether you intend it to be or not. Structure communicates worth, and names communicate worth, and “keep the lights on” is an accurate description and a demoralizing identity at the same time. Here’s the thing that makes this more than a feelings problem. The work of keeping a product reliable for the people who pay for it is not lesser work. If your structure implies that it is, your strongest maintainers either leave or quietly check out, and then you have neither the innovation you reorganized for nor the stable core you took for granted. You can lose both halves by mislabeling one of them.
A few things help, and none of them are the reorg itself. Rotate people through both sides so nobody’s identity calcifies into “maintenance person.” Tie the upkeep charter to something real, the reliability and trust that keep customers around, rather than framing it as the place you put people who aren’t on the new stuff. Be deliberate about the language in the all-hands and in the doc, because that’s where the status reading gets set. And watch the load, because the trap underneath the trap is that the same few people who know the domain best end up carrying both the upkeep and the new bets, and you burn out your most valuable people while telling them they’re just the safe pair of hands.
The teachable part
Every reorg is a values statement, and the people inside it read it more closely than you do. Before you split innovation from maintenance, ask what story the split tells about who matters, because the team will believe what the structure implies and not what you say from the stage. If “maintenance” is going to read as “demotion,” you have two choices: change the structure, or change the language and the rotation and the recognition until the structure says what you actually mean. Don’t let the org chart deliver a message you’d never say out loud.