Conflict and Correction

Competitive teams will make mistakes. The question is whether correction improves the next attempt or damages trust. Good correction is specific, evidence-based, and directed at behavior.

Behavior, Evidence, Next Action

A useful correction has three parts: the behavior, the evidence, and the next action. "You never listen" is not useful. "On the last objective call, two players rotated before the caller confirmed. Next time wait for the rotate phrase" is useful.

Worked Example

After a loss, one player says another player threw the round. That claim is too broad and personal. The review lead pauses and asks for the observable moment. The team identifies that the actual issue was an early rotation before vision was confirmed.

The correction becomes a team rule: "No rotation call without location confirmation or caller override."

Repair Language

Use phrases like:

• "The decision failed because..."
• "The evidence we have is..."
• "The next version of the rule is..."

Avoid phrases that attack identity, skill, or effort.

Artifact: Correction Script

Write a correction script for one common esports mistake: over-committing, ignoring objective, unclear callout, early rotation, or tilting in comms.

Common Failure

Do not wait until everyone is angry to create norms. Correction rules should exist before conflict.

Check

If your correction can be followed by any teammate without embarrassment or confusion, it is probably usable.