Just over 60% of change initiatives fail — not from a lack of urgency, but from a lack of a system that carries urgency past week one. This is the research behind the Onward Arc, and why twelve weeks of sequenced daily action succeeds where sweeping mandates don't.
Every principal knows the feeling of a good launch. The staff meeting where the new initiative gets announced. The energy in the room. The nodding heads. For a week, maybe two, it even sticks — people try the new thing, ask questions, show up differently.
Then the fire drill happens. A parent complaint lands. State testing windows open. A teacher goes on leave and nobody's covering fifth period. And the initiative that felt so urgent in September quietly becomes the initiative nobody mentions by November.
Most school systems don't have a problem starting things. They have a problem sustaining them. That's not a character flaw in any one leader — it's consistent with what change-management research has shown across industries for forty years: just over 60% of organizational change initiatives fail to fully achieve their intended outcomes, most often because the plan stopped at the announcement instead of continuing into daily practice.1
Schools are living this at a pace no other sector is. AI adoption alone has swept through classrooms faster than almost any technology before it2 — and every one of those adoptions is, underneath the tools, a change a human being has to actually make. Onward12 starts from a different premise than most edtech: this was never primarily a technology problem. It's a human problem in managing complex change, and it has a body of research behind it that most school leaders were never handed.
Organizational change isn't an unstudied problem — it's one of the most studied problems in leadership. Three bodies of work, in particular, answer three different questions a school leader is quietly asking at once.
The organizational sequence — how a whole staff or district moves from a standing start to a change that outlasts the leader who started it.
Organizations don't change — people do, one at a time. ADKAR is the individual sequence underneath every organizational rollout.
Not a sequence — a diagnostic. Five conditions have to be present simultaneously. Miss one, and you get a specific, predictable failure pattern.
Every one of these is rigorous, and every one of them is real. But look at where they were built to live: a Harvard case study, a corporate consulting practice, a systems-change conference handout. None of them was written for a principal with four minutes between the morning bell and a hallway full of kids. That gap — between board-room frameworks and Tuesday-morning practice — is the actual problem Onward12 was built to close.
Kotter and ADKAR both move in sequence — one at the organizational level, one at the individual level — and both sequences line up, almost step for step, onto the same four phases. Knoster doesn't move in sequence at all; it's the diagnostic lens checked continuously underneath, catching whichever condition is missing before it turns into a named failure mode.
This is the same four-phase arc on the homepage — here's the research underneath each phase, and what it actually looks like as a daily microaction.
Why this change? Who is affected? What does success look like?
Most launches skip straight to announcement. Onward12 spends the first two weeks doing what Kotter calls creating urgency and forming a strategic vision, and what ADKAR calls building awareness — but instead of a single town-hall speech, it's a leader answering three questions in their own words, then getting a daily microaction that turns those answers into language they repeat until staff can finish the sentence for them. Knoster's read on this phase: skip it, and what looks like resistance later is usually just confusion now.
Build buy-in. Identify resisters, allies, and champions.
Kotter's guiding coalition and ADKAR's desire stage both live here — and both are, underneath the theory, about specific relationships with specific names. So the microactions get specific too: connect with your identified champion and name what they're doing well, check in directly with a known resister instead of avoiding them, thank an ally publicly. A coalition isn't a slide with logos on it. It's four weeks of individual conversations that add up to one.
Daily microactions. Remove obstacles. Celebrate small wins.
This is the longest phase on purpose — four weeks, not one — because ADKAR's knowledge and ability stages are the ones a single PD day can't actually deliver. Real competence comes from repeated, low-stakes reps with feedback, which is the same adult-learning principle behind how new instructional practice gets built in a classroom, not just a change initiative. Onward12 removes obstacles and manufactures short-term wins daily instead of once a quarter, because Kotter's research is clear that momentum dies in the gap between kickoff and the first visible win.
Embed the change. Prevent backslide. Institutionalize the new.
The final phase is deliberately unglamorous. ADKAR's reinforcement stage and Kotter's final step — embedding change into the culture — both name the same risk: the moment leadership attention moves to the next crisis, an un-reinforced change quietly reverts. So weeks 9–12 aren't a celebration lap. They're a concrete action plan for what keeps happening after Onward12 isn't reminding anyone daily — which is Knoster's fifth condition, and the one most initiatives never write down.
Knoster's real power isn't the checklist — it's the diagnosis. Miss one of the five conditions and you don't get generic resistance, you get a specific, recognizable pattern. If you already know which one you're staring at, that's usually the fastest way to know where an initiative needs help this week.
This is the same diagnostic behind the free Initiative Readiness Assessment — twenty questions across these five conditions, scored, with your weakest one surfaced as your primary exposure before you spend twelve weeks finding out the hard way.
"The hardest part of managing change is mindsets — and finding coherence and alignment with district priorities."
Gerardo MartinezDirector of Technology, Westminster School District
"It is very difficult to get principals to execute change at the building level."
Dr. Mario AndradeSuperintendent, Nashua School District
"We're now past the early adopters and trying to reach the pragmatists and later-stage adopters. That's the hardest part of the change process."
Gary BeidlemanSuperintendent, Manhattan High Schools
Twenty questions across the same five conditions above. Free, five minutes, and a clearer read on where this week's work should actually go.