Data as a Mirror: See and Know the System (Learning Entry 4: Data as a Mirror: How Teams Learn to See the System)

Data as a Mirror: How Teams Learn to See the System 

By: Dr. Morgan Goering and Erin Potter

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

Estimated read time: ~8 minutes 

A mirror doesn’t tell you what to do. It tells you only what exists. 

When we say data is a mirror, we’re not talking about another way to “track progress.” We’re talking about the discipline of seeing the patterns, blind spots, drift, alignment (or misalignment) between what we value and what we do in practice. A mirror is honest, and honesty can feel sharp when you’re already carrying pressure. Mirrors can also be kind because when held well, they can prevent us from making up stories. They can keep us from scapegoating individuals, and they can help us stop guessing. 

The question is not whether we have data; it's likely in abundance if you sit to list it. The question is whether our teams have learned how to use data to see the system, including the adult operating system. A mirror is a discipline of seeing. And in systems work, seeing is not neutral; it’s constructed together. Sensemaking research reminds us that people act based on the meaning they build through interaction, not the “objectivity” of information alone (Weick, 1995). When leaders rush the room to interpretation, they don’t just speed up time; they narrow the meaning-making space. 

This series began by widening what counts as data, then moved into inquiry, and then named fear as a rational response when data has historically been used as judgment. This final entry asks a different question: 

What does it look like when teams build routines that keep data functioning as a mirror over time? 

Data as Human Experience: What Happens in the Room Is Data 

Most educators can picture the moment: A chart goes up, the room shifts, and eyes move toward the leader. The silence changes shape, and that change is a part of your data. 

Who speaks first? Who waits? Who stays quiet? What questions are safe? How quickly does the team move to closure? Is uncertainty tolerated, modeled? Take notice.

Teams are always reading signals about what data is for, and those signals create predictable responses, some curious, some protective. Organizational learning research has long described how defensive routines emerge under perceived threat (Argyris & Schön, 1978). In data conversations, those routines can look like: 

• quick agreement without meaning 
• quiet compliance 
• rushed solutioning
• private skepticism that never makes it into shared learning 

None of these is an individual character flaw. They are adaptations to what the system has taught people is safe. This is why psychological safety matters, not as an abstract value, but as a condition for voice and learning. When teams believe they can take interpersonal risks without embarrassment or punishment, learning behavior increases (Edmondson, 1999). Data becomes a mirror when teams can say, out loud: 

“I don’t know yet.” 
“I see it differently.” 
“Can we slow down?” 

Leadership Practice in the Moment: Three Moves That Keep the Mirror in Place 

When data functions as a mirror, leadership often looks like restraint and structure, not charisma. 

Move 1: Name the purpose before the numbers 

Teams cannot interpret everything at once. “Looking at data” is not a purpose. Purpose is protective. It clarifies what belongs in the room and what doesn’t. Improvement science emphasizes disciplined inquiry aimed at a specific problem of practice, learning quickly, together, toward better outcomes (Bryk, Gomez, Grunow, & LeMahieu, 2015). Without a defined aim, teams drift into storytelling, blame, or a checklist review that no one owns. 

A simple anchor question changes the tone: 
“What is this team responsible for noticing and improving?” 

Move 2: Hold both lenses: students and adults 

A mirror reflects the whole system. If the mirror only points at students, it becomes a microscope, and microscopes tend to magnify deficits. Equity-centered data practice requires attending not only to outcomes, but to belonging, identity, access, and experience, dimensions that dashboards alone rarely capture (Ladson-Billings, 1995; Hammond, 2015). It also requires noticing what Safir and Dugan call “street data”: the lived experiences and patterns that reveal how the system is experienced, especially by those historically marginalized by traditional measures (Safir & Dugan, 2021). 

So leaders consistently hold the second lens: 
“What might this be asking of us?” 
“What adult practices or conditions are shaping what we’re seeing?” 

Move 3: Slow down interpretation enough for meaning to form 

Sometimes, leadership is delaying closure. Not delaying forever, delaying just long enough for the team to make meaning together. Sensemaking is social (Weick, 1995). When leaders move quickly to explanation, they unintentionally convert shared inquiry into passive reception. When leaders slow the pace, they protect thinking. In our work across teams, we often need to accept and expect non-closure because continuous improvement and change grounded in real or vulnerable data conversations can take longer than the agenda item allots time for. This is not softness or inaction; it's the slow but intentional building of infrastructure. 

System & Structure Lens: If We Want Mirrors, We Need Routines 

If teams are expected to “use data well” without consistent structures, the system will rely on individual talent and endure uneven practice. Four structures protect the mirror effect: 

1) Team purpose drives what data belongs in the room 

Different teams need different evidence because they have different responsibilities. Research on instruction and teacher learning shows that data use is shaped by the institutional context, roles, norms, time, and decision authority, not simply individual skill (Cobb, McClain, Lamberg, & Dean, 2003). When the purpose is unclear, teams either review everything or avoid anything that feels risky. 

2) Cadence matters more than volume 

Many systems do “data events.” Mirrors work because they are used repeatedly. A predictable cadence reduces threat and cognitive load. It also supports sustainability: routines that remain stable even when people change. When data only appears in high-stakes moments, fear becomes rational again. 

3) Protocols protect thinking 

When teams lack a protocol, the loudest sensemaking wins, or the safest interpretation survives. Structured dialogue tools help teams suspend judgment, surface assumptions, and build shared meaning before action (Data-Driven Dialogue protocols are built for this purpose).  Similarly, ORID (Objective–Reflective–Interpretive–Decisional) supports teams in sequencing how humans naturally process experience, preventing premature conclusions. Protocols don’t make the work mechanical. They make it more humane. Choosing a consistent structure that works for your team's purpose and ensuring that all members are trained in its use can support collective meaning-making.

4) Team self-reflection is part of the data routine 

Data is not only about student response. It is also about adult behavior. If teams never examine how they are using data, who carries the interpretation labor, whether the inquiry is real, and whether psychological safety is enacted, data drifts into compliance. This is one reason inquiry matters as double-loop practice: the team learns not only to adjust actions, but to examine assumptions and routines shaping actions (Argyris & Schön, 1978). Building in checkpoints to examine the team's efforts toward their purpose, where practices, operations, or implementation barriers and successes can be shared freely, allows for small items to be handled before they become an ingrained structure that hinders better work.

Check out this Data as a Mirror: Double Loop Conversation Framework to support teams and leaders in guiding reflective data conversations when working to build a culture of curiosity while balancing the integrity, humility, and grace of the adult learners in the data conversation.

Reflect. Connect. Grow. 

Choose a few of the prompts below to interpret your meaning of the learning you engaged in in this entry, begin to notice the patterns of your system, and connect work across contexts.

Reflect (individual sense-making) 

• Where does data feel heavier than it needs to be right now? What might that heaviness be protecting? 
• What assumptions might I be carrying into this interpretation? (Weick, 1995) 

Connect (system patterning) 

• Who carries the most responsibility for “making meaning” of data in our system? What does that reveal about our teaming structures? (Cobb et al., 2003) 

•  Where are pockets of strong data practice—and what conditions make them possible there? 

Grow (intentional direction without urgency) 

• What is one small routine we could add that protects curiosity before interpretation? (Edmondson, 1999) 
• How could we build a quarterly mirror check—team self-evaluation—so data remains a mirror, not a performance tool? (Argyris & Schön, 1978) 

Looking Forward: The Mirror is the Beginning, Not the End 

In our next entry, Janine Gacke brings the mirror into the reality of statewide implementation and behavioral systems leadership. As an Education Program Consultant in Iowa’s Division of Special Education, and a former district behavior supervisor. Janine has worked at the intersection of policy, practice, and people, where data is not abstract, but operational.

Her work spans MTSS, Tier 3 behavior systems, Specially Designed Instruction (SDI), and statewide scaling of evidence-based practices. She has led teams through the complexity of interpreting behavior and implementation data in moments that carry high stakes for students and adults alike.

In her entry, Janine explores what happens when data moves from conversation to consequence, when compliance, correction, and care coexist in the same room. She invites leaders to consider:

• How do we hold accountability without collapsing curiosity?
• What does it mean to scale implementation without scaling fear?
• How can behavioral data remain a mirror rather than a mandate?

If this series has asked how we notice, question, and reflect, Janine’s contribution asks what it looks like to lead when the mirror is public.

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.  
Hammond, Z. (2015). Culturally responsive teaching and the brain. Corwin. 
Ladson-Billings, G. (1995). Toward a theory of culturally relevant pedagogy. American Educational Research Journal, 32(3), 465–491. 
Safir, S., & Dugan, J. (2021). Street data. Corwin. 
Weick, K. E. (1995). Sensemaking in organizations. Sage.