Running in All Directions (The Tool Circus Nobody Asked For)
The Problem
Letting everyone pick their own tools and approaches, creating 3, 5, or 10 different ways to do the same thing. Technology teams love new shiny tools. Getting technologists excited about the latest thing is easy. But with too many choices, everyone grabs something different and runs with it, convinced they're innovating. The result? Chaos. Fragmentation. Three teams implementing three different data catalog vendors. Some building custom, others buying commercial. Same vendor used five different ways. Everyone thinks they're maturing the organization. Nobody realizes they're killing it.
The Principle
SHARED DIRECTION OVER INDIVIDUAL FREEDOM: Progress requires everyone running down the SAME side of the road together. When everyone picks different paths, you see small pockets of value team by team, but as a whole it diminishes your organization's fitness. Create a clear mountaintop: Make it crystal clear where you're going as ONE team. Paint the picture. Show the destination. Then audit for duplication—find where you're doing the same thing multiple ways. Standardize strategically: Pick ONE way for ONE thing. Doesn't mean one tool for everything—it means one approach per problem. Stop new fragmentation—any new initiative must answer "how does this align with our shared direction?" Retire competing approaches gradually. Communicate the WHY before making people climb. If you asked "where is your organization doing the same thing 3 different ways?" and have multiple examples, you're fragmented, not fit. Fix that first.
3 Steps to Take Action
- 1
Draw the Mountaintop: One page. Where are we going as ONE team? What's the future state? Make it crystal clear. Get leadership buy-in.
- 2
Audit for Duplication: Find everywhere you're doing the same thing 3+ ways. Data catalogs? BI tools? Quality frameworks? List them all. Pick ONE per function.
- 3
Sunset Competing Approaches: Give teams 90 days to migrate to the chosen approach. Retire the rest. Stop new fragmentation - any new tool must align with mountaintop.
In Practice
A healthcare analytics org had five separate teams. Each team decided—independently—to "solve the data quality problem." Team A built a custom Python framework. Team B bought Collibra. Team C bought Informatica. Team D built their own too, but in Scala. Team E just hired more people to manually check data. Annual cost of this fragmentation: $2M. Five solutions. Zero coordination. Constant confusion about which system owned quality for which data. New VP walked in, drew the mountaintop on a whiteboard: "ONE shared data quality framework. Period." Teams resisted. "But our approach is better!" "But we already spent $400K!" "But our team knows this tool!" VP was ruthless: "I don't care. Pick one. Sunset the rest. You have 90 days." They picked Team B's approach (Collibra), killed the other four. Reallocated the $1.6M saved to capabilities that actually moved the needle. Migrated gradually over six months. Results? Work completed 3x faster because everyone pulled in the same direction. No more "which quality system do we use?" debates. Data quality actually improved because resources were focused, not fragmented. Fragmentation costs real money and real momentum. One direction. Always.
