970x125
I’ve watched this pattern repeat across organizations: a new technology, program, or policy launches with great enthusiasm. Budgets are approved. Dashboards go live. Reality sets in and momentum dies.
When that happens, it’s tempting to blame “resistance.” But more often, the problem is simpler and more human: leaders are making decisions based on a version of reality that isn’t the one people are living.
That gap is what I call the reality delta: the difference between what leaders assume is happening and what people experience as they try to get the work done.
Reality Deltas at Work
Reality deltas don’t show up in strategy decks or steering committees. Instead, they surface as unseen behaviors and unheard concerns, like:
- An extra step someone adds because the “new process” breaks in real life.
- A shadow spreadsheet running alongside the “single source of truth.”
- A veteran’s shrug: “We’ve always done it this way” (because the workaround is safer).
- Quiet anxiety about AI: “If I use this to automate, will I be judged, replaced, or blamed if it’s wrong?”
Why It Matters for Managers
Reality deltas are early warning lights. When the gap persists, it creates predictable costs:
- The wrong people get rewarded. Conscientious employees get overloaded.
- Shadow systems multiply (spreadsheets, local databases, unofficial automations).
- Work slows down (double entry, extra checks, exception handling).
- Risk rises (compliance gaps, audit surprises, ungoverned AI use).
- Change fatigue builds (“this too shall pass,” so people disengage faster next time).
In short: reality deltas are how well-intended transformation turns into operational friction.
How It Begins: Naïve Realism and Organizational Silence
A key reason the reality delta exists, and why it often catches leaders by surprise, is a cognitive bias psychologists call naive realism.
Naive realism is one of the most robust findings in psychology. It is the tendency to experience our own perceptions as objective and complete, and to treat disagreement as evidence that others are uninformed or biased (Ross & Ward, 1996). In organizations, those biases collide with two structural forces:
- Hierarchies create silence. Employees often self-censor, especially when they believe speaking up will be punished, ignored, or labeled as negativity (Morrison & Milliken, 2000; Detert & Edmondson, 2011).
- Change is fundamentally a sense-making process, not merely an implementation challenge. People interpret new tools and initiatives through the lenses of what helps them get work done, what is reinforced or rewarded by the organization, and what feels personally or professionally risky (Weick, 1995; Maitlis & Christianson, 2014).
Leaders assume their plans, communications, and strategies are clear and sufficient. Employees assume that leaders understand the constraints, pressures, and workarounds inherent in daily tasks. When differences emerge, each side tends to dismiss the other’s perspective instead of exploring it.
Listening for Deltas
Listening for deltas is the discipline of tuning in to the difference (Δ) between your assumptions and the reality people are navigating every day. It requires paying attention to:
- What people do rather than what they say they do.
- What they adjust rather than what they endorse.
- Where informal practices diverge from formal plans.
The reality delta shows up in three places: priorities (what people are really optimizing for), operations (how work actually flows), and emotions (the risks and fears people won’t say out loud).
1. The Priorities Delta
The first gap emerges from a lack of clarity or conflicting directions. When priorities are unclear, technology becomes a shiny object rather than a strategic lever.
What you might hear:
- “We have 10 priorities.” This is a red flag. If everything is a priority, nothing truly is. Technology efforts become fragmented, diluted, and ultimately ineffective.
- “Why are we doing this again?” When employees question the purpose of a new tool, it signals a disconnect between the technology’s perceived value and the organization’s overarching goals.
2. The Operations Delta
Even with clear priorities, new technology often clashes with existing operational realities. Processes, systems, and skillsets are deeply entrenched. Simply dropping a new tool into an old workflow is like putting a jet engine on a horse-drawn carriage.
What you might hear:
- “I have to copy-paste data from the new AI into our old spreadsheet.” Manual workarounds are a clear sign the operational delta is wide.
- “The tool is great, but our process still requires three manual approvals.” Here, the technology’s potential is undermined by the current state of the workflow.
3. The Emotions Delta
This is the most critical and neglected delta. Ignoring the emotional landscape during transformation is a surefire way to encounter resistance, disengagement, and outright sabotage.
What you might hear:
- “Is this thing going to make my job harder or eventually replace me?” This fear, whether voiced or silently held, is a powerful inhibitor. Ignoring it doesn’t make it go away; it merely drives it underground.
- “I’m afraid to try the new feature because I might break something.” This reflects a lack of psychological safety. If experimentation and learning aren’t encouraged (and even rewarded), employees will cling to the familiar, less efficient old ways.
Closing the Reality Delta: Listen, Validate, and Build
Every change creates a reality delta: the gap between what leaders intend and what work actually feels like on the ground. In technology change, that gap shows up quickly: workarounds multiply, cycle times creep up, trust in data erodes, and teams quietly revert to “the old way” when pressure hits.
Closing the delta takes more than collecting feedback at launch. It requires a disciplined cycle that moves from discovery to action.
1. Listen to Ground Truths
Get out of your office and listen to how things really are. Don’t just ask, “How’s it going?” Ask for “show me” evidence:
- “Show me the last time this slowed you down.”
- “Where do you leave the system to get the job done?”
- “What do you do when the data looks wrong?”
- “Which steps disappear when you’re under pressure?”
Capture the delta in specifics: what takes longer, what breaks, what creates rework, and where people are forced to choose between speed, compliance, and customer experience.
2. Validate What You Hear
Validation doesn’t mean agreement. It means treating people’s experience as useful data about how an existing system.
The fastest way to widen the delta is to explain it away:
- “That shouldn’t happen.”
- “You’re using it wrong.”
- “People just don’t like change.”
Instead, reflect what you heard and name the impact:
- “Here’s what I saw.”
- “Here’s where it’s adding time.”
- “Here’s where trust breaks.”
When leaders validate reality, teams will continue to share the truth.
3. Build on What Works
Translate the most painful deltas into a prioritized backlog and deliver small wins quickly (Weick, 1984). Early fixes build credibility and unlock better information.
Over time, use the deltas to challenge the assumptions behind the workflows. That’s double-loop learning: not just correcting errors, but revisiting the thinking that created them (Argyris & Schön, 1978).
