The cursor hovers over the button: ‘Save and Commit.’
I hate this button. I hate what it represents. It’s not a commit to actual work; it’s a ceremonial sacrifice of 17 minutes of my life to a database designed by committee, for a purpose I suspect even the designers have forgotten. The irony is excruciating: I’ve spent the last 21 minutes trying to optimize the view of this very system-tweaking filters and conditional formatting-because the default interface is medically depressing. I know better than to polish a turd, but here I am, providing governance to the digital sewage system. This is my essential, announced contradiction: I criticize the system while simultaneously investing my expertise into making it marginally less painful for myself and the three other poor souls stuck on this client implementation.
The Illusion of Selection
We were given a ‘choice.’ That’s the lie we tell ourselves in enterprise procurement. Eurisko-our client-was facing pressure from 41 different internal departments to modernize their legacy CRM. So, the C-suite, bless their detached hearts, hired an army of consultants who synthesized a matrix, ran 31 workshops, and finally presented two options: Vendor A (the reliable dinosaur) or Vendor B (the sleek, over-promised jet plane). Both cost $5,000,001 to license upfront, and both required 1 year of mandatory, intrusive customization. The committee, led by people who haven’t logged a sales call since 2001, chose B. Why? Because the sales rep for B wore a better suit, promised ‘full integration capability,’ and, frankly, was willing to spend 1 evening golfing with the SVP of Operations.
A Market of Governance, Not Utility
Utility, workflow, human experience? Those factors barely registered as 1 point on the final weighted score sheet. That choice wasn’t about empowering the workforce. It was about risk mitigation and bullet points for the board. The enterprise software market isn’t a market of utility; it’s a market of governance. Buyers need to prove they bought the ‘safest’ option, the one that checks the most security boxes, the one where the vendor guarantees they will be alive in 11 years. They are buying insurance policies against their own incompetence, and the users are the deductible.
The Friction Cost: Screens to Log Follow-up
We deployed B. A year and several million dollars later, the promised integrated platform is a loose collection of modules that barely tolerate each other. The front-line staff-the people who actually input the data that drives the $171 million revenue stream-have to jump through 41 different screens just to log a simple follow-up.
The Cost of Agency Loss
They have developed what I call ‘Digital Calluses.’ This leads directly to the core problem: learned helplessness. When employees have zero agency over their primary tools, when every movement is a battle against the UI, they stop caring.
They retreat into shadow IT, setting up unofficial spreadsheets and clandestine Slack channels to manage the parts of their job the official system actively prevents them from doing. Why bother improving a process when you know the tool will sabotage you anyway? You learn to survive the system, not thrive within it.
Tactical Error: UAT Friction
51% More Clicks
I made a mistake in the implementation planning phase, a tactical error I should have foreseen. I trusted the vendor’s demonstration environment. I failed to push back hard enough when the initial user acceptance testing (UAT) group-a team of 11 individuals-reported that the core feature required 51% more clicks than the legacy system. I dismissed it as resistance to change. It wasn’t. It was accurate data I chose to ignore because the implementation deadline loomed.
We sacrifice efficiency on the altar of integration.
The Case for Purpose-Built Utility
If his inventory tracking system requires him to stop cleaning a highway abutment, climb into his van, and click through 17 menus to log that he used 1 liter of solution, the system is fundamentally broken.
Think about friction, real friction, the kind that hurts. I was talking recently to Sage K.L. Sage is a graffiti removal specialist for the city. His job is intensely specific: neutralizing chemical compounds, matching historical paint textures, and working against the clock before the stain sets permanently. He operates with 1 spray gun, 41 liters of specialized solvent, and a precise, highly optimized workflow.
Sage needs tools designed for his job, not a generic, off-the-shelf system configured by someone 2,001 miles away who thinks ‘field services’ means checking a box on a contract. His tools must be precise, purpose-built, and eliminate cognitive load. Generic ERPs are fundamentally antithetical to his existence.
Beyond the Duopoly
This is where we acknowledge the necessity of moving beyond the vendor duopoly. When the default options fail, you must seek partners who prioritize the user’s utility over the executive’s checklist. This requires a level of deep, collaborative development-the kind that shifts the focus from ‘integrating everything’ to ‘solving one essential problem perfectly.’
I’m thinking specifically about how the team at Eurisko eventually tackled the internal resentment caused by the CRM failure. They realized that throwing more money at the system itself wasn’t the answer. The fix wasn’t an upgrade; it was an amputation of the parts that caused pain, and the creation of highly specialized, user-centric tools that acted as a bridge, designed only to manage the 11 tasks that generated 81% of the workload.
The Price of Admission
That required humility from the leadership-a rare commodity. It meant admitting, a year and $5,000,001 too late, that the initial choice was flawed, not because the software wasn’t capable, but because the decision-making framework was broken. We weren’t choosing a hammer; we were choosing a procurement philosophy.
The Ongoing Expense of Inertia (Visualized with slight color shift)
1,111 Reluctant Daily Users
Now, the new system, this necessary evil, requires constant maintenance. I update software I never use, logging into servers only to keep the lights on for the 1,111 employees who reluctantly use it every day. I see the expense report that shows the $3,001 spent on advanced training that nobody attended because they’d already given up. The entire process smells faintly of solvent, not from the successful removal of a mistake, but from attempting to dissolve the sheer bulk of bureaucratic inertia.
I eventually clicked ‘Save and Commit.’ The system responded with a generic error message, Error Code 171, that required me to log out and back in 1 time. It was a final, petty act of digital sabotage. The system is perfect, I realize, because it is perfectly reflective of the disjointed, checklist-driven committee that selected it.
The Final Question
So, before we sign the next $1,000,001 contract for the ‘fully integrated digital ecosystem,’ we must ask one fundamental question, not of the vendor, but of ourselves:
Are we buying governance, or are we buying utility?