The Performance of Success
Mark beamed at the projected line chart-all steep, triumphant green-showing 91% user adoption of the new Unified Enterprise Data Engine (UEDE). They paid a boutique firm $1,300,001 just to design the UI. And yet, if you opened the task manager, you would find an instance of Excel humming softly in the background, minimizing what they still needed to do the actual job.
💡
The failure of transformation is almost never a failure of code. The software *works*. The failure is that the system requires people to work differently, disrupting an existing, deeply comfortable power structure.
The Citadel of Idiosyncrasy
Consider the procurement team, gatekeepers for 21 years, whose power resided in the arcane, personalized spreadsheet they created in 2001. The new enterprise system standardizes input, making data transparent to the junior analyst. Suddenly, the gatekeeper has lost their gate.
It’s a deliberate sabotage-not out of laziness, but out of self-preservation. When the new system throws up an error (and every new system throws errors, especially during the first 41 weeks of deployment), who gets called? The person who maintained the ‘real’ data in the parallel file.
The gatekeeper successfully negotiates the terms of ‘modernization’ back into the terms of ‘personal indispensability.’ This is where authority is















