Your Data Meeting Has a Blind Spot.
It's excellent at identifying who is struggling. It was never designed to ask why.
Your Data Meeting Has a Blind Spot.
It's excellent at identifying who is struggling. It was never designed to ask why.
Picture the meeting. Eight people around a table. A spreadsheet on the screen. A list of students with numbers next to their names.
You go down the list. This one is below the cut score — she stays in intervention. This one improved — maybe she's ready to exit. This one is new — let's get her scheduled.
Forty minutes in, you get to a fourth grader. She has been hovering around the 25th percentile in reading for over a year. Sometimes a little above. Sometimes a little below. Every meeting she gets the same response — pulled for more support when she's below the line, released when she clears it.
Someone moves to the next name on the list.
And then someone asks the question that had never been asked in that room.
Why is this happening?
What followed changed how I thought about every data meeting I'd ever sat in.
— — —
Here's what that question uncovered. This fourth grader — I'll call her Grace — had been pulled for intervention so many times that she had come to believe something about herself. That she was the kid who needed fixing. That something was wrong with her.
Her confidence had been quietly worn down — not by anyone's intention, but by the accumulated message of being removed from class again and again.
There was more. Her parents were going through a divorce. She was navigating the intensity of fourth grade friendships — the kind that ten-year-olds carry with them through the door every morning. And the classroom instruction, through no fault of malice but through inexperience, wasn't building the small wins that help a struggling reader think: maybe I can do this.
None of this was in the spreadsheet. None of it had been named in any previous meeting. Because the meeting had been built to sort students. Not to understand them.
— — —
Most data meetings are sorting sessions. They identify who is in the red, the yellow, the green. They schedule responses. They measure whether the responses worked.
What they rarely do — and what Grace needed someone to do — is ask what is underneath the number. What is the classroom experience for this student every day? What does she believe about herself as a learner? What is she carrying in through the door that the spreadsheet can't see?
The shift from sorting to understanding doesn't require a new meeting format or a new data system. It requires one question, asked honestly, before you move to the next name on the list.
Why is this happening?
That question is the difference between a meeting that keeps Grace in intervention for another six weeks and a meeting that actually changes something.
— — —
Before Your Next Data Meeting: Three Questions to Add to the Agenda
Add these before you open the spreadsheet. They take five minutes. They change who gets seen.
□ For each student who keeps appearing on this list — have we asked why?
Not what to do about them. Why does this keep happening? What is the system, the classroom, or the experience producing this outcome?
□ What do we know about this student that the data doesn't show?
Confidence, engagement, home situation, classroom conditions, relationship with the teacher. What is walking in through the door every morning that the cut score can't capture?
□ Is our response matched to what we actually found — or to the number?
More intervention is a response to the score. It may or may not be a response to what's actually producing it. Have we asked which one we're doing?
Grace eventually got the right support — once someone asked the right question. But she had been on that list for over a year before anyone did.
That's not a Grace problem. That's a meeting design problem.
.
Not sure which pattern your building is in?
The Move Toward Organizational Assessment is a free 10-question tool that identifies which pattern is producing your persistent problems — and gives you a specific first move.