TRC Blog

Are You a Data Leader or a Data Manager?

Written by Tom Kaster | Sep 11, 2026, 1:58:23 AM

Picture this: You're a school leader who believes, rightly, that your school isn't using data as well as it could. You've carved out a Monday afternoon for teams to meet, handed benchmark assessment results to team leaders and instructional coaches, and asked them to walk their teams through a See, Think, Wonder protocol and then build a plan for using the data to drive instruction for the rest of the quarter. You've allocated the time, provided a protocol, and set a clear goal. What could go wrong?

Now picture it from the teacher's side. It's mid-quarter, progress reports are due, and the day was derailed by a surprise assembly that left students, and nerves, in tatters. You arrive at an after-school data meeting that's not even on your usual meeting day. Someone hands you a spreadsheet: hundreds of rows, forty-plus columns, benchmark results you've never been trained to interpret. You work through a protocol while barely understanding what a good score looks like versus a bad one. The meeting ends, and you're somehow supposed to weave all of this into your lesson planning. What were they thinking?

The push for data-informed decision-making in schools is real, growing and largely worth celebrating. But there's a wide gap between doing it well and doing it in name only; and that gap almost always comes down to leadership style and data fluency at the administrative level. Which raises the question: what's the difference between a data leader and a data manager?

The conventional wisdom holds that leaders focus on vision while managers focus on tasks, and that effective administrators blend both. Fair enough. But when it comes to data initiatives specifically, the distinction plays out in concrete, consequential ways.

Managers tend to:

  • Schedule data meetings and hand teachers raw spreadsheets to analyze
  • Ask teams to discuss the data and identify what they "see and wonder"
  • Require each teacher to complete a SMART goal by the end of the meeting

Leaders tend to:

  • Protect time for data meetings by shifting lower-priority meetings to email when necessary
  • Pre-process and visualize data in formats teachers can actually use, with filtering options to surface patterns by student subgroup, learning support status, seating cohort and more
  • Anonymize data across classrooms so teams can identify trends without defensiveness
  • Facilitate the development of shared strategies that all teachers can implement, so every student benefits

The differences can be stark or subtle, and strong administrators draw from both columns. What matters most is which items they prioritize. So how do you become the kind of administrator your staff actually wants to work with when it comes to data?

Make the meetings matter:

Data-focused meetings need to be regular, protected and purposeful. But how you present the data will make or break them. Teachers are insightful, reflective practitioners. They are not data analysts. Handing them raw spreadsheets and expecting meaningful analysis in a 45-minute meeting sets everyone up to fail. The data needs to arrive pre-processed and, ideally, visualized. That's what makes it usable within the time constraints of a real school day.

Do the heavy lifting or find someone who can:

Administrators' time is as scarce as teachers'. However, if you want data-informed decisions to happen at the classroom and school level, someone has to do the preparation work upstream. That might mean building that capacity internally, tapping central office resources or engaging an outside partner. Making data accessible to a general audience is not a small task, but it's a prerequisite for making the use of data a genuine priority.

Build data literacy across your staff:

Weave data training into professional development throughout the year, not just how to read a dashboard, but how to ask the right questions when presented with data. Offer sessions on tools like Google Sheets or Excel, practical methods for ongoing data collection in a busy classroom, and quick analysis techniques that don't require a statistics background. When teachers feel competent with data, a data culture becomes possible.

Anonymize before you share. Teachers should never feel that their results are being put on display for colleagues to judge. When data is aggregated at the team or grade level and stripped of individual identifiers, it shifts the conversation from defensiveness to problem-solving. Let teams diagnose shared challenges and design shared solutions. Individual classroom data absolutely has a place, however, it should come after the group analysis.

Done well, a school data culture becomes self-sustaining; something teachers seek out rather than endure. Done poorly, it becomes one more initiative that fades quietly after a semester. The difference lies in whether leadership has done the work to set their teams up for success.

Tom Kaster is the founder of The Datafied Classroom, which helps schools turn fragmented student data, from IB exam results to MTSS data to attendance records, into intuitive visualized dashboards that teachers and administrators actually use. He spent nearly 20 years as a high school math teacher before starting the company.

  Email: tom.kaster@datafiedclassroom.com | Website: www.datafiedclassroom.com