Reflection
Why I Built a Framework for Leading Change
A first-person reflection on what I have learned leading and studying school transformation — why so many initiatives die quietly, what it actually takes to lead the human side of change, and why I built this framework to make transformation something schools embrace and sustain rather than survive.
Why Initiatives Fail When Leaders Manage Programs, Not People
I have watched too many good initiatives die quietly — not because the idea was wrong, but because the leader managed a program instead of leading people through change. We roll out the platform, deliver the training, publish the plan, and then act surprised when nothing shifts. The truth I keep returning to is that organizations do not change; people do. A program is a set of activities; a transformation is a set of human decisions to think, work, and believe differently. When leaders treat change as logistics — timelines, tools, compliance — they skip the only work that actually matters.
This is the failure pattern I designed the framework against. Initiatives fade because the "why" was never made compelling, because the people expected to live the change were never asked to shape it, and because no one tended the change once the launch energy faded. I built a framework that refuses to let leaders mistake activity for transformation.
Leading the Human Side of Change
If change is human, then leading it is fundamentally about urgency, vision, and coalition. I have learned to resist the pull to act first. Before anything is implemented, people need a reason to move — a felt, honest urgency that makes the status quo less safe than the change. Then they need a vision vivid enough to picture themselves inside, not a mission statement but a believable better future. And they need to see that they are not alone: a guiding coalition of trusted colleagues who carry the change into every corner the leader cannot reach.
What I find hardest, and most important, is the discipline to slow down to go fast — to spend real time building belief and ownership before launching activity. Every time I have skipped that work to save time, I have paid it back with interest in resistance and decay later.
Stakeholder Engagement and Managing Resistance
I used to think of resistance as the obstacle. I now think of it as information. When people push back, they are usually telling me something true — that the change threatens something they value, that I have not made the case, or that I am asking for trust I have not yet earned. The leaders I most admire engage stakeholders before they need them, mapping who holds influence and who feels the stakes, and inviting people to shape the change rather than simply receive it.
I have learned to win over credible skeptics rather than route around them, because a converted doubter is the most persuasive advocate a transformation can have. Engagement is not a communications task bolted on at the end; it is how ownership is built, and ownership is what makes change survive the leader who started it.
Communication as the Engine of Change
I have come to believe that communication is not a phase of change — it is the engine of it. People do not resist change so much as they resist confusion, and in the absence of a clear, repeated message they will write their own story, usually a fearful one. So I over-communicate the "why" before the "what," I make it two-way so I can hear what the change feels like from the inside, and I repeat the vision long past the point where I am bored of saying it — because that is roughly the point where people are starting to believe it.
The most underrated communication tool I know is honesty about what is hard. Naming the difficulty, the past failures, and my own uncertainty builds more trust than any polished launch — and trust is the currency every transformation runs on.
Sustaining Change in the Culture, Not Just Launching It
The failure I am most determined to prevent is the one that happens after the launch succeeds. A change can go beautifully for a term and still evaporate, because it lived on enthusiasm rather than in the culture. I have learned that sustainability is the work, not the wrap-up. From the very first phase I now ask: what routine, system, story, or norm will hold this in place once the attention moves on?
Embedding change means anchoring new practices in how the school actually runs — its calendars, its meetings, its hiring, its language about itself — and celebrating the change until it becomes simply "how we do things here." When a new staff member arrives and learns the changed way as the only way they have ever known, the transformation is finally complete. That is the standard I hold myself to: not launched, but embedded.
What This Demonstrates About Leading Transformation
Building this framework — and the case study that brings it to life — clarified what I most want my leadership to stand for. It demonstrates that I can take the research on change and turn it into something a leader can actually do on a Monday morning. I can hold the sequence under pressure: urgency and vision before action, coalition before mandate, engagement before rollout, and embedding before celebration.
It also demonstrates a point of view I am willing to defend — that leading change is a human discipline, not a project-management one. The framework is my argument that transformation succeeds when leaders lead people, and my evidence that I can translate change research into practice that schools embrace and sustain.
What it demonstrates
This work demonstrates my ability to translate established change-leadership research — Kotter, ADKAR, transformational leadership, systems thinking, and organizational development — into a coherent, usable framework; to lead the human side of transformation through urgency, vision, coalition, engagement, communication, and embedding; and to design change that is owned locally and sustained in culture rather than dependent on any single leader. It is the through-line from my doctoral study of the behaviors that sustain people through change to a practical system any school or system can lead with.
What I'd Build Next
This framework is a foundation, and I already know where I want to take it. I would build a change-leadership development program that grows internal coalitions and change coaches, so a school's capacity to lead transformation outlasts any one principal. I would deepen the tools for the "messy middle" — the period after launch where most change quietly dies — with rhythms and dashboards that keep the human side of change visible.
And I would extend the framework outward, from single schools to networks and systems, with shared readiness measures and a "coach the coaches" model so leading change becomes the default way improvement happens — not a campaign a system endures, but a capability it owns. That is the work I am building toward.