The Human Problem That Technology Cannot Solve Alone

I spent one day in a room with Lou Tice.

Lou was a former high school football coach who became one of the most quietly influential thinkers in the field of human performance. He did not talk about productivity systems or motivation hacks. He talked about something deeper and more uncomfortable: the way our subconscious belief systems quietly govern everything we do, and how the most durable change happens when the belief system moves in the same direction as the change, rather than against it. When belief and reality are aligned, change takes root. When they are not, something has to give.

One idea from that day has stayed with me for decades. I have watched it play out in boardrooms and on factory floors and in every technology implementation I have ever been part of. And I believe it explains something that the technology industry consistently gets wrong.

Let Me Tell You About Bessie

You have a car you have driven for years. You love this car. No payments. Low insurance. Cheap registration. You have even given it a name, Bessie. Bessie is part of your life.

One day a commercial catches your eye. A new model. Sleek. You do not think much of it. But then you see one on the road. Then another. Months pass. You tell yourself you are just curious, you are not in the market for a car, you just want to drive one. So you do. Thirty minutes in a dealership lot.

You get back into Bessie.

And for the first time, you see every crack in the upholstery. You hear the rattles you stopped noticing years ago. You see how the door handles have yellowed. The seat that always felt comfortable now feels wrong. Bessie has not changed at all in thirty minutes. Not a single molecule of Bessie is different.

But you are deeply uncomfortable.

What changed was not the car. What changed was your subconscious belief about what a car should feel and look and sound like. That belief shifted during the test drive. And now your reality, Bessie, is in conflict with your new belief. The gap between the two is what Lou Tice called cognitive dissonance, and it is not a minor psychological inconvenience. It is one of the most powerful forces in human behavior. It demands resolution.

One More Story

You are playing golf with a friend. You can feel you are playing well, better than usual. But you have not been keeping score. After nine holes you ask your friend to total up your card while you get some drinks. You come back and your friend says: you shot a 30.

Something happens in your head. I have never broken 90. That is your belief. A 30 on the front nine means a 60 or better on the back to break your record. Your body knows what to do to resolve this dissonance. You shoot a 60 on the back nine. Your total is 90. Reality has been brought back into alignment with your belief system.

The tragedy is that you were capable of a 30 all along. The belief system was the constraint, not the ability.

The Real Reason Change Programs Fail

I have spent thirty years in operational technology. The implementations that succeeded, the ones where the technology delivered what it promised and the value held over time, were the ones where behavior changed. Not where people were trained. Not where the system was installed and the project was closed. Where the way people thought about the work, and what they believed was possible, shifted first. The research reflects how rare that is: independent analysis suggests that more than 80 percent of technology implementations in manufacturing fail to deliver sustained value.

The standard explanations are training deficiencies, poor change management, inadequate executive sponsorship. These are real factors. But they are symptoms of something more fundamental.

The deeper failure is a sequencing problem.

When an organisation makes a major technology change, the usual approach is to implement the technology and then ask people to adapt. Install the system. Train the users. Measure the outcomes. The assumption is that if the technology works and the training is adequate, behavior will follow.

It will not. Not reliably. Not sustainably.

What actually happens is this: the implementation changes the reality before it changes the belief. The gap between the new reality and the existing belief is cognitive dissonance. And people, rationally, instinctively, unconsciously, work to resolve that dissonance by bringing the reality back in line with their beliefs. They find workarounds. They revert to old processes. They undermine the new system not because they are obstructive but because they are human. Resolving dissonance is what brains do.

The Bessie problem, played out at scale, across an entire organisation, with millions of pounds of technology investment on the line.

What Successive Approximation Actually Does

There is a different approach. It does not start with the technology. It starts with the belief.

The principle is called successive approximation toward a goal, a concept borrowed from behavioral psychology and applied, deliberately, to the design of how operational technology should be deployed. The idea is straightforward: instead of implementing the full system and asking people to catch up, you deploy in small stages, each one calibrated to deliver an immediate, visible, undeniable success.

The first deployment is not ambitious. It does not try to change everything. It changes one small thing, on one line, in one area. It produces a result that everyone involved can see and feel. The operator notices something different. The supervisor can point to a number that moved.

That small success does something more important than its direct value. It moves the belief system. Just a little. Just enough to make the next step feel possible rather than threatening.

And here is the critical insight: once that belief has moved, the cognitive dissonance flips direction. It no longer pulls people back toward the old reality. It pulls them toward the new one. The technology, which was previously the source of anxiety and resistance, becomes the thing people are drawn toward, because it is now consistent with what they believe is possible.

Each successive deployment builds on the last. Each small success extends the boundary of what feels achievable. By the time the implementation reaches the scale that was originally envisioned, it does not feel like a disruption. It feels like the natural continuation of a journey that the team has already been on.

The goal of the technology, improved quality, reduced scrap, faster training, better process knowledge, is achieved. But it is achieved because the human system was changed first, not because the technical system was imposed on the human system.

This Changes What Technology Has to Do

The implication for technology design is significant and largely overlooked.

If the implementation sequence is the critical variable, if behavior precedes outcome and belief precedes behavior, then the technology has to be designed to support this sequence. Not just architecturally, but philosophically.

Most enterprise technology is designed to be deployed at scale. The business case is built around full deployment. The ROI model assumes full coverage. The technology is tested and validated at the scale it was built for. This is entirely rational from a commercial perspective.

But it is behaviorally backwards.

A platform that cannot start small cannot respect the human sequence. A platform that requires months of implementation before delivering any visible value cannot build the early belief-system wins that change is built on. A platform that asks for the full leap rather than the first step will always encounter the resistance that comes from asking people to live inside a cognitive dissonance they did not choose.

What Leadership Has to Understand

Technology that is designed for successive approximation will not succeed without leadership that understands why the sequence matters.

The temptation for senior leaders is always to accelerate. Once the case is made, once the budget is approved, the instinct is to deploy as widely and as quickly as possible. To capture the full value. To prove the ROI that justified the investment.

This instinct, however understandable, can undermine the very value it is trying to capture.

The teams on the floor, the operators, the supervisors, the engineers who know the process, are not obstacles to change. They are the people whose belief systems determine whether the change sticks. If those belief systems are not brought along, if the cognitive dissonance is created without the successive wins that resolve it constructively, the investment will produce the numbers it was supposed to produce in the project plan and then quietly revert once attention moves elsewhere.

The leaders who succeed with these programs are the ones who understand that their job is not to overcome resistance. Their job is to make resistance unnecessary. That means giving people the small successes that shift the belief before the big change asks them to live in a new reality.

It means starting with one line, one process, one team. Measuring clearly. Sharing the results visibly. Letting the people who were closest to that first success become the people who explain it to the next team. That conversation, operator to operator, supervisor to supervisor, is more powerful than any executive mandate. It changes beliefs.

The Technology Is Only Half the Story

The industries where I have spent my career, manufacturing, aerospace, logistics, healthcare, are full of intelligent people who have invested seriously in technology and been disappointed by the results. The technology worked. The people did not adapt. The implementation failed.

Lou Tice would have understood exactly why.

The belief system is not a soft consideration to be managed alongside the hard work of technology implementation. It is the ground on which every implementation stands or falls. Change the belief first. Let the technology confirm and extend what people already believe is possible. And design the technology so that the sequence of small wins is not an afterthought but an architectural commitment.

When you do that, the cognitive dissonance stops being the enemy of change. It becomes the engine of it.

That is what successive approximation is. Not a deployment strategy. A behavioral design principle for how human beings actually change.