BRIEFING / WEEK 08
Get the Message Through
Coordinate across unequal information using questions, read-back and renewed confirmation when an instruction changes.
Read, then try it
This briefing explains the week's idea and shows a worked example. Read the objectives and example, then open the lab for the actual controls, three practice configurations and saved fieldwork record.
The week’s question: Two competent people hold different dispatch information. Establish a shared, acknowledged instruction before acting.
Both people are competent. Each has half the information.
What you will learn
- Identify missing action-critical information from the receiver’s position.
- Use questions and full read-back to resolve misunderstanding before action.
- Reconfirm changed instructions and distinguish solo practice from pair evidence.
The briefing
Unequal information creates the task
The analyst sees the source request. The operator controls dispatch and must establish destination, quantity and verification code. Keep the source card with the analyst during the first attempt. If everyone reads the same card, the task becomes copying rather than communication.
The receiver should identify missing information before asking. “Tell me everything” may work for a tiny card, but does not demonstrate deliberate coordination. Ask for the detail that changes the next action and explain why it matters.
Read-back tests shared understanding
The receiver repeats the instruction as an executable action. The sender compares every consequential field with the current source, then confirms or corrects it. “Okay” records receipt of a message without showing what was understood.
Preserve misunderstandings instead of tidying the record into a perfect conversation. Name the ambiguity and the clarification that resolved it. Uncertainty should become visible before action.
Confirmation has a scope
When a destination, quantity or code changes, the old confirmation no longer authorises the new instruction. Obtain a new read-back and record which version was acknowledged.
Swap roles in person. Online partners can reveal one role view at a time. Solo switching rehearses the method but cannot establish team communication. Written, spoken and assistive communication can meet the same accuracy standard without rewarding speed or theatrical style.
Worked example · a different scenario
In the separate example, the analyst requests Dome, five cases, VIOLET. The operator reads back four cases. That mismatch is kept in the record and corrected before confirmation. A later card requests Pool, two cases, SILVER, so the demonstrator repeats the complete read-back rather than reusing the first acknowledgement. The method transfers; the message itself changes.
Watch this separate example and inspect its finished record.
A plausible mistake
Repeating the same instruction more loudly does not fix different assumptions. Giving every available fact at once can also bury the condition that matters. Prioritise the next decision and confirm its essential constraints.
Supplied rule sheet
Where to find the named materials: These labels identify the supplied material on this page and in the combined campus pack; they are not separate files you need to locate. CO-01 is the analyst’s destination, quantity and code for the selected phase. CO-02 is the operator’s receiving task: record those fields, read them back and obtain confirmation. The campus pack explains how to keep the two role views separate.
- The analyst holds the authoritative destination, quantity and verification code. The operator must record and read back all three.
- Practice handoff: destination Relay; quantity 2; code AMBER.
- Skill check: destination Archive; quantity 3; code COPPER.
- Transfer: destination Dispatch; quantity 1; code IVORY.
- The handoff is complete only when the operator’s fields agree with the analyst card and acknowledgement is recorded.
- Role switching is explicit in solo mode; a team can divide the two information views.
Before the lab
Read only your assigned role pack first (10 minutes). Rewrite one vague everyday instruction using action/object/condition/confirmation (10 minutes). Solo students inspect packs in sequence and record what changed.
What happens next
A2 assesses a real handoff between partners. The final team uses this method when source findings, equipment conditions or responsibilities change another person’s work.
Keep handoff-agreement from this week’s lab. Download the campus pack.
SLOP UNIVERSITY · THE ACADEMY OF IMPOSSIBLE SKILLS
An original fictional course. Progress records practice, not academic certification.