Clear and Constructive Messages

Short is not always clear.

"He is there" is brief but ambiguous.

Under pressure, teammates should not decode riddles.

Structure for fast calls

Useful baseline:

What + Where + Action or Status

Examples:

• Two left, pushing.
• Objective open, rotate back.
• Ten seconds, hold.

Context can compress messages, but only when vocabulary is shared.

Shared vocabulary problem

If one location has five names, interpretation slows down.

Consistency creates speed.

Teams should define and practice terms, not assume them.

Constructive means useful, not decorative

Compare:

• Why do you keep pushing alone?
• We split when you push before the call. Wait for team next push.

Second version gives observation, impact, and next action.

Timing and channel

During live action: short, current, actionable.

Between rounds: concise adjustment.

Post-match: detailed analysis.

Text chat is persistent but easy to misread under frustration.

Voice is fast but can overload.

Pings are fast but narrow.

Choose channel by job.

Message Lab

For each message:

1. Identify purpose.
2. Identify problem.
3. Rewrite.
4. Choose channel.
5. Choose timing.

Messages:

• Over there.
• Why did you do that?
• Nice.
• They are on the left side behind the wall moving toward where we were.
• Stop pushing.
• You never listen.
• Reset.

Closed-loop challenge

Decide which should be message-only and which require acknowledgment:

• Nice shot.
• Switch roles next round.
• Reset now.
• Match starts at 4.
• I need backup.
• Equipment check complete.

Defend your choices.

Compression tradeoff

Compression increases speed but raises training demand.

Code words only work if the team shares the code.

Build three standard calls

Create one threat call, one team-decision call, and one reset call.

For each include:

Message
Meaning
Who can say it
Acknowledge required?
Expected action

Exit ticket

Rewrite: You need to communicate better.

Your rewrite must include:

1. observable problem
2. why it matters
3. next action

Then write one live match call using What, Where, Action.

Source note

This lesson substantially adapts Learn with League material from Teamwork, Positive Attitude, and Respect on clear communication under pressure, non-judgmental strategy talk, and avoiding rushed-frustrated message failure.

The call-structure model, channel selector, compression tradeoff, closed-loop challenge, and Message Lab are original Robotnix Academy components.