The Silent War of Screens

Sarah is currently at war, though she won’t call it that. She calls it ‘getting around to it.’ But right now, the war is silent, fought across three monitors. One screen holds the gleaming, $1,444,000 CRM system-the official operating truth of the company. The other two screens hold the truth she actually uses: her specific, private, color-coded spreadsheet and a Slack window where she asks a peer, “Did you actually log that?”

Her action in progress is the same action she has performed 44 times this week: documenting a customer interaction. In the new system, this requires navigating three primary tabs, four sub-menus, and filling out exactly 17 mandatory fields. These 17 fields are not required for her job; they are required for her manager’s report, which will be presented to executives who demanded transparency without bothering to understand flow. Every field represents a layer of organizational anxiety.

The Lie of Resistance

I hear that claim constantly:

“The adoption rate is low because the employees are resistant.” This is a lie we tell ourselves to justify catastrophic management failure.

I’ve been involved in the implementation of systems that cost hundreds of thousands of dollars… And almost universally, the implementation team focuses all its energy on training, documentation, and compliance policing-all focused on changing Sarah’s behavior. But Sarah’s behavior is rational. She is optimizing her day against the structural obstacles we created.

We purchased accountability, and in the process, we murdered efficiency.

Structural Cruelty and Optimization

I remember talking to Hiroshi M.K., a specialist who focuses on dyslexia intervention in higher education… He calls it structural cruelty-the system is designed to break the user, not support them. We do the same thing in the enterprise. When we insist on 17 mandatory fields, we are imposing organizational dyslexia on our front lines.

This shadow system… is the proof that the official process is broken. And we pay consultants $474 per hour to ignore that reality and try to police the symptoms.

The Real Cost of Friction

I made this mistake myself early in my career… They reduced the delay by 74%. My mandate didn’t stop the shadow system; it just forced it into the shadows, making the data entry mistake-prone.

This misalignment is lethal when integrity is your most vital asset. If the regulatory burden demands specific data points, the workflow must be structured such that capturing those points is the path of least resistance.

The Symptom of Power Dynamics

Executive Priorities vs. User Reality

It is the clearest symptom of organizational power dynamics: the people who control the budget prioritize their anxiety (control) over the efficiency of the people who execute the mission (Sarah).

The Path Forward: Generative Friction

The only way forward is to redesign the system based on the principle of generative friction-friction that creates value, not reporting requirements. What does Sarah need to know, or do, right now, that makes the interaction successful? Whatever that is, that’s the button you build, and the reporting follows.

So if your software implementation is struggling, don’t ask why your employees are resistant. Ask: Whose job did this million-dollar purchase actually make easier?