300 Officers, One Lesson: The Call That Never Gets Made Sinks Ships

More than 300 deck officers have passed through Enhanced Bridge Resource Management programs over the past three years, and the training's central finding is uncomfortable: technical competence alone does not prevent incidents. What happens in the seconds between an officer noticing a deviation and voicing it decides whether that competence is ever used.

The scenario the training industry uses to make the point is deliberately routine. A vessel approaches a berth. The bridge team has a passage plan, functioning equipment and experienced officers. One officer notices the ship setting closer to the edge of its planned track than expected. The master is engaged with the pilot. The officer hesitates.

No incident occurred. The illustrative example matters because it isolates a single question that extends far beyond one bridge: how quickly does a private observation become information the whole team can act on?

What separates a vague call from a useful one?

Trainers draw a hard line between two ways of speaking up. "Something doesn't look right" leaves the rest of the team to work out what has changed. "Our lateral movement is greater than planned; I recommend we verify our position before continuing" gives the team an observation, its significance and a proposed next step in one sentence.

The master's reply carries equal weight. "Show me what you're seeing" is a short invitation with an operational purpose — it keeps information flowing up the hierarchy rather than shutting it down.

The article's author, a human factors trainer, is blunt about the limits of classroom agreement: a junior officer may know they should challenge a decision yet still worry about interrupting the master. A master may sincerely welcome challenge yet close it down with an impatient first response. Nodding along in training tells you little about behavior under pressure.

Where does emotional intelligence belong on a bridge?

The author's claim — backed by the three-year, 300-officer program — is that communication, leadership and self-awareness "cannot be treated as optional additions to technical competence." They determine whether technical skill gets deployed when circumstances change.

This is not a call to replace command with committee. The master remains accountable. The stated aim is narrower: give the person in command the fullest available picture, so hierarchy supports the decision rather than obstructing the flow of information.

The problem extends past the bridge. A handover can omit a constraint because the giver assumes the receiving team already knows. A crew member can spot an abnormality yet struggle to raise it across rank or department. Shore management can create schedule pressure without intending to discourage a pause.

How would an operator know the training works?

Here the author concedes what many training providers do not: a completed course is evidence of attendance, not proof that behavior changed. The proposed evidence is behavioral. In a simulator exercise, an assessor notes when a deviation was detected, when it was voiced, how the message was acknowledged and whether the plan was revised.

An exercise that ends safely after a late observation is still valuable evidence, the author argues — it creates a chance to examine the hesitation without waiting for a poor outcome. Evaluation criteria must be concrete. "They communicated well" is dismissed as too vague to guide development; did the person describe the change, explain its operational implication, receive an acknowledgement and confirm the next action?

The same framework gives managers sharper post-incident questions: what information was available, who held it, when did it become shared, and what made the conversation harder? Blaming the last person in the chain, the author notes, rarely gives the organisation the whole picture.

What is not being claimed

To the author's credit, the promise is bounded. Emotional intelligence alone will not prevent incidents. Ships still need sound equipment, technical competence, procedures and effective oversight. The argument is that those investments depend on people connecting at the right moment — and that no poster declaring everyone has a voice ever strengthened one. If operators train technical skills thoroughly but leave these human capabilities to chance, the question is what critical information never reaches the people who need it.