I’ve watched CIOs build their careers on saying yes. A team needs better code completion, they approve the tool. Another team needs automated testing, they approve that too. A third team needs deployment automation, they find budget for it. Each decision makes them look responsive, business-aligned, and supportive. They’re the CIO who enables teams rather than constraining them. That’s how they’ve built relationships across the organization. That’s how they’ve maintained credibility with product leaders who want to move fast.
Here’s what leaders aren’t saying out loud: every yes creates fragmentation, and they know it. Every approved tool request adds to integration overhead, increases total cost of ownership, and makes infrastructure harder to manage. But saying no—consolidating to a unified platform, forcing teams to use shared infrastructure—makes them look like the gatekeeper. The person who slows teams down. The IT leader who prioritizes control over enablement.
That’s the real barrier to platform investment I keep encountering. It’s not financial. The math clearly favors platforms when you have more than a handful of teams. Point solutions create hidden costs that dwarf the price of shared infrastructure. But the math doesn’t matter if the political cost is too high. The CIO who says yes to tool requests is popular. The CIO who consolidates to a platform is seen as constraining. And they’ve been rewarded for being popular.
The shift to platform thinking requires becoming a different kind of leader. Instead of enabling every request, they’re defending an architecture. Instead of saying yes to make teams happy, they’re saying no to create leverage. Instead of being valued for responsiveness, they’re valued for discipline. That’s not just a strategic shift—it’s an identity shift. The competencies that made them successful (relationship management, business alignment, responsiveness to requests) become less relevant than competencies they may not have built (architectural vision, long-term thinking, willingness to absorb short-term criticism).
What I’m seeing is that most CIOs aren’t ready for that trade-off. Distributed tool spending looks like business enablement. Consolidated platforms look like IT control. So the fragmentation continues, and leaders stay valuable by managing the complexity they could eliminate.
The pattern I observe: organizations with distributed tool spending across teams, where the total cost of ownership for fragmented tooling has never been calculated against what a unified platform would cost. When that’s the case, leaders are probably optimizing for saying yes rather than building leverage. And the first step to changing that is admitting what’s actually being optimized for: driving business value, creating culture and community around developer experiences and communities, and managing cost.
Leave a Reply