FAQ · EXECUTIVE
When a change initiative goes sideways, leaders usually blame the people — “they’re resistant,” “they don’t want to adapt.” Most of the time, that’s backwards. Resistance to change is almost always resistance to unclear change.
People don’t fight a better future. They fight a future they can’t see — one where they don’t know why it’s happening, what it means for their job, or what “done” looks like. Clear those three up, and most resistance melts before it forms.
Lead with the why, not the what
The order matters. Most leaders announce the what — the new system, the reorg, the new process — and expect the why to be obvious. It never is.
Before you ask anyone to change their behavior, tell them, in plain language, why. What problem are we solving? What breaks if we don’t? People will tolerate a lot of disruption if they understand the reason and believe it’s real. They’ll resist even a good change if it feels arbitrary.
Define “done” before you start
The second killer is ambiguity about the end state. “We’re becoming more agile” isn’t a destination; it’s a mood. A change has to have a concrete end point: what’s different when we’re finished, how we’ll know, and what stops happening.
If you can’t describe the end state in three sentences, don’t announce the change yet. You’re not ready.
Run change through TRADE
Change management isn’t a separate discipline bolted onto leadership. It’s the same five beats you use for everything:
- Task Preparation — scope the change, and be honest about what it costs.
- Resource Allocation — make sure people have the tools and the air cover to actually do it.
- Action Execution — roll it out in small, visible steps, not one big bang.
- Debrief & Reflection — check in honestly: what’s working, what’s breaking.
- Evolution & Improvement — adjust. The first plan is never the last plan.
The old saying applies: Proper Planning Prevents Poor Performance. Most change fails in the preparation step — not because people are stubborn, but because the plan was vague.
Your one move this week
Write the “why” and the “done” in three lines each, before your next change announcement. If you can’t, that’s the work — not the rollout. Hand those six lines to your team before you ask for the behavior, and watch how much smoother the conversation goes.
When the change is bigger than a memo
For one-off changes, clear communication does it. For an organization that’s always changing — scaling, restructuring, adopting new systems — the fundamentals need to live in the team, not in your announcements. That’s the deeper work: the 24-Month Transformative Leadership Program builds change management into Month 9 and continuous improvement into everything after. And if the change is operational — new SOPs, new workflows — that’s organizational consulting, not just a talk.
The rollout sequence
In practice, the order is everything. First, name the why — the problem, in one or two honest sentences. Second, describe done — what’s different when it’s finished. Third, resource it — give people the time and tools to actually change, not just the instruction to. Fourth, run it in small steps and debrief each one. Most leaders skip straight from step one to step four — announce, then expect. That’s not change management; that’s hoping. The leaders who get adoption spend their time on the first two steps, because that’s where the resistance actually lives.
Take the Chaos vs. Capacity Scorecard to see whether your team is ready for what’s next.