Needs Sensing & Planning

Continuous improvement is not an annual compliance exercise. It is an ongoing process of understanding needs, identifying causes, focusing priorities, planning action, and learning from implementation.

Understand the Need Before Choosing the Solution 

Build a Shared Data Story

A productive data conversation begins by separating what the evidence shows from what participants believe it means.

Teams can develop a clearer data story by examining four complementary forms of evidence:

• Outcomes: What are students learning and experiencing? Consider academic achievement and growth (see Adeq Growth to combine both), comparison to similar schools (see RNN Data or SEDA), attendance, behavior, engagement, graduation, well-being, and other desired outcomes. What strengths and bright spots should we recognize and build upon?

• Demographics & Context: Who are the students, families, educators, and communities being served? What contextual factors may help the team understand the patterns it sees? What patterns are consistent across multiple sources of evidence? Which students or groups are being served well, and which are not?

• Perceptions & Experiences: What do students, families, educators, and community partners say about their experiences, needs, opportunities, and sense of belonging? Which conditions are within our influence?

• Processes & Practices: What instructional practices, programs, structures, policies, and support systems are currently in place—and how consistently are they being implemented?

The value comes not only from reviewing each type of evidence, but from considering where the findings intersect. A pattern found in student outcomes may become more understandable when examined alongside perceptions, participation, instructional practice, or access to resources. Which need is important enough to receive focused attention? What factors may be contributing to the current results? What are the root causes?

Move From the Data Story to a Focused Plan

Once a team has identified and better understood a priority need, the next step is to develop a plan that people can understand and carry out. An improvement plan should guide ongoing decisions rather than become a document that is completed, submitted, and set aside. 

A practical improvement plan connects:

• A clearly defined need: What condition or outcome should improve?

• A root cause: What is contributing to the current condition and is within the organization’s influence?

• A measurable goal: What should change, for whom, by when, and how will progress be measured?

• A focused strategy: What evidence-informed practice, program, or system is most likely to address the identified cause?

• Purposeful activities: What must be done to prepare for, support, and sustain implementation?

• Clear responsibilities and resources: Who will do what, by when, and with what support?

• Measures of progress: How will the team know whether implementation is occurring and whether outcomes are improving?

As teams learn from implementation, they may need to refine activities, strengthen support, reconsider timelines, or revisit assumptions about the causes of a need. Planning is therefore part of a continuous and overlapping cycle—not a single event completed before the “real work” begins. The internal work is often messy, but some districts, like Bear Valley, have found ways to present a clean public facing document that has some summary of the complex plan.