School Districts Don't Want a Data Warehouse, They Just Don't Know it Yet...

I've spent the past year connecting with leaders in school districts across the country regarding their data needs - more specifically, their purposes for using data. Not surprisingly, schools are experiencing similar challenges and share similar goals regardless of location.

While the words they use to describe their problems and the goals they define in their strategic plans differ, they're generally looking to find ways to improve tier 1 instruction, empower teachers with data to support their professional learning communities (PLCs), streamline the ways they implement and manage tier 2 tier 3 interventions, find ways to increase collaboration, and create efficiencies to help offset time and resource limitations.

Knowing those goals, it's interesting to note that most inbound requests we receive are to "review a data warehouse." That's an interesting choice of words given what we know most districts are really trying to accomplish. To be fair, the idea of breaking free from data silos and moving toward centralization or a "one stop shop" with access to data analysis is also high on their list - though that's a function that supports the goal (or a tactic vs. a strategy), not the other way around.

In the world of K-12 business intelligence, a traditional data warehouse works in concert with operational systems including an SIS, assessment data systems (such as FastBridge, STAR, NWEA MAP, and iReady) curriculum-based measurements (AIMSweb, DIBELS, etc.) and others by ingesting the raw, meta, and summary data for use in what are typically considered "data marts" that are often tailored to a specific user (finance, teachers, interventionists, etc.).

That said, when districts suggest they're looking for a data warehouse, what they're really looking for is a system that integrates the data warehouse and data mart components in a way that can transform data into information so that it can be used to empower educators to take action.

This important distinction is critical to understanding the "why" behind data centralization and visualization. Simply put, district leaders want to empower their teams with tools to that can be used to improve outcomes for students (stated in different ways, of course).

As educators, we seek to remove labels so that students do not associate themselves as something they are not (a "red" kid, or an "at-risk" student, etc.). As a consultant, it's also important that the districts I connect with have a clear understanding of what our solutions truly provide and how they can be used as tools to support comprehensive efforts to complement and improve multi-tiered systems of support across all tiers and for all stakeholders.

Depending on who reaches out, however, the value of the tools may still have shadows cast upon it as the day-to-day impact for multiple stakeholders cannot be fully understood by a single point of contact - especially with a "demo" approach to reviewing systems (more on this in a later article). As such, conversations generally move from the concept of a data warehouse to the more functional data mart (in other words, we need the data warehouse so we can...) and ultimately the 'why' behind the need. This is why it's so critical that the district is able to clearly articulate what their goals are not only for a system but also each stakeholder group.

During my consultations, my team and I emphasize a collaborative workshop approach that involves and empowers each stakeholder to share their goals and challenges openly so that we can identify and prioritize shared goals together and as partners. This not-so-subtle shift from "demo" to discussion helps ensure that all perspectives are heard - which will have a significant impact on solution adoption, lessens the burden of change management, and ensures that we're able to collaborate together throughout your solutions evaluation journey to ensure that you're able to make a fully informed decision.

A good question to put on your white board for discussion is, "We need data, so we can________________."

If your district is currently considering solutions for a data warehouse - be sure to clarify your 'why' so that you can have the conversations you deserve to have during this important time.

Author's Note: I value meeting new people, making new connections, and hearing new stories. If that's important to you as well, I'd love to connect with you directly. Please feel free to like, share, comment, or connect!