The Slope Nobody Mentions: Authority Gradient and Why Juniors Hedge

What It Is

Every ship has a chain of command, and it has to. The authority gradient is the unspoken slope of it: how steep it feels between the person who sees a problem and the person who can fix it. Where it is too steep, a junior who sees something wrong hesitates, hints, or says nothing. Where it is too flat, nobody is clearly in charge and decisions drift. Good bridge teams aim for a gradient steep enough that command is clear and shallow enough that anyone can speak.

The research word for the hesitation is hedging: ‘Do you think maybe we might want to…?’ instead of ‘Captain, that is not the right track.’ Hedged language is easy to miss, easy to wave off, and easy to regret.

Where It Shows Up In Real Cases

• El Faro, 2015. The NTSB case tags Authority Gradient and Hedging Language. Mates raised their concerns about the storm; the Captain held course on a forecast that was about twelve hours old. All 33 crew died.
• Costa Concordia, 2012. An unauthorised close approach that had not been properly charted, risk-assessed or briefed to the whole bridge team. Authority Gradient is one of the tags on our case.
• Jabal Hafit / Nirali, 2025. At 2234 someone saw the danger. At 2246 it was too late. Authority Gradient sits beside Normalisation of Deviance and Confirmation Bias in our analysis of that case.
• Tenerife, 1977. The best-known aviation example. The KLM flight engineer questioned whether the Pan Am aircraft was clear of the runway, and the captain answered emphatically that it was. 583 people died. Aviation took crew resource management from this lesson, and BRM took it from aviation.
• A positive case: IMCA SF 24/20. A Master challenged a sailing order that conflicted with dangerous goods rules. The client rejected it, the Master escalated, and company management backed him fully. The gradient worked because the company had made clear in advance that he could.

What Steepens It

• Rank, age and reputation: ‘he has done this for thirty years.’
• Culture and language differences, where challenging a senior is rude or hard to phrase in a second language.
• A leader who reacts badly to questions, once.
• Time pressure and commercial pressure.
• A brief that tells the team the plan and never asks what they think of it.

What Flattens It Safely

1. Ask for challenge in the brief. ‘If you think I am wrong, tell me. If I say I know, tell me again.’ This is the cheapest thing a Master can do.
2. Say it with facts. ‘The CPA is 0.017 miles and closing’ is easier to hear than ‘I am a bit worried.’
3. Use the graded model. PACE: Probe, Alert, Challenge, Emergency. Start with a question, move up one level at a time, and go straight to the top when time has run out. See our PACE guide.
4. Close the loop. The senior repeats back what they heard and what they will do about it.
5. Back the junior afterwards. Nothing steepens a gradient faster than a junior who spoke up being criticised.

The Other Direction

It can also be too flat. If everyone has an equal say in every decision, a fast manoeuvre goes nowhere. Command exists so that one person decides when it counts. The aim is a Master whom everyone feels able to challenge, and who decides.

Test Your Knowledge

Think you've got this covered? Put it to the test in Crew Connect's free Knowledge Checker — try a quick leadership round and see how you score.

Related Reading

• PACE: the escalation framework behind challenge and response
• Bridge resource management in six short modules
• Who can say stop?