Data as a Mirror: See and Know the System (Learning Entry 3: Moving from Fear to Curiosity: Data Literacy for Every Educator)

Moving from Fear to Curiosity: Data Literacy for Every Educator

By: Mandi Kopischke 

February Series: Data as a Mirror: See and Know the System 

Estimated read time: ~7.5 minutes 

When Data Feels Like Judgement, Learning Slows 

Most educators can name the moment. The meeting where data was projected on a screen and the room shifted. The report that arrived without context. The time data was used to explain what was wrong, but not what was possible.  

Or the quieter moments, sitting in a PLC, wondering if you were the only one who didn’t see what everyone else seemed to see in the numbers. Wondering if saying that out loud would make you look unprepared. For many educators, data is not neutral. It carries memory. It carries emotion. It carries stories about evaluation, compliance, and deficit thinking (Hammond, 2015; Safir & Dugan, 2021). 

If leaders want data literacy to grow across a system, they cannot start with tools or dashboards. They have to start with experience, because people do not learn from data when they feel threatened by it. They learn when they feel safe enough to be curious about what it might mean. Research on psychological safety reinforces this. Amy Edmondson’s work shows that people are more willing to share uncertainty, ask questions, and report mistakes when they believe they will not be punished or embarrassed for doing so. In those environments, learning accelerates because thinking becomes visible.  

Data literacy is not just a technical skill; it is a relationship. 

Every Educator Has a Data Story. Every educator learned what data meant somewhere. Some learned that data was used to sort and rank. Some learned that data conversations happened after decisions were already made. Some learned to protect themselves by staying quiet, agreeing quickly, or waiting for someone else to interpret. None of those responses are signs of resistance. They are signs of adaptation. 

I once coached a teacher who froze during a data conversation, even though she was highly skilled. Later, she shared that in her previous school, teachers were publicly ranked based on test results. That memory shaped her instinct to wait and watch rather than speak up. Her hesitation wasn't resistance; it was adaptation to what she had learned about how data was used.  

When educators hesitate in data conversations, they are often responding to the system they learned inside, not avoiding learning itself. This aligns with organizational learning research from Argyris and Schon (1978), who describe how people develop protective routines when systems punish vulnerability to mistake-making. When survival becomes the goal, learning slows.  

This matters because leaders sometimes interpret hesitation as a lack of skill or motivation. But hesitation is often information: 

• Information about psychological safety.
• Information about clarity.
• Information about whether data has historically been used to learn or to judge.  

Safe to say,  “I’m not sure what I’m seeing yet.”  “I might be missing something.” or “Can we slow down for a second?” 

Data Literacy Lives in Leadership Behavior 

Data literacy grows when leaders model how to be learners in front of data, not just interpreters of it.  

This can sound like: 

• “I’m noticing this pattern, but I’m not sure yet what it means.” 
• “What are you seeing that I might be missing?” 
• “What questions should we be asking before we decide anything?” 

I remember visiting a 3rd grade classroom where the teacher paused mid-lesson to notice a pattern in student engagement. One student who usually dominated the discussion was unusually quiet, and another who rarely spoke had a thoughtful comment. The teacher asked, “What do you notice here?” and invited students to share their observations. That brief moment of modeling curiosity made the data feel like a tool for understanding students, not a measure of compliance.  

These moments matter more than any training session because educators are constantly reading leader behavior for signals, often without realizing it: 

• Is this about evaluation?
• Is this about compliance? 
• Is this about improvement? 

Leaders set the emotional tone of data use long before teams engage with the data itself.  Research on professional learning supports this modeling effect. Thomas Guskey (2002) found that educator beliefs shift most powerfully when they see changes in student outcomes connected to new practices, not when they are simply told new information. In other words, feedback must lead to visible learning, not just awareness.  

When leaders slow down interpretation, they protect thinking. When leaders stay curious, they make curiosity possible for others. When leaders normalize uncertainty, they create room for learning.  

Data literacy does not grow through mandates; it grows through modeling.  

Data Literacy Is a System Condition, Not Just an Individual Skill 

Confidence with data does not develop in isolation. It develops inside systems that either support or constrain learning. Research on teacher learning environments shows that educators build data literacy fastest when they are supported in making real instructional decisions using evidence, not just reviewing data after the fact (Cobb, McClain, Lamberg, & Dean, 2003). 

Data literacy grows faster when: 

• Decision authority is clear. 
• Expectations for data use are consistent across buildings and roles. 
• Teams have protected time for sense-making, not just reporting. 
• Data conversations are part of normal work, not special events.
• Feedback leads to action, not just awareness 

When these conditions are missing, even highly skills educators can disengage data work because the system makes learning risky. This is why data literacy is not just a professional development goal. It is an organizational design responsibility.  

Leaders shape data literacy every time they: 

• Introduce data. 
• Frame data. 
• Respond to questions about data. 
• Decide how quickly action is expected.  

Clarity reduces fear. Predictability reduces cognitive load. Consistency builds trust. Trust makes curiosity possible. 

Curiosity Changes the Direction of Data Conversations 

Curiosity is not a personality trait. It is a condition created by the environment. When educators trust that data will be used to guide rather than judge, curiosity increases naturally. 

In a grade-level PLC I coached, a teacher nervously shared that her reading scores were lower than expected. Instead of jumping to conclusions, the team asked, “What else could be influencing this?” They explored interruptions to their schedules, student absences, and instructional shifts. By the end, the teacher was brainstorming small experiments for her lessons. Curiosity had turned fear into actionable insight.  

They are asking: 

• What might this be telling us? 
• Who else should we talk to before we decide? 
• What might we try next that is small enough to learn from quickly? 

This aligns with improvement science research showing that small, testable changes reduce fear and increase learning because teams can see impact quickly and safely (Bryk, Gomez, Grunow, & LeMahieu, 2015). 

Curiosity shifts data from something that happens to educators to something educators use for students. When curiosity spreads across teams, data literacy stops being an individual skill and becomes a collective practice.  

Reflect. Connect. Grow. 

Reflect (Sense-Making): Where does data feel heavier than it needs to be in your current context? What past experiences might still be shaping how data conversations feel today? 

Connect (System-Awareness): Where do you see confidence with data vary across roles or teams? What system conditions might be influencing that pattern? 

Grow (Intentional Direction): What is one small leader move that could lower threats before your next data conversation? What might become possible if your team experienced data with curiosity instead of evaluation?  

The Takeaway 

When educators experience data as a tool for learning instead of judgment, curiosity becomes sustainable. Sustainable curiosity is what allows teams to ask better questions, test better ideas, and respond to students with greater precision and care. Data literacy is not about knowing more. It is about creating conditions where people are safe enough to keep learning. 

Data does not build capacity on its own. People do. When leaders create systems where curiosity is protected, data becomes not something done to educators, but something built with them. 

When that happens, data stops being something teams survive and becomes something they use to move forward.... together.  

Looking Forward 

Next week, we will bring our data series to a close with a conversation about data as a mirror for each team that uses it. The when, how, and what. Knowing which data to examine when starts with the goals and responsibilities of the team and the questions they are trying to answer. To ground in teaming, consider checking out the Teaming That Holds: Leadership's Infrastructure series.  

References

Argyris, C., & Schön, D. A. (1978). Organizational learning: A theory of action perspective. Addison-Wesley. 

Bryk, A. S., Gomez, L. M., Grunow, A., & LeMahieu, P. G. (2015). Learning to improve: How America’s schools can get better at getting better. Harvard Education Press. 

Cobb, P., McClain, K., Lamberg, T., & Dean, C. (2003). Situating teachers’ instructional practices in the institutional setting of the school and district. Educational Researcher, 32(6), 13–24. 

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.