A large organization was under significant expense pressure. After studying the problem, its leaders decided to move several functions from fully autonomous business-unit structures into a shared-services model.
Technology was one of the first functions selected.
The business case was compelling. A shared model could reduce expense, improve consistency, present one face to clients, and strengthen service delivery across the enterprise. Similar efforts had been attempted before, with mixed results, so the leadership team knew the transition would require discipline and sustained commitment.
Every business head agreed to the plan.
At least formally.
One executive volunteered for his business to move to the end of the transition schedule. His stated reasons sounded practical. His clients were unique. His business was complex. Timing mattered. Other units could go first, allowing his team to benefit from the lessons learned.
But beneath the logic was another hope: that the initiative might lose momentum or fail before it ever reached his organization.
That distinction mattered.
The executive did not openly oppose the decision. He agreed in the room. But his behavior afterward communicated reluctance, doubt, and distance. His staff noticed. They adopted the same posture. Instead of preparing to make the transition successful, they waited, questioned, and protected the existing model.
The organization ultimately achieved its objectives. Costs came down. Client delivery improved. The shared-services model worked.
But the reluctant executive’s business had one of the most difficult transitions.
That was not because it went first or lacked the benefit of experience. It went last. It had every opportunity to learn from the units that preceded it.
Its difficulty came from something else.
Pressure had revealed a leadership pattern that was probably already present: when faced with an enterprise decision that threatened local control, the executive protected his own organization first. He complied formally but withheld full commitment. Under ordinary conditions, that pattern may have been less visible. Under pressure, it became unmistakable—and his organization absorbed it.
Leaders transmit their relationship to change before they transmit the change plan.
Like the other business units, this executive assigned several people to the organization-wide transition team. They attended the meetings and participated in the work, but their posture was different.
They entered the process primarily looking for reasons the model would not work.
Their clients were unique. Their requirements were more complex. A centralized model, they argued, would be too standardized to meet their needs. Some of those concerns may have been legitimate. But instead of using those differences to improve the shared-services design, they used them to defend the existing structure.
The distinction is important.
Constructive challenge asks, “What must be true for this to work for our clients?”
Resistance asks, “How do we prove that this cannot work for us?”
The executive’s reluctance had become embedded in the team’s approach. They did not need to be told to resist. His hesitation gave them permission to protect the status quo, continue questioning the decision, and search for alternatives that would preserve local control.
As pressure increased, most business units moved forward, learned, adjusted, and helped improve the model.
The reluctant business tried to establish a separate unit instead.
Its leaders continued to argue that their needs were exceptional and that full participation in the shared model would put client delivery at risk. Eventually, they did transition—but only after creating additional work, delay, and strain for themselves and the wider organization.
The prevailing view afterward was straightforward: they had made the transition harder than it needed to be.
The experience reinforced something I had learned earlier in my career from a senior executive who often said, “We go slow so we can go fast.”
She did not mean that organizations should delay difficult decisions or wait for universal enthusiasm. She meant that leaders should take the time to surface concerns, test assumptions, clarify the decision, and establish real commitment before execution begins.
That is different from seeking consensus.
Leaders do not have to agree with every aspect of a decision. They do have to understand it, challenge it honestly, and then decide whether they are prepared to lead it.
Once a decision has been made, leaders remain responsible for surfacing material risks. But repeatedly relitigating the decision, withholding commitment, or allowing their teams to resist indirectly is not constructive dissent. It is a failure to lead.
Pressure makes that distinction more visible.
Under ordinary conditions, a leader can sometimes conceal reluctance behind polite language, procedural questions, or requests for more analysis. Under sustained pressure, those patterns intensify.
Thoroughness can become delay and analysis paralysis.
Confidence can become certainty and dismissal.
Caution can become avoidance.
Control can become micromanagement.
Loyalty to the function can become protection of territory at the enterprise’s expense.
Pressure does not usually introduce a new pattern. It gives an existing one more force and consequence.
That is why leaders need to understand how they respond when control is threatened, resources tighten, expectations increase, or the path forward becomes uncertain.
Their teams are watching.
They notice what the leader questions repeatedly, what the leader defends, where the leader withdraws, and whether the leader treats the change as something to shape or something to survive.
The formal message may be, “We are committed.”
The behavioral message may be something else entirely.
And in most organizations, the behavioral message wins.
When leaders are inside the planning and implementation process, these patterns can be difficult to recognize. They are close to the decisions, deadlines, and daily pressure. Sometimes it takes a wider system view to see how leadership behavior, team posture, governance, and execution are interacting—or failing to interact.
Commitment cannot be secured once and assumed to hold. It has to be tested and reinforced throughout the work.
Pressure usually increases as execution progresses. Timelines tighten. Resources become constrained. Early optimism gives way to operating reality.
Strong governance matters because it keeps decisions, ownership, risks, and commitments visible when pressure rises. But governance cannot carry what leaders will not reinforce. If leaders say yes in the room and communicate no through their behavior, the system will eventually believe the behavior.
Pressure does not create the pattern. It reveals it and amplifies it.
An executive taught me many years ago: listen to what leaders say, but watch what they do.
Under pressure, the organization will do the same.
