Change Management that Feels Human
If you’ve watched a dozen change efforts this year, you know the same chorus shows up:
“ADKAR works,” or “we just need to be Agile.” I’ve been on the ground for enough transformations to know that’s only the headline.
Change is messy, relational, and stubbornly human.
It’s less about a framework and more about the stories we tell, the trust we earn, and the habits we replace.
I share a broader, more human approach to change, one that sits beside ADKAR and Agile, not in their shadows.
Think of it as a lived‑in map for turning ideas into durable shifts.
Change is a system you feel, not a checklist you tick
I once watched a team celebrate a training milestone, only to see the adoption stall weeks later.
The missing link wasn’t willpower; it was a friction point in leadership behaviour, incentives, and daily rituals that didn’t align with the new way of working. The real magic happens when you map change as an ecosystem, the people at the table, the decisions that get made, and the rituals that either reinforce or erode the new habit.
Action you can take:
Draw a simple system diagram of your change.
Identify who influences what and where friction lives. Design interventions that touch multiple levers at once: communication, sponsorship, capability, and governance.
People and culture come first, even when the tech shines. A frontline manager told me, “The tool is nice, but trust is the true onboarding.” Technology can enable change, but it’s trust, clarity, and psychological safety that sustain it. The best bright spots come from leaders who model the change in real conversations, not just in dashboards.
Lead with story and empathy.
Co‑create the change narrative with frontline teams. Invest in sponsor coaching and frontline coaching that demonstrate the new behaviours you want to see.
Sustainability isn’t an afterthought.
A successful launch isn’t the same as lasting impact. I’ve seen organisations “land” a change, only to watch it fade because daily routines, performance conversations, and rewards weren’t redesigned to reflect the new state.
Clarity around governance and decision rights.
In a recent programme, a decision about configuration changes got stuck in a long chain of approvals. Momentum died there, quietly. Clear decision rights aren’t flashy, but they’re the fuel that keeps momentum from turning into drift.
Add outcomes staff actually care about.
Customer impact, employee engagement with the change, time‑to‑value, and early indicators of habit formation (where friction drops, help requests decrease, workflows normalise).
Stakeholder ecosystems, not single audiences.
Change ripples across functions, geographies, and levels. Celebrate one group's wins without overlooking the tensions another group experiences.
Do a broad stakeholder map
Sponsors, champions, sceptics, early adopters, and operational advocates. Design targeted conversations and support for each group’s reality.
Risk is a living companion.
Risks evolve as people react and as technology landscapes shift. Treat risk management as an ongoing capability
Maintain a living risk register with early signals, owners, and adaptive mitigations. Schedule regular risk reviews with your leadership forum.
Technology as a platform, not the destination. New software is a catalyst, not the change itself. If workflows and rituals aren’t redesigned to fit the tool, adoption sags.
Coach leaders on change conversations.
Make visibility of commitment a metric, not a checkbox. Tie leadership behaviours to incentives and performance reviews.
A living discipline: learning and adaptation. Change isn’t a one‑off project; it’s a capability you practise. The most resilient teams continuously refine what works and what doesn’t.
I’d love to hear your experiences.
Have you led change programmes that refused to be boxed into ADKAR or Agile?
What practices helped you move from activity to lasting impact