The Difference Between Leading Change and Forcing the Finish
There are moments in leadership when "just do it" is exactly the right advice.
Stop overthinking. Make the call. Take the first step. Move the work forward.
There are also moments when "just do it" becomes something entirely different.
It becomes an order.
Push the initiative through. Get people on board. Make the change happen. Do not spend too much time worrying about resistance. Do not slow down for questions. Do not wait for collective understanding. Just get it done.
That version of "just do it" can leave a crater.
I learned that distinction working for an administrator who was comfortable with fallout.
He made decisions quickly and expected the people beneath him to move those decisions through the organization just as quickly. He did not place much value on creating collective understanding or building the collaborative conditions necessary for meaningful change. His priority was implementation.
If people were angry, they were angry.
If families pushed back, deal with it.
If staff felt blindsided, keep moving.
If trust was damaged, the initiative was still technically implemented.
He wanted people around him who could take an idea and shove it across the finish line.
The problem was that the person doing the shoving was often left standing there when everyone started asking why they had been pushed.
That is not the same thing as leadership.
Being Given the Reins Is Not the Same as Being Given the Lead
There is an important distinction between being empowered to lead organizational change and being assigned responsibility for carrying out someone else's decision.
A leader who is truly given the lead has room to assess the landscape.
They can listen.
They can ask questions.
They can involve people who will be affected.
They can identify unintended consequences.
They can modify the implementation plan when new information emerges.
They can determine whether the organization is actually ready.
A person who is simply given the reins may have none of that authority.
They are told where the organization is going and then handed responsibility for getting everyone there.
That person often becomes the visible face of a decision they did not fully make.
From the outside, leadership looks like authority, while from the inside, it functions like compliance.
That distinction matters.
You cannot hold someone accountable for leading change while denying them the authority to shape how the change happens.
Implementation Is Not the Same as Leadership
Organizations sometimes confuse movement with progress.
A new initiative launches.
A schedule changes.
A program begins.
A mandate is communicated.
A policy goes into effect.
The boxes get checked.
From an implementation standpoint, the work appears complete.
Leadership asks a different set of questions.
Do people understand why we are doing this?
Did we include the people closest to the work in shaping it?
What concerns surfaced before implementation?
What concerns are emerging now?
What are we learning?
What needs to change?
What relationships are being strengthened or strained?
Those questions slow implementation down.
That is exactly why they are often skipped.
Speed can create the illusion of decisive leadership.
Trust takes longer.
Fallout Is Data
One of the most dangerous habits in organizational change is treating resistance as an inconvenience rather than information.
People pushing back are not always afraid of change.
They may be responding to poor communication.
They may see consequences leadership has missed.
They may understand operational realities better than the people designing the initiative.
They may simply be asking for enough information to make sense of what is happening around them.
Resistance can be frustrating.
It can also be incredibly useful.
Strong leaders do not automatically retreat every time someone objects. They also don't automatically accelerate just because someone objects.
They listen long enough to understand what the resistance is telling them.
Fallout is data.
Ignoring it does not make the information disappear.
There Is a Difference Between Urgency and Recklessness
Organizations occasionally need to move quickly.
Emergencies happen.
Deadlines exist.
Opportunities close.
Leadership cannot always wait for perfect consensus.
Urgency still requires judgment.
Recklessness says:
We decided. Make it happen.
Leadership says:
We need to move quickly. What do people need to understand? What barriers should we anticipate? Who needs to be part of this conversation? What damage can we prevent while still moving forward?
The pace may be similar.
The process is not.
When Responsibility Travels Down and Accountability Travels Nowhere
The most destructive version of "just do it" happens when authority and accountability separate.
Someone at the top makes the decision.
Someone in the middle is told to implement it.
The community reacts.
The person in the middle becomes the target of the reaction.
The original decision-maker quietly steps back.
That creates an unhealthy relationship with leadership itself.
You begin carrying decisions you did not own.
You absorb anger you did not create.
You defend choices you were never permitted to question.
You become responsible for protecting the organization from the consequences of decisions made above you while receiving little protection in return.
I once had an administrator tell me that I needed to learn to look out for myself because he was the only person who looked out for him.
I remember the sentence because it clarified more than he probably intended.
It explained the culture.
When self-protection becomes the leadership model, everyone downstream eventually learns the same lesson.
Cover yourself.
Document everything.
Do not take risks.
Do not challenge decisions.
Do not trust that anyone will stand beside you when things go wrong.
That is not a culture of innovation.
It is a culture of survival.
Innovation Requires More Than Permission to Act
Innovation is often described as boldness.
Move quickly.
Try something new.
Challenge the status quo.
Take risks.
All of that can matter.
Sustainable innovation also requires relational intelligence.
People need context.
Communities need communication.
Teams need opportunities to question assumptions.
Leaders need the humility to change course.
Implementation must account for the human beings expected to live with the consequences.
The goal is not simply to move an initiative from idea to completion.
The goal is to move an organization forward without unnecessarily breaking trust along the way.
That requires something far more sophisticated than "just do it".
It requires knowing when to move.
When to listen.
When to explain.
When to invite.
When to reconsider.
When to absorb responsibility yourself instead of pushing it onto the person beneath you.
Before pushing organizational change forward, it is worth examining whether you're leading the change or simply forcing implementation. These questions can help reveal the difference.
Do the people affected by this change understand why it is happening?
Have they had a meaningful opportunity to shape any part of it?
Am I interpreting questions as resistance simply because they slow the process down?
Who will absorb the fallout if this decision creates conflict?
Does the person implementing this initiative have enough authority to make adjustments?
Am I willing to publicly stand behind the decision if there is pushback?
What information might resistance be giving me?
Is the urgency real, or am I simply impatient?
What relationships could be damaged by the way this is being implemented?
Will people trust leadership more or less when this process is over?
Better change leadership does not require endless meetings or organizational paralysis. It requires a few deliberate practices that protect both progress and trust.
Clarify decision ownership.
Make it clear who made the decision, who helped shape it, and who has authority to modify the implementation.
Build a listening phase into implementation.
Even when the destination is fixed, people can help identify the best route.
Explain the why before announcing the what.
Context dramatically changes how people experience change.
Give implementers real authority.
If someone leads the work, they need permission to adapt the plan when reality demands it.
Stay visible when resistance appears.
Leaders should not disappear once the difficult conversations begin.
Study the fallout.
Pushback, confusion, frustration, and unintended consequences should inform the next decision.
Slow down when trust is at risk.
A delayed initiative can recover. A deeply damaged culture is far harder to repair.
The Leadership Lesson
There is a version of leadership that celebrates the person who can walk into resistance and force something through.
That person gets things done.
Until the accumulated damage catches up.
Organizations eventually pay for change that moves faster than understanding.
They pay through distrust.
They pay through disengagement.
They pay through turnover.
They pay through quiet compliance from people who no longer believe their voices matter.
They pay when talented leaders learn that taking responsibility means standing alone when something goes wrong.
“Just do it” may be good advice when fear is stopping action. It is terrible change-management advice when people, trust, and culture stand in the way.
The problem is not decisive action.
The problem is confusing decisive action with effective leadership.
Innovation does not require avoiding resistance.
It requires understanding what resistance is telling you while still having the courage to move.
There are moments when leaders need to push.
There are moments when they need to pause.
The innovation mindset is knowing the difference.
Getting something done is not the same as leading people through it.
Sometimes "just do it" gets the initiative implemented.
Sometimes it creates fallout.
Sometimes the fallout is nuclear.
The true measure of leadership is not whether the initiative survived.
It is whether the people and the organization did too.
Comments