Your Sense of Urgency Does Not Alter My Speed
One of the great misconceptions of digital transformation is that speed is primarily a technology problem.
It is not.
We talk about transformation as if the moment the tools are available, the organization should naturally move faster. The cloud platform is ready. The AI model is trained. The automation workflow is configured. The dashboard is live. The executive team has approved the investment. The steering committee has met six times, which in corporate terms means it has achieved ceremonial legitimacy.
And yet, the organization still moves slowly.
This is where leaders often get frustrated. They look at the pace of technology and then look at the pace of people and assume something is wrong with the people. They are resistant. They are old-school. They are not innovative enough. They do not “get it.” I think that diagnosis is usually too convenient. People do not change at the speed of software. They change at the speed of trust, clarity, habit, incentives, identity, and perceived risk. Sometimes that speed is impressive. Sometimes it is glacial. And sometimes, frankly, it looks like a sloth in a sport coat carefully reviewing a 47-slide change management deck before deciding whether to move one branch to the left.
But slow does not always mean stubborn. Slow often means unconvinced.
Technology Can Be Installed. New Ways of Working Must Be Earned.
Most organizations are much better at deploying technology than they are at changing behavior. That is not because technology is easy. It is not. Systems integration is hard. Data architecture is hard. Cybersecurity is hard. AI governance is hard. Anyone who has tried to connect old industrial systems to modern digital platforms knows that the word “legacy” is often a polite way of saying, “No one fully understands this anymore, but please do not turn it off.”
Still, even difficult technology work has a certain mechanical logic. There are requirements, architectures, vendors, timelines, releases, and acceptance criteria. Eventually, something goes live. Human change is different. A new system may be available on Monday morning, but that does not mean people believe in it by Monday afternoon. It does not mean the frontline worker trusts the data. It does not mean the supervisor knows how to make decisions differently. It does not mean the plant manager is willing to abandon the spreadsheet that has quietly run the operation for eight years. It does not mean finance, operations, IT, engineering, and commercial teams suddenly agree on what “better” looks like.
That is why so many transformation programs create the appearance of progress before they create the reality of progress. The technology moves forward. The behaviors do not. The organization gets new tools, but old habits. New dashboards, but old meetings. New data, but old arguments. New workflows, but the same informal workarounds hiding underneath.
This is the uncomfortable truth: transformation does not happen when technology becomes available. Transformation happens when people are willing, able, and expected to work differently because of it.
The Hidden Clock Inside Every Transformation
Every transformation has two clocks. The first clock is the technology clock. This is the one executives like because it can be measured in milestones: system selected, pilot launched, data connected, AI use case deployed, training completed, go-live achieved. The second clock is the human clock. This one is harder to see and much harder to manage. It measures when people actually understand the change, trust the change, internalize the change, and adjust their daily decisions because of it.
The mistake many companies make is assuming the first clock controls the second. It does not. You can create urgency in the boardroom, but that does not automatically create readiness in the organization. You can announce a transformation, but that does not mean people know what to stop doing. You can invest in AI, but that does not mean employees understand how their judgment, expertise, and accountability now change.
In my experience, people are slow to move for several very rational reasons:
They do not understand why the change matters beyond executive language.
They do not trust that the new system reflects operational reality.
They have seen previous initiatives launch with energy and quietly disappear.
They are being asked to change behavior without changes to incentives, metrics, or decision rights.
They fear that adopting the new way will expose gaps, reduce control, or make their expertise less valuable.
That is not irrational resistance. That is organizational memory. People remember failed rollouts. They remember tools that made work harder. They remember being told a system would save time and then spending their evenings feeding it data. They remember when “transformation” meant more meetings, more reporting, and more acronyms with very little actual improvement. So when people cling to the old branch, maybe the issue is not that they hate innovation. Maybe the issue is that the new branch has not yet proven it can hold their weight.
Leadership Is Not About Moving Faster. It Is About Making Movement Make Sense.
The leadership challenge, then, is not simply to demand more urgency. Urgency is easy to declare and difficult to sustain. Any executive can say, “We need to move faster.” That sentence has been said in enough conference rooms to power a small nation. The better question is: have we made movement make sense?
That requires a different kind of leadership discipline. Not louder communication, but clearer communication. Not more transformation theater, but better operating logic. Not a bigger technology roadmap, but a sharper explanation of how work, decisions, accountability, and value creation are supposed to change.
Before leaders complain that people are moving too slowly, they should ask themselves:
Have we explained the why in language people actually recognize from their daily work?
Have we made it safe for people to admit what they do not understand?
Have we changed the incentives that keep old behavior alive?
Have we removed the workarounds, duplicate processes, and shadow systems that compete with the new model?
Have we shown people what better looks like, not as a slogan, but as a practical change in how decisions get made?
Because most people do not resist change in the abstract. They resist confusion. They resist risk. They resist being asked to trust a system that has not earned trust. They resist being told to move faster by leaders who have not removed the friction slowing them down. Digital transformation is not a race against technology. It is a negotiation with people.
And that negotiation requires empathy, discipline, and honesty. It requires understanding that people move when the new path is clearer than the old one, when the cost of staying still becomes visible, and when the organization proves that this is not just another initiative passing through with a new logo and a slightly different acronym. Technology is almost always ready before the organization is. The work of leadership is to close that gap.
So yes, move with urgency. But do not confuse urgency with impatience. Impatience blames people for moving slowly. Urgency removes the reasons they cannot move faster. That distinction matters.
Because your sense of urgency does not alter their speed.
But your clarity, credibility, and leadership just might.
