FIREBREAK COMMAND

Saw It, Inferred It, Missed It: Three Labels for Better Game Feedback

← Crew journal

Gaming & Teamwork · Firebreak Command editorial

Make team discussions more precise by distinguishing visible information from interpretation.

Name the kind of information

Game discussions become confusing when observations and assumptions sound identical. Try three labels during a shared demo review: saw it, inferred it, and missed it. Saw it means the information was visibly present. Inferred it means the participant drew a conclusion from available clues. Missed it means the relevant information was not noticed at the time. These labels do not require special software or an in-game feature. They are a proposed discussion method for Firebreak Command community members reviewing material they can actually access.

Compare perspectives before judging

Suppose one viewer says a choice was obvious while another says the screen provided no guidance. Before arguing, ask each person to identify the exact cue they noticed or expected. AHRQ's TeamSTEPPS material distinguishes active situation monitoring from the resulting awareness and shared understanding. That health care framework offers a useful conceptual comparison, not proof that this exercise improves firefighting performance. A game group can use the distinction to ask whether members received different information, interpreted the same information differently, or simply focused on different parts of the presentation.

Turn disagreement into a testable question

Finish by writing one focused question for a future viewing: would a clearer label change the interpretation, or was the explanation already present but easy to overlook? Preserve both accounts until there is evidence to resolve them. Do not convert a missed cue into a judgment about intelligence, commitment, or professional competence. This remains communication practice around a demo, not department-approved instruction or certification. A useful discussion ends with a better description of uncertainty, even if the group never reaches a single preferred strategy or agrees that the interface needs changing.

Bring it to your crew

When players disagree about an obvious cue, what would help distinguish missing information from different interpretations?

Further reading: AHRQ TeamSTEPPS — Situation Monitoring: Explanation of Key Concepts and Tools ↗

Stay with the crew.

Subscribe for Firebreak Command articles, development updates and community news. Newsletter delivery has not started.

Member sign-in · Manage your account and newsletter preference