Week 13 · lesson

Evidence Before Opinion

Review is where many teams lose discipline. Players remember the loudest moment, the final mistake, or the scoreboard. Evidence-based review slows the team down and asks what can actually be observed.

Claim Versus Evidence

A claim says what someone thinks happened. Evidence shows why the claim is reasonable. "We lost because our comms were bad" is a claim. "At 3:20 three players spoke over the objective caller, and the rotate call was missed" is evidence.

Worked Example

A team blames a missed shot for a lost round. The review shows the team entered without information, used no fallback call, and left the objective uncovered. The missed shot happened last, but it was not the root cause. The better claim is: "The round failed because our entry decision had no information rule."

Artifact: Claim Repair

Write three review claims. For each, add the evidence that would be needed to prove it. If the evidence is missing, rewrite the claim as a question.

Common Failure

Do not use review to rank teammates. Use it to find repeatable decisions the team can improve.

Check

A review claim is ready only when it points to an observable moment, not a personality judgment.

process flow

Week 13: Evidence to Improvement

  1. Observe

    Read the supplied scenario or record.

  2. Interpret

    Separate evidence from assumption.

  3. Practice

    Use a team artifact.

  4. Apply

    Make one reasoned choice.

  5. Review

    Record an inclusive improvement.

Read this concept flow as plain text
  1. Observe. Read the supplied scenario or record.
  2. Interpret. Separate evidence from assumption.
  3. Practice. Use a team artifact.
  4. Apply. Make one reasoned choice.
  5. Review. Record an inclusive improvement.