A leadership team commits to a transformation. They communicate the vision. They train the people. They buy the platform, run the pilots, celebrate the early wins. Eighteen months later, the organization is doing almost exactly what it did before.
If you have spent any time inside organizations, you have seen this movie. You may have been in it. The failure rate for digital transformation sits somewhere around seventy percent, and the reason cited most often is not technology. It is culture. Which is a strange thing to accept, because culture is precisely the thing every one of those transformations was trying, and failing, to change.
So let me offer a different explanation. The reason these efforts fail is not that people resist change. It is that they aim at the wrong target.
Behavior is not the thing you can change
Almost every change program is, at its core, an attempt to get people to behave differently. Adopt the new tool. Follow the new process. Collaborate more, hoard less, decide faster. The whole apparatus of change management exists to move behavior from where it is to where leadership wants it to be.
Here is the problem. Behavior is not an input you can set. It is an output. It is produced, reliably and continuously, by the conditions people operate within. Who has the authority to decide. What information is visible and what stays hidden. What gets rewarded and what gets quietly punished. The written rules, and the far more powerful unwritten ones.
Those conditions are always running. They were running before your transformation started, and they will still be running the morning after the last training session ends. If you change the behavior without changing the conditions, the conditions win. They always win, because they never stopped applying pressure while you were busy trying to persuade people to ignore them.
You cannot change behavior directly. You can only change the conditions that produce it.
This is why the most common transformation tactics disappoint so consistently. Communication tells people what to do, but does not change what the system rewards. Training builds capability, but deposits it into an environment engineered to produce the old behavior. Both are aimed at the person. Neither touches the machinery around the person. And the machinery is what is actually in charge.
Every behavior you can see is being produced by something
Try this reframe the next time a behavior in your organization frustrates you. Instead of asking "why do people keep doing this," ask "what conditions are producing this." The question moves the problem from the realm of persuasion into the realm of design, and design is something a leadership team can actually do.
Take a team that will not share information across silos. The conventional response is to exhort them to collaborate, maybe with a workshop on teamwork. The conditions response asks different questions. What are these people rewarded for? Almost always, it turns out they are measured and promoted on the performance of their own unit, with nothing riding on what happens next door. The behavior is not a character flaw. It is a rational response to the recognition system. Change what gets rewarded, and the hoarding dissolves, no teamwork workshop required.
Or take an organization where no one will make a decision without escalating it upward. You can tell people to be more empowered until you are exhausted. Or you can look at the actual decision rights and discover that the last three people who made a call without checking got publicly second-guessed for it. The behavior is the system working as built. The fix is in the conditions, not the pep talk.
This is the pattern, over and over. What looks like a people problem is nearly always a conditions problem wearing a people problem's clothes.
Seeing the system, then redesigning it
If behavior is produced by conditions, then serious change happens in two moves. First, you have to see the system clearly enough to understand which conditions are producing the behavior you want to change. Then you have to redesign those conditions on purpose.
The first move is harder than it sounds, because most organizations have never actually seen their own operating system. They see its outputs, the results and the recurring frustrations, but not the machinery underneath. When a pattern keeps recurring despite everyone's best efforts to change it, that is not stubbornness. It is a system doing exactly what it was built to do, and the first job is to make that machinery visible.
The second move, the redesign, turns out to concentrate in a small number of places. In practice, most of the leverage sits in four conditions: who holds which decision rights, how information flows and to whom, what actually gets recognized and rewarded, and how governance defines what is permitted. These four are powerful precisely because they are impersonal. You are not asking anyone to be a different person. You are changing the environment they operate in, and letting the new environment produce the new behavior.
There is more to a full transformation than seeing and redesigning the system, of course. The change still has to reach individual people, move through the technology, spread across the group, and be watched by a learning loop that tells you whether any of it is working. But all of that sits on top of the foundational move, and the foundational move is the one almost everyone skips: change the conditions, not the behavior.
The next time you are tempted to launch a transformation by telling people how they need to change, pause on one question. What in your organization's conditions is currently producing the behavior you are unhappy with? If you cannot answer it, you are not ready to change the behavior yet, because you have not yet found what is producing it. And if you can answer it, you will usually find that the answer, not the people, is where the work actually is.
The system was always producing your results. The good news in that sentence is easy to miss. If the system is producing the results, then the system can be redesigned to produce different ones. That is a far more hopeful place to stand than the exhausting business of trying to change people one by one.
The Behavior-Conditions Model
I've laid out the full architecture in a white paper: the Cultural Operating System for seeing the system, the four conditions that carry the leverage, the five layers of change, and the seven phases that turn it into a running program. Free to download, no email required.