Across the first seven episodes, the story has moved through a full cycle of change.
Urgency helped people see that the current way of working was putting too much strain on adults and leaving students without the consistent support they needed.
The guiding coalition brought together a cross-role group of people who were trusted and positioned to influence real decisions.
A clear vision and a focused set of initiatives answered the question, what are we actually trying to build in our MTSS and student support systems, and what big moves will take us there?
A volunteer army expanded the work beyond a small inner circle, inviting many more staff into roles that felt like real opportunities, not just extra duties.
Removing barriers focused on schedules, policies, forms, roles, data tools, and norms that quietly blocked willing people from acting.
Short-term wins gave staff and leaders early evidence that the work was making a difference, in both the numbers and in how daily life felt.
Sustaining acceleration was about building on those early wins, deepening what worked, spreading it thoughtfully, and avoiding both backslide and overload.
Now the focus turns to the final step in Kotter’s model: institute change. Kotter describes this step as articulating the connection between new behaviors and organizational success, and making sure those behaviors continue until they are strong enough to replace old habits, with systems and processes that reinforce the new way of working.
In simple terms, this step is about making the new way the normal way.
It asks a hard question.
How do we keep this from unraveling when people change roles, when district priorities shift, when leadership turns over, or when the spotlight moves on to something else?
In public education, that question is not abstract.
Many educators can name a promising initiative from the past that faded after a few years.
Maybe it was an earlier MTSS push.
Maybe it was a behavior framework, a student support redesign, or a new way of organizing interventions.
For a time, meetings were held, forms were used, and routines changed.
Then a superintendent left.
Or a principal changed.
Or a new mandate arrived.
Slowly, the language disappeared.
Older routines came back.
New staff arrived who had never heard the original story.
What had once been described as our new way became a memory held by a few people, rather than a pattern held by the system.
Instituting change is about preventing that pattern.
That does not mean freezing every form, script, or meeting forever.
It does not mean turning a living system into a compliance machine.
It means embedding the core behaviors, routines, and expectations deeply enough that they survive people’s departures and can continue to evolve.
That distinction matters.
Establishing a change is not the same as over-bureaucratizing it.
Leaders do not need to preserve every temporary tool exactly as it first appeared.
They do need to preserve the essential logic of the work: the core routines, the key expectations, the protections of time, and the commitments that made the new system better than the old one.
One way to think about this step is to ask a blunt question.
If every member of your current guiding coalition moved to another role in two years, what would remain?
Would your initiative continue because it is now part of how the district operates?
Or would it survive only in the memories and personal habits of the people who built it?
That question often reveals the work still left to do.
To see what instituting change looks like in practice, imagine a district that has spent several years strengthening MTSS, redesigning Tier 2 and Tier 3 supports, improving the quality of FBAs and BIPs, reducing removal-based responses, and trying to make staff work more sustainable.
The work has moved through the earlier steps.
There is urgency.
There is a coalition.
There is a vision.
There have been wins.
The system has not solved everything, but it is in a better place than it was.
Now the district wants to make sure that these gains do not disappear with the next leadership change.
The first place they look is policy and procedure.
For several years, much of the MTSS and student support work in this district has been guided by playbooks, training decks, and local agreements.
Those have been useful.
But they are not stable enough on their own.
The district’s policy team, working with the coalition, reviews student support and discipline policy.
They notice that the current language mentions interventions and supports in general terms, but does not clearly describe the district’s multi-tiered approach, the expectation for layered supports, or the commitment to using removal-based practices only when necessary for safety.
So they revise it.
The updated policy explains, in plain language, that the district uses a multi-tiered framework for academic, behavior, and social support.
It outlines the expectation that concerns move through a clear problem-solving process.
It describes the district’s commitment to coordinated Tier 2 and Tier 3 supports.
And it clarifies that schools are expected to use established structures for support planning before defaulting to reactive or removal-based responses whenever safety allows.
This policy does not try to script every meeting.
It does something more important.
It gives the work formal standing.
When a new principal asks, are we really expected to run these MTSS meetings and support processes, the answer is no longer, well, the previous administration cared about them.
The answer is, yes, this is how our district approaches student support, and here is where that expectation lives.
The second place they look is time structures.
Across the earlier episodes, a major theme has been the need to protect time for the work.
At first, protected MTSS blocks, Tier 2 planning windows, and problem-solving meetings often depended on individual principals making tradeoffs.
To institute the change, district leaders write these time structures into annual scheduling guidance.
The planning memo that goes to principals each spring now includes explicit expectations about a recurring problem-solving block during the contract day.
It identifies windows for data review and support planning.
The district also aligns its own demands with those windows.
It avoids scheduling competing district activities during the same time whenever possible.
That shift affects multiple roles.
Principals inherit a calendar template that assumes this work happens.
Teachers and support staff are less likely to experience problem-solving time as optional or temporary.
Counselors, psychologists, and paras can plan around more stable routines.
The third place the district looks is roles and job descriptions.
In the early years of change, much of the work may have relied on the initiative of certain people.
A principal who really believed in the vision protected the time.
A counselor who cared deeply about coherence coordinated plans that were not technically in their job description.
A teacher leader stepped in to support grade-level teams.
A para became the informal keeper of an important hallway routine.
That kind of discretionary leadership is valuable, but it is not enough to sustain a system over time.
So the district starts to formalize some expectations.
Teacher leader roles now include language about supporting grade-level problem-solving and MTSS implementation.
Counselor and school psychologist roles include clearer expectations around coordinated support planning, not just crisis response or isolated service delivery.
Assistant principal or dean roles include language about building preventative supports and aligning discipline responses with the district’s student support framework.
At the central office level, one position now has explicit responsibility for the health of the MTSS and student support system, rather than carrying it only as an informal side responsibility.
This matters when people are hired.
It matters when supervisors set expectations.
And it matters when leadership transitions occur.
The fourth place they look is onboarding and ongoing learning.
One of the easiest ways for a system to slide backward is for new staff to enter it without understanding the newer way of working.
They fall back on what they have seen elsewhere, or on what the loudest voice in the building says is normal.
To prevent that, the district builds MTSS and student support into its onboarding routines.
New teachers, counselors, paras, and office staff receive a simple training of how student support works here.
How do you raise a concern?
What happens next?
Who is involved?
What should you expect from the system?
New principals receive a leadership version of that training.
They review the district’s support framework, the meeting structures they are expected to protect, and the role they play in keeping the system coherent.
Even new central office leaders receive this grounding.
That matters because institutions backslide when new leaders inherit structures they do not understand.
The fifth place they look is culture, stories, and symbols.
This part is less formal, but it is just as powerful.
Culture is shaped partly by what people talk about and what they repeatedly notice.
In this district, staff meetings and leadership gatherings regularly include examples of the support system working well.
Not only crisis reports.
Not only compliance updates.
A teacher might share how a concern raised in September led to a coordinated support plan by October, and how that changed a student’s trajectory.
A counselor might describe how a Tier 2 routine is helping a group of students stabilize earlier in the day.
A para might explain how a consistent transition plan has changed the feel of a hallway.
Leaders connect those stories back to the larger message.
They make it clear that these are not isolated acts of heroism.
They are examples of the system working more as intended.
Symbols matter too.
The one-page MTSS flow is not just distributed once and forgotten.
It is referenced in meetings.
It is posted where people actually use it.
Leaders repeat phrases that reflect the new way of thinking, such as, we do not rely on superheroes; we rely on systems, or, if we are seeing the same crisis again and again, that is a sign that the system still needs work.
Over time, those phrases help new staff understand what is valued.
They also help long-time staff remember what the district is trying to protect.
Even with strong policies, stable schedules, role clarity, onboarding, and culture work, systems can still drift.
That is why instituting change also requires leaders to watch for backslide.
The signs are often subtle at first.
A protected MTSS block gets repurposed for another topic and no one says much.
An old referral form resurfaces because it is familiar.
New staff learn the quickest informal workaround rather than the newer shared process.
One school quietly returns to more reactive discipline because the principal is overwhelmed.
Staff begin to say things like, we used to have a system for that.
When those signs appear, the response cannot simply be blame.
It has to be inquiry, clarity, and correction.
District leaders can ask what is driving the drift.
Is the problem a leadership transition?
A scheduling squeeze?
Competing priorities?
A part of the model that was never as clear as it needed to be?
Then they can respond accordingly.
That might mean revisiting the calendar guidance.
It might mean retraining new leaders.
It might mean clarifying what parts of the model are non-negotiable and what parts are flexible.
That distinction is especially important here.
Not every element of the system needs to look identical in every school forever.
Some parts can and should flex by context.
A middle school may organize support meetings differently than an elementary school.
A large campus may need a different staffing pattern than a smaller one.
But some parts need to remain stable if the system is going to hold.
There must still be a clear path for raising concerns.
There must still be protected time for problem-solving.
There must still be expectations for layered supports and timely follow-up.
There must still be leadership attention to reducing fragmentation and overreliance on removal-based responses.
Instituting change means getting clearer over time about what is essential and what is adaptable.
It also means planning for succession.
When a principal, a coalition member, or a district leader moves on, the handoff should include this work.
Outgoing leaders can share what has been built, what is working, where the tensions still are, and what must be protected.
Incoming leaders can be oriented into the story rather than left to discover it by accident.
That matters at every level.
If a principal changes, building staff should not have to wonder whether the MTSS block still matters.
If a district support leader leaves, schools should not have to guess whether the referral process still stands.
If a counselor or para who carried important pieces of the system moves on, someone else should understand those routines well enough to continue them.
This is one reason documentation matters.
Not bloated manuals that no one reads.
Simple, shared, usable documents.
A one-page flow.
A brief leadership guide.
A calendar template.
A short onboarding module.
A clear list of roles and responsibilities.
These are not glamorous artifacts, but they are part of what makes change durable.
As this final episode comes toward a close, it helps to step back and see the full arc of the series.
Kotter’s model begins with urgency: recognizing that the current pattern cannot continue.
It moves to building a guiding coalition: assembling a group with enough trust and influence to guide the work.
It asks leaders to form a strategic vision: clarifying how the future will differ from the past and linking that future to concrete initiatives.
It calls for enlisting a volunteer army: creating the conditions for many people to want to contribute.
It requires leaders to remove obstacles: clearing the obstacles that slow people down and block progress.
It highlights short-term wins: the early, visible results that must be recognized and shared.
It pushes leaders to sustain acceleration: using growing credibility to keep improving systems, structures, and policies after the first successes.
And it ends with instituting change: making the new behaviors and ways of working strong enough to replace older habits, reinforced by systems and processes over time.
For educational leaders, the message is not that every improvement effort will move through these steps neatly.
Reality is more tangled than that.
The message is that lasting change requires attention at all of these levels.
It is not enough to launch a promising initiative.
It is not enough to have a few strong pilots.
The work has to become ordinary.
Not ordinary in the sense of invisible or unimportant.
Ordinary in the sense of reliable.
Students entering the system years from now should feel the benefit of what is being built now.
Staff entering the system years from now should step into clearer, more manageable routines rather than into a blank slate or a story about what used to exist.
That is the aim.
And for listeners thinking about how to use this series in real life, these episodes can function as more than a podcast. They can be used as a summer leadership study, a sequence for MTSS or student support teams, or a set of discussion prompts for principals and district leaders trying to lead change efforts more coherently.
Kotter’s eighth step is a reminder that the goal is not simply to start strong. It is to help a better way of working become durable enough to shape what comes next, even as people, pressures, and contexts change.
