It Was Never About the Tech

The pattern that repeats across every team

Implement the same system, the same governance model, the same tooling across eight different teams over fifteen years, and you'd expect eight similar outcomes. You get eight completely different ones — because the platform was never the variable doing the work. The teams that thrived had clarity on what they valued and permission to work across boundaries. The teams that stalled had neither, regardless of how good their tooling was on paper.

Shadow IT is usually a symptom, not the disease

IT calls them risk creators — the business analysts running elaborate spreadsheet macros because the official process takes six weeks for something they need in two days. Shut them down in the name of governance and a predictable thing happens: business value drops, sharply, because those "risky" analysts were quietly doing the most productive work in the building, working around a broken system rather than causing one. The fix was never prohibition. It was giving them real tools and light governance instead of handcuffs — because the people who route around your process are usually telling you exactly where the process is broken, if you're willing to listen instead of enforce.

A manifesto beats a hundred-page policy

The cultural fix that actually holds is not a new tool or a new org chart. It's a short, explicit statement of what the team values more than something else — modeled on the Agile Manifesto's format. "We value usage and re-use more than building another solution. We value working across teams more than individual optimization." The "more than" phrasing matters: you're not saying the thing on the right is worthless, you're saying the thing on the left wins when they conflict, and everyone now knows which way to lean when a decision is ambiguous.

Printed and referenced in actual meetings — "does this align with our manifesto" becoming a real question people ask out loud — a manifesto like this changes daily decisions in a way that a comprehensive governance document, sitting unread in a shared drive, never does.

Where this shows up in the book

This is the fourth and final leadership essay, drawn from watching the same systems implemented across eight teams over fifteen years produce entirely different outcomes every time — because the technology was never the thing that varied.