The Output Lens Protocol
An Emergent Systems Thinking Protocol: Developing the capacity to redirect attention from what was agreed to what was produced.
What this is for: Developing the capacity to locate alignment in outputs rather than in conversations. Agreements, commitments, and shared understanding are made in meetings. Alignment — or its absence — shows up in what the system actually produces afterward. The practitioner learns to redirect attention consistently toward the evidence rather than the statement.
When to use: When a system keeps evaluating its alignment through the quality of its conversations rather than through what those conversations produced. When meetings feel productive but execution keeps diverging. When the same alignment discussion happens repeatedly without the underlying pattern changing. When the system confuses the feeling of shared understanding with the fact of it.
The goal: To develop the habit of reading outputs as the primary evidence of a system’s actual state — so that evaluation is grounded in what the system did rather than what it said it would do.
The foundation.
A system’s alignment is visible only in its outputs. Not in its stated commitments. Not in the energy of its planning sessions. Not in how well its members articulate shared direction. In what it produces.
This is not a cynical position. It is a structural one. Agreements are made in the context of a conversation — with all the ambient cues, relational pressures, and shared understanding that the conversation provides. Those cues dissolve when the conversation ends. Each person returns to their own context, their own pressures, their own interpretation of what was agreed. What the system actually produces is shaped by all of those individual contexts, not by the shared understanding that briefly existed in the room.
The primer establishes this directly: systems produce outputs that reflect their actual actions, not their intended purposes. Agreement is an intended purpose. Output is actual action. Reading one as evidence of the other mistakes the aspiration for the result.
Donella Meadows offered a practical discipline for this: starting with the behaviour of the system forces attention onto facts rather than theories. Behaviour is output. What the system does, not what it intends.
The moves.
1. Name where attention currently lives.
When the system is evaluating whether it is aligned, notice where attention goes first. Does it go to what was agreed in the last meeting? To whether people seemed to understand? To the quality of the conversation? If attention is living in the conversation rather than in what the conversation produced, the practitioner’s first move is to name that.
Not as a correction — as an observation. “We are evaluating our alignment through how the meeting felt. Let’s see where the alignment actually shows up.”
What happens: The system becomes aware of where it has been looking. The distinction between agreement and alignment becomes perceptible rather than theoretical. This naming is the prerequisite for what follows.
2. Bring outputs into the room.
Make the system’s actual outputs present and concrete. Not plans about outputs, not intentions toward outputs — the outputs themselves. What was delivered? What decisions were enacted? What resources were moved? What behaviors are observable?
If the outputs cannot be named specifically, that is the first finding. A system that cannot describe what it has produced has been operating primarily in the space of intention.
What happens: The conversation shifts from how things feel to what things are. This shift is often uncomfortable — the outputs may reveal a gap that the conversation had covered. That discomfort is structural information.
3. Place outputs alongside stated intentions.
Hold both — what the system said it would produce and what it actually produced — simultaneously. Not to judge the gap but to make it visible. “Here is what we committed to. Here is what we produced. What does the distance between these tell us?”
The practitioner’s role at this point is to hold the question open rather than to interpret the gap. The gap belongs to the system.
What happens: The system encounters the evidence of its own alignment or misalignment in a form it can examine. The evidence is no longer abstract — it is specific, bounded, and real. The system can now make choices about what it wants to do with what it sees.
4. Redirect attention back to outputs when it drifts.
Attention will drift back toward conversation, toward intention, toward explanation of the gap. Each drift is an opportunity to redirect — not punitively, but consistently. “What did we produce?” asked again and again becomes the practitioner’s primary contribution.
The redirection is not about the content. It is about training the system’s attention toward the evidence rather than the narrative.
What happens: Over time, the system develops its own habit of reading outputs first. The practitioner’s active redirection becomes less necessary as the system internalises the discipline. This is the practice working — the capacity is developing in the system rather than residing in the practitioner.
The internal calibration.
Before applying this protocol:
Am I looking at outputs or at intentions? Have I brought actual evidence into the conversation, or am I working from reported experience?
Am I holding the gap between intention and output as a question, or have I already decided what it means?
What outputs does my own practice produce? Am I reading my own alignment from what I say or from what I do?
The discipline.
Agreement lives in the meeting. Alignment lives in the outputs. Return to the outputs. When the conversation drifts toward how things felt or what was agreed, redirect to what was produced. The evidence is always available. The practitioner’s discipline is to keep bringing the system back to it.
If this protocol is part of the practice you are building, the paid protocols go further — developing the capacity to work with what the outputs reveal once the system can see them clearly.
🎧 Thank you for reading.
An Emergent Systems Thinking Protocol. © 2025 Victor Nuñez / LABKOM Co. Ltd. Thailand. All rights reserved.
Further Reading
Meadows, Donella H. Thinking in Systems: A Primer. Chelsea Green Publishing, 2008.
Weick, Karl E., and Kathleen M. Sutcliffe. Managing the Unexpected. 3rd ed., Wiley, 2015.
