Every school system feels pressure to improve. Leaders are asked to raise test scores, improve graduation rates, reduce discipline incidents, strengthen student well-being, and modernize instruction—all at the same time.
When results lag, the most common response is to choose a new solution and roll it out: a new curriculum, a new behavior approach, a new technology tool, or a new professional development series. The intention is good. But many improvement efforts break down because schools are complex systems. One change in one place can bump into policies, schedules, staffing patterns, and routines somewhere else.
For example, a district might train teachers to differentiate instruction, but teachers may not have planning time built into the day. Or a school may adopt restorative practices, but long-standing classroom management habits and time pressures pull staff back to what feels faster and more familiar.
This is where continuous improvement comes in. It is not a single program. It is a way of working: diagnosing what is really causing a problem, trying solutions in manageable ways, learning from results, and adjusting through feedback and iteration.
Continuous Improvement, in Plain Language
Continuous improvement is a practical approach that helps school teams:
- Define a problem clearly (not just “students are struggling,” but where, when, and for whom).
- Look for system causes (the routines and interdependencies that keep the problem in place).
- Test changes on a small scale before going big.
- Use data and feedback to learn quickly.
- Refine what works and drop what doesn’t.
Some districts using continuous improvement have reported strong results, such as increased college applications, narrowed achievement gaps for English learners, and improved graduation rates. But even with promising examples, continuous improvement won’t spread just because it’s a good idea. Leaders choose improvement approaches based on their circumstances.
A Helpful Lens: “Jobs to Be Done”
The report The K–12 Improvement Imperative: Pathways to adopting continuous improvement uses the “Jobs to Be Done” theory to explain why leaders adopt certain approaches. The big idea is simple: people “hire” tools and strategies to help them make progress in a specific situation.
In K–12 improvement work, the report identifies three common “jobs” that shape how leaders decide to use continuous improvement.
Job 1: Correct
“I have a specific problem. Help me fix it.”
Leaders in the “Correct” job are often dealing with one stubborn, clearly felt issue—something that matters deeply and has not improved despite repeated attempts. Over time, they realize the problem isn’t just a missing program. It’s being held in place by the system around it.
What these leaders typically want:
- A way to solve a specific problem quickly
- Tools that feel practical, not overly theoretical
- Permission to start small with a few willing colleagues
What can get in the way:
- Continuous improvement can sound complex or time-consuming
- Leaders may worry they need extensive training before starting
What helps “Correct” leaders succeed is the same thing that helps many educators: a clear target, a small first step, and coaching that is available when it’s needed.
How this connects to student support services
In special education and related services, “Correct” might sound like:
- “Our speech referrals are high, but progress is inconsistent. What’s driving that?”
- “Students are missing services due to scheduling conflicts. How do we fix the system, not just the calendar?”
When schools “hire” a service partner, they often need more than a provider—they need a partner who can help teams see patterns, remove barriers, and adjust supports over time.
Job 2: Coordinate
“I’m frustrated. Help me rally others to move the needle.”
In the “Coordinate” job, leaders still have a specific problem, but it stretches beyond their direct control. They may need cooperation across departments, buildings, or roles. The barrier isn’t only the problem itself—it’s the difficulty of aligning people and processes that don’t naturally line up.
What these leaders typically want:
- A shared language and method to bring people together
- Strategies for cross-team collaboration
- A way to show leadership by making progress on a visible challenge
What they don’t want:
- A brand-new philosophy that requires everyone to “buy in” before anything changes
- Long training sequences without immediate payoff
For “Coordinate,” continuous improvement works best when it becomes a coordination tool: a way to clarify the aim, define roles, track measures, and keep teams focused on learning rather than blaming.
A school-based example
Consider attendance improvement. A principal can’t solve chronic absenteeism alone. Transportation, family communication, school climate, health needs, and community factors all intersect. Continuous improvement gives teams a way to test small changes (like new routines for follow-up calls or check-ins), measure impact, and adjust.
Job 3: Reorient
“We can’t do what we did in the past. Help us find a new way as a school system.”
“Reorient” is the biggest job. Leaders here aren’t facing one isolated challenge. They’re seeing breakdowns across the system—academics, behavior, staffing, operations, and student supports. They have learned the hard way that one-off initiatives don’t stick. Staff may respond to new programs with “this too shall pass,” especially if previous initiatives came and went.
What these leaders typically believe:
- Problems are interdependent and can’t be solved in isolation
- Real improvement must be done by the people closest to the work
- Top-down mandates alone won’t create lasting change
The challenge: continuous improvement can feel complicated to scale. A superintendent or district leader might understand it deeply, but teaching it across hundreds or thousands of staff members is hard—especially with staff turnover and competing priorities.
So leaders often simplify the language, translate the method into everyday routines, and accept that implementation will be uneven at first.
What “Reorient” looks like in real life
Instead of asking, “Which program should we adopt?” the system begins asking:
- “What do we want to get better at getting better at?”
- “How will teams identify problems, test changes, and learn together?”
- “How will we support different levels of improvement skill across staff?”
How to Choose the Right Entry Point (Without Overwhelming Staff)
One of the most useful takeaways from the report is that continuous improvement adoption depends on context. If you’re a school or district leader, you can start by naming which “job” you’re actually trying to do.
- If you’re in Correct: start with a small team, a tight problem statement, and quick cycles of testing and learning.
- If you’re in Coordinate: focus on shared measures, clear roles, and routines that keep cross-department work moving.
- If you’re in Reorient: invest in building system-wide habits, simple training resources, and tiered support so people can grow their improvement skills over time.
Catalyzing Improvement: What Primes Schools to Adopt Continuous Improvement
The report also highlights conditions that often show up before leaders choose continuous improvement:
- Repeated failure of past initiatives that makes leaders doubt another “solution of the month” will work
- Exposure to improvement methods or comfort with data-based problem solving
- Belief in front-line expertise, trusting educators closest to students to solve real problems
For organizations that support schools—like TinyEYE—this matters. The best partnerships don’t just deliver a service. They strengthen a school’s ability to implement, learn, and sustain improvements even when staffing changes or priorities shift.
Where TinyEYE Fits in the Improvement Story
As an online therapy provider partnering with schools, TinyEYE often works in the exact spaces where interdependencies show up: scheduling, staffing shortages, student needs that change over time, and the coordination required across educators, families, and service teams.
Continuous improvement thinking can support that work by encouraging schools to:
- Start with a clear aim (for example, increasing service consistency or improving student participation)
- Identify system barriers (like missed sessions due to assemblies, testing windows, or unclear communication routines)
- Test small changes (new scheduling routines, clearer referral steps, or improved documentation workflows)
- Review data and feedback regularly to refine what’s working
In special education, sustainable improvement is rarely about one perfect fix. It’s about building a system that can notice problems early, respond quickly, and keep learning.
Conclusion: Improvement That Sticks Is Improvement That Learns
Schools will always face an “improvement imperative.” But lasting progress usually requires more than adopting a new program. Continuous improvement offers a way to learn through action—especially when leaders understand their context and choose an entry point that matches the job they are trying to do: Correct, Coordinate, or Reorient.
For more information, please follow this link.
