Module 6: Team Diving and Human Factors

This module is different from the five before it. Modules 1–5 taught you geometry, optics, registration, and surface operations — the mechanics of producing a defensible underwater map. This module is about the humans who do that work, and the predictable ways human cognition and team dynamics fail under task load. Mapping is a high-task-load activity; the failure modes named here are the failure modes you will personally experience on Dives 1, 2, and 3.

This course follows the framing developed by Gareth Lock and the Human Factors Skills in Diving curriculum (“Under Pressure,” 2019; humanfactors.diving). Lock’s work, in turn, draws on decades of aviation Crew Resource Management research and on parallel work in medicine. The recreational diving community has been catching up over the last ten years. This course adopts that framing because mapping a site cleanly is exactly the kind of activity where good gear and good intentions are not enough.

Why “Team” and Not “Buddy”

Throughout this handbook we use “team” rather than “buddy.” The change is deliberate. A buddy is a companion — the person paired with you at the dive shop, watching you and being watched by you. A team is a working group with differentiated roles, shared accountability, and flat in-water decision authority. Buddy framing is symmetric: both members do the same job. Team framing is asymmetric by design: each member has a primary task, with overlapping responsibility for safety.

Your team is bigger than two divers. It includes the Surface Data Operator topside, who is watching the Fish Deeper app and the GPS lock and has the authority to call an abort. It includes the Surface Watch, who is protecting the float from boat traffic. Both topside roles are full team members. They are not your support staff; they are your team.

During your training, the instructor is a separate role outside the team — supervising, certifying, intervening when needed. After certification, you will dive this specialty without an instructor present. The procedures and habits this module builds are what make that safe.

Five Concepts You Will Use on Every Dive

1. Task Loading and Attention Narrowing

Human attention is finite. Under high task load, attention narrows onto the most salient task and the others are dropped. You will not notice the others being dropped — that is the point. The photographer concentrating on a 0.6-second shutter interval, frame composition, and orbit radius will, predictably, lose track of gas, depth, NDL, and the position of the Safety Diver. This is not a discipline failure; it is a cognitive default.

Your defenses: assigned roles (Photographer focuses on capture; Safety Diver focuses on gas/NDL/team awareness), explicit time and gas check intervals (quarter-turn checks during the orbit), and a willingness to stop the data run when attention has narrowed. The data is not worth a missed NDL ceiling.

2. Shared Mental Model and Closed-Loop Communication

Before descent, your team must agree on what the dive looks like: what success is, what abort looks like, who calls what, what the gas turn pressure is, what the planned depth is. This is the shared mental model. The pre-dive briefing is not bureaucracy. It is the moment when four separate mental models become one.

Closed-loop communication is how the team maintains that shared model under stress. When the Surface Data Operator signals “GPS lock,” the team acknowledges back: a confirming signal that says “heard.” When the instructor says “turn at 1500 PSI,” the diver repeats “turn at 1500.” This is how aviation has prevented misheard instructions for fifty years. It costs nothing. The alternative — “I thought you said 1500” / “I said 1800” — is a real conversation that has happened on real dives.

3. Plan Continuation Bias

Once a plan is in motion, humans rationalize continuing it even when the inputs change. You spent the morning loading gear. You drove to the site. You set up the sonar. You briefed. The wind picks up. The forecast worsens. The visibility drops. And you press on, because turning back feels like wasting the morning. This is plan continuation bias, sometimes called “press-on-itis,” and it kills divers.

Your defenses: name it in the briefing (“if conditions worsen, we turn around — nobody loses face for that”); set explicit go/no-go criteria before you arrive at the site; and recognize that the cognitive sting of an aborted dive lasts a few hours, while the consequences of pressing on can last a lifetime. Aborting is a skill, not a failure.

4. Speaking Up and Graded Assertiveness

When a junior team member sees something wrong, they need to be able to say so without hesitation. In hierarchical or socially uncomfortable situations they often will not. They will hint. They will hedge. The danger is most acute when the senior person is the one making the error. Aviation has lost crews because the first officer noticed something wrong and did not feel empowered to override the captain.

The technique is graded assertiveness: escalate clearly through stages. “I’m noticing the float is dragging.” “I’m concerned the float is submerging.” “We need to stop — the float is under.” “Stop the dive.” The grades give the senior person space to course-correct, while making escalation feel procedurally normal rather than personally confrontational. Practice this in briefings, not in emergencies.

5. Debriefing as Practice

After every dive, your team debriefs: what went well, what went wrong, what would we do differently. Most recreational divers have never been taught how to debrief. They think a debrief is when you tell stories at the dive shop. It is not.

A real debrief is short, structured, and focused on the system that allowed an error — not the person who made it. The phrase “just culture” captures this: errors are treated as information, not punishment. “I lost GPS lock for two minutes” should be received as data about the procedure, the equipment, or the conditions — not as a failing on the part of the Surface Data Operator. If your team punishes the person who reports an error, you will get fewer reports, not fewer errors.

This is how teams get better. It is also how you get better. Adopt the habit early.

After Certification

During this course, your instructor sits outside the team — verifying, supervising, intervening. After certification, you will work in teams of qualified divers without an instructor present. The procedures, the role differentiation, the closed-loop communication, the no-blame debrief — these become your responsibility to maintain. They are habits, not requirements. Treat them as habits and they will hold under pressure.

Self-Check

1. Your team is set up at the site. Wind has picked up since the morning forecast. You spent two hours driving here. What cognitive bias is most likely to affect the go/no-go decision, and what defense did you set up in the briefing?

2. Why is closed-loop communication (e.g., repeating back the turn pressure) more reliable than nodding?

3. You are the Safety Diver on Dive 2. The Photographer’s SPG just hit 1500 PSI but they are still adjusting the orbit. Apply graded assertiveness: write three escalating statements you could make.

4. After Dive 1, the Surface Data Operator reports losing GPS lock during the third lane. What is the right immediate team response in a just-culture framing, and what is the wrong one?

Answers

1. Plan continuation bias. The defense set up in the briefing should be explicit go/no-go criteria stated before arriving on site, plus an explicit norm that aborting carries no social cost. If you only decide whether to dive once you are already wet-suited up, sunk cost has already biased you.

2. Nodding tells the speaker that the listener acknowledges the message, but not that the listener understood it correctly. “Turn at 1500” → “Turn at 1500” catches the misheard “1800.” Nodding does not.

3. Possible escalations: (a) “I’m noticing we’re at 1500.” (b) “We’re at turn pressure now — we should wrap up.” (c) “Turn pressure. We’re ending the orbit.” Stage (a) gives the Photographer space; stage (c) is firm and not negotiable.

4. Right response: treat the GPS-loss report as information. Note when and where, document it for the surface interval, debrief whether the cause was wave action, antenna submersion, drag, or something else, and revise the procedure or the conditions for next time. Wrong response: any version of “why didn’t you tell us sooner” or “you should have been watching the screen” — those statements reduce future reporting without reducing future errors.

Generated from the Reef Cartographer Student Handbook, version 05.008. The course documents are the authority; if these pages and they ever disagree, the documents are right.