The Ladder of Inference for Sport & Esports Coaches
What is the Ladder of Inference?
The Ladder of Inference is a simple mental model that maps how humans move, often in milliseconds, from what we observe to what we do. Chris Argyris and Donald Schön introduced the idea in their work on organizational learning.
In coaching environments, the ladder explains why two people can watch the same rep or round and come away with different stories, and why those untested stories can quietly drive decisions, emotions, and culture. The Ladder of Inference, can be a powerful awareness and check-in tool for coaches and players alike to challenge what they are observing, believing and acting on continuously.
The six rungs (from data to action)
The Ladder of Inference is made up of the following six rungs (from bottom to top).
1. Observable data & experiences (what a camera would capture and what we notice)
This is the base of the ladder and it consists of all the raw information that is relevant to the situation. From points scored and plays made, to athlete reactions, language used, tone, posture, and in esports, comms or in-game choices. These observations are often informed by our beliefs, values, and experience—and when faced with a problem, our minds search for familiar patterns to enable rapid decision-making. The goal for the coach is to stay grounded here as long as possible: describe what actually happened before interpreting why it happened.
2. Add meaning (from culture/context)
Once we’ve noticed certain data, we begin to add meaning to it based on context—our team culture, environment, or past experiences. A coach might see an athlete walk off without eye contact and attach meaning like “they’re frustrated” or “they’re disengaged.” In esports, a player staying silent in comms might be interpreted as “tilt” rather than “focus.” These meanings aren’t inherently wrong, but they are subjective, filtered through personal and cultural lenses. Awareness here helps a coach pause and ask, “What other meanings might fit?”
3. Make assumptions
Meaning leads naturally to assumptions. Once we’ve decided what something means, we fill in the blanks with what we think is true. For instance, “If they’re frustrated, they must not trust my plan,” or “He’s silent because he doesn’t care.” Assumptions are shortcuts, mental models that help us respond quickly, but they can create blind spots. In high-performance environments, unchecked assumptions spread fast, shaping how we treat individuals and how they respond in turn. Effective coaches name their assumptions openly: “I’m assuming you’re quiet because you disagree—is that true?”
4. Draw conclusions
Assumptions, if left unchecked, harden into conclusions. We start believing our stories are facts: “The athlete isn’t coachable,” or “Our team always chokes under pressure.” These conclusions feel like truth because they’re built on real observations, but filtered through meaning and assumptions. The danger here is that conclusions can guide planning, selection, or communication before being tested. Coaches who stay aware of this rung consciously test conclusions by asking for athlete perspectives or reviewing objective data (e.g., video, performance metrics, comms logs).
5. Adopt beliefs (“this player is…”, “we always…”)
Over time, repeated conclusions crystallize into beliefs, generalizations that shape how we perceive and interact with others. Beliefs like “this player doesn’t perform under pressure” or “our team never wins scrims” can become self-fulfilling. They influence tone, opportunity, and trust. In team environments, these beliefs form the unwritten rules of culture, the “way we do things.” Great coaches challenge these patterns regularly, asking, “What belief am I carrying about this player or group, and is it still serving us?”
6. Take action (coach/athlete behavior follows the belief)
Finally, our beliefs drive our actions. A coach who believes a player is lazy may stop investing time in them. An athlete who believes the coach doesn’t listen may stop speaking up. The loop then reinforces itself, the behavior confirms the belief. Awareness of the ladder allows coaches to intervene earlier: pause before reacting, test assumptions, and invite shared interpretation. In practice, this might sound like, “Here’s what I saw… what was happening from your side?” Over time, this habit builds trust, accountability, and a learning culture where performance grows through dialogue, not directives.
Two crucial insights:
We filter at every rung; higher rungs are more abstract and less reliable.
We then “climb down” rarely; our beliefs start filtering future data, creating self-confirming loops (Argyris calls this single-loop vs. double-loop learning).
Why it matters in coaching
Buy-in is built on shared reality. When coaches and athletes see different “games,” trust and execution fracture. Soft-skill mastery (listening, inquiry, framing) is what converts compliance into commitment.
Psychological safety underpins honest sense-making. Teams that feel safe to question assumptions learn faster and correct sooner—vital in high-velocity esports metas or injury-constrained return-to-play.
Data ≠ meaning. Even in data-rich environments (“invisible monitoring,” GPS, dashboards), people still interpret, often inconsistently. Coaches need protocols to separate what happened from what we think it means.
Two coach-specific failure patterns the ladder explains
The Directive Spiral (Top-Down Only).
You see a missed rotation → assume apathy → conclude “player isn’t committed” → tighten control (more rules), which reduces autonomy and engagement → confirms your belief.
Fix: Balance advocacy and inquiry: state your view and ask how they see it. Leading SapiensThe Data-Trap (Tech ≠ Truth).
You notice a dip in APM or RPE spike → assume poor sleep → prescribe volume cuts → athlete interprets as “coach doesn’t trust me,” withholds info → your dashboard “proves” they’re unreliable.
Fix: Start at observable data, then test inferences explicitly. Schwarz Associates
How to use the ladder in practice
A) Pre-brief: Build a shared bottom rung
Use this 3-minute huddle before a session/scrim:
Facts first: “What will the camera/match log show if we succeed today?” (e.g., “3 of first 5 map rotations on time; comms <1.5s delay on mid-round calls.”)
Signal plan: “What specific data will we watch?” (GPS HSR bursts, micro-split times, cooldown adherence; or in-game ult-economy calls, retake timings.)
Meaning agreement: “If X happens, what might it mean? What won’t we assume yet?” (Normalize uncertainty.)
This anchors everyone on the same base rung before pressure kicks in—key to preventing leaps. (See Senge’s “mental models” work.) The Systems Thinker
B) Live coaching: Speak in advocacy + inquiry pairs
A simple script:
Name the data (bottom rung): “I saw two late rotates on B in the last three rounds.”
Offer a tentative meaning (advocacy): “I’m thinking our trigger to leave A is unclear.”
Invite their data/meaning (inquiry): “What are you seeing/hearing that I’m missing?”
This pattern operationalizes Argyris’ “high advocacy/high inquiry” and reduces defensiveness mid-game or mid-set.
C) Post-session debrief: Climb down before planning up
Run a 10–12 minute debrief with the Left-Hand Column tool:
Right column: transcribe a short, sticky exchange (voice chat clip or touchline correction).
Left column: each person privately writes what they thought/felt but didn’t say.
Compare & test: “Here’s what I saw/heard; do you see it differently?” → “I inferred ___; is that right?”
MIT and NHS have ready-to-use handouts you can link/download. MIT Open Learning Library+2edX+2
D) Film/VOD review: The Data → Meaning separation
Use a two-pass review:
Pass 1 (Data only): Time-stamp objective events (locations, timings, comms verbatim).
Pass 2 (Inferences): Add possible causes/meanings; tag each with “confidence: high/med/low.”
Pair with a quick assumption test: state the data, then your story, and ask the athlete to confirm/adjust (Schwarz’s method). Schwarz Associates
E) Conflict & pressure moments: The De-escalation Ladder
When emotion spikes (tilt after a throw, parent confrontation, staff disagreement), use Senge/Schwarz guidance to pause and walk down the ladder in the moment:
“What did we each see/hear?”
“What did we notice or filter out?”
“What meaning did we add?”
“Which assumptions can we test right now?”
Example: A Soccer Coach & a Late Rotation
Scenario
On an important match day for a soccer team, the coach observes that the defensive unit reacts late to a counter-attack and concedes just before half-time. The coach reacts in the break and then during the next training builds a drill and gives a sharp directive.
Mapping the Ladder
Observable data: At minute 43 the opponent broke with three attackers, our defensive line was caught high, second-man left uncovered, score 0-1 at halftime.
Selected data: The coach focuses on the left-centre back drifting up, the left wing-back staying wide and not tracking, and the defensive midfield not dropping to cover.
Meaning added: The coach interprets this as “the left side defence lost focus” and “they aren’t committed to the team plan”.
Assumption: “That left-centre back thinks he’s above the plan, he doesn’t show full urgency” or “the wing-back doesn’t care about defensive duties”.
Conclusion: “We have a culture problem on the left side. If this continues, we’ll lose more matches this way.”
Belief: “Players on the left aren’t bought in; they will always leave space. I can’t trust that side to execute.”
Action: Coach gives a directive in training: “Left-side defenders you must check in to X-space immediately when we lose possession. No exceptions. Today we drill 10 × transition left side at high tempo.”
What happens next (and what could’ve been done differently)
What happens: The players feel they’re being blamed; the wing-back responds with “But I had pushed high as planned”; the centre-back says “I was closing down the ball, the midfielder should have helped me”. The drill runs, but players are defensive and the next match they still make a similar error. The coach reinforces harder.
What could be done: Instead of jumping to assumptions and directive, the coach pauses and uses inquiry: “In that move at 43’, what did you each see? What were you thinking?” Then the coach asks: “What triggered you to stay high/what prevented you from shifting left? How do you think we could adjust our trap so the left side doesn’t get exposed again?” This way the coach stays on the lower rungs (data, meaning) before assuming intent or culture.
Why the ladder matters
By climbing quickly, the coach moved from data → meaning → assumption → conclusion → action. The risk: missing alternate explanations (midfielder stepped up too late; opposing coach set a clever trap; fatigue from wing-back’s previous run) and negatively influencing player trust and buy-in. By pulling athletes into the inquiry process, the coach builds shared reality and joint agency in solving the problem.
Final thought
The ladder isn’t about being less decisive, it’s about being decisive on the right rung. In both sport and esports, where milliseconds and morale matter, coaches who can surface data, name their stories, and test assumptions in the moment build faster learning loops, stronger trust, and more resilient performance cultures.