Key Principle
Six pre-agreed behavioral norms prevent the most common team dysfunction patterns under time pressure. When those norms fail to unstick progress, the Hint Request Escalation Ladder provides five graduated levels of help-seeking that preserve maximum solving agency. The Five-Minute Rule sets an objective threshold: no progress after five minutes means hand it off or request a hint. (Ch. 21, Ch. 22)
Why This Matters
Without communication rules, a room full of smart individuals becomes a collection of parallel solvers who duplicate work, miss cross-clue connections, and frustrate each other. Without a hint strategy, teams default to either "never ask" (ego) or "just tell us" (impatience), both of which degrade the experience. "That's really the biggest advantage enthusiasts have over newcomers: we know how to work with each other, and we know what to expect in the room." (Errol Elumir, Ch. 21)
Good Examples
Six Rules of Communication: (1) Be nice -- stress causes snapping; morale damage compounds. (2) Check in, don't hover -- hovering signals distrust. (3) Call out findings -- announce discoveries immediately. (4) Constantly assess -- track what has been used and what remains. (5) Double-check -- have multiple eyes on searched areas. (6) Hand it off -- pass unused information to teammates; let someone else try when stuck. (Ch. 21)
Hint Escalation Ladder: (1) "Can you confirm this information is correct?" -- validates a hypothesis. (2) "Can you give us a nudge in the right direction?" -- directional guidance. (3) "Have we missed something important?" -- combats tunnel vision. (4) "Help, we need a hint!" -- general request. (5) "Can we please have the answer?" -- last resort. (Ch. 22)
The Thing Table: A designated central surface for all found items. This is the physical infrastructure that makes Rule 3 (call out findings) and EGAT's Gather phase work. Without centralization, information is distributed across pockets, shelves, and corners. (Ch. 21)
Counterpoints
Hint Stigma: Hints are not failure -- they are a designed part of the experience that bridges the gap between puzzle design and player interpretation. "Hints exist to bridge the gap between the puzzle's design and the player's ability to interpret it." (Ch. 22)
Hovering as Help: Checking in on a teammate is constructive; hovering over their shoulder signals distrust and triggers defensiveness, which reduces information sharing. (Ch. 21)
Waiting Too Long: Under time pressure, ego is the most expensive resource leak. A player who fails at a task twice and keeps trying wastes more time than admitting "this isn't my strength" and pivoting. (Ch. 21)
Key Quotes
"That's really the biggest advantage enthusiasts have over newcomers: we know how to work with each other, and we know what to expect in the room." -- Errol Elumir, Chapter 21
"Hints exist to bridge the gap between the puzzle's design and the player's ability to interpret it." -- L.E. Hall, Chapter 22
"The key question to answer is, are you having fun?" -- L.E. Hall, Chapter 22
"Nine times out of ten, a player is actually pretty close to the solution, and their thought process just needs a little tweaking." -- L.E. Hall, Chapter 14
Rules of Thumb
- Five-minute rule: no progress after five minutes = hand off or hint
- Pre-agree on hint strategy before entering the room to prevent mid-game arguments
- Start with the most agency-preserving hint level and escalate only as needed
- A hint that confirms your code is correct but not working gives meta-information: wrong entry point, broken lock, or misidentified endpoint (Ch. 22)
- Establish a Thing Table at the start of every game
- When the answer to "are you having fun?" is no, ask for help immediately
- Strength-based delegation: willingness to say "I can't do this part" is itself a communication skill (Ch. 21)
Related References
- Core Framework: Communication Over Cleverness - Why communication is the multiplier
- Team Dynamics and Player Archetypes - Role-based solutions to communication breakdowns
- EGAT Solving System - The Gather phase that the Thing Table supports
- Common Mistakes and Red Herrings - GM perspective on when to ask for help