Leadership, HR & Resource Management

Every chief engineer eventually meets both failure modes of delegation in the same career, sometimes in the same week. The first is the one nobody warns you about until you have done it: taking the spanner off a competent second engineer because it is quicker to do the job yourself than to explain it, teach it, or wait for it. That is not efficient management, it is the absence of management — the department stops developing the moment the chief starts doing its work. The second failure is the opposite and more dangerous: handing a job over and treating your involvement as finished. It is not. Delegation moves the task; it never moves the responsibility. If the job goes wrong, the chief answers for it exactly as if he had done it himself, whether or not he was standing there.

What sits between those two failures is a specific, examinable sequence, and it is worth holding it in that order because each step depends on the one before it. First, a brief that is actually clear — not “sort out the purifier” but what, by when, and to what standard. Second, a genuine check of competence against the task, not assumed competence based on rank or time served. Third, a verification point chosen in advance, at the moment in the job where a mistake would still be cheap to catch — not a general “let me know how you get on.” Fourth, the authority, used without hesitation, to stop the job the moment the check fails. And fifth, a record, because a verification that leaves no trace did not, for examination purposes, happen.

Resource management is the bridge-team-management idea carried into the engine room, and it earns its place in the syllabus for a blunt reason: when an inquiry sits down after a serious engine room incident, the missing ingredient is almost never technical knowledge. Someone in the team usually knew, or half-knew, that something was wrong — a reading drifting, a noise that was not quite right, a nagging feeling about a job — and it did not reach the person who could act on it, or it reached them too late, or it was said too quietly to be heard over rank. The plant did not fail the crew; the crew's use of the information available to it failed.

Five things make up the practical content of the idea, and they are worth keeping separate because each fails in its own way. Situational awareness is simply knowing, continuously, what state the plant and the people are actually in — not what the last log entry said. Workload distribution means noticing when one person is task-saturated while another is idle, and moving work before the saturated one starts missing things. Prioritisation is choosing, under time pressure, which of several legitimate demands gets attended to first — usually safety before schedule, schedule before comfort. Communication is closing the loop: saying it, having it acknowledged, and checking the acknowledgement matched what was meant. Assertiveness is the hardest of the five to teach, because it asks a junior engineer to challenge a senior one's decision when the evidence in front of him says the decision is wrong — and it asks the senior one to have built a department where that challenge is welcomed rather than punished.

It is easy to treat the rest-hour rule as a piece of paperwork — a table to fill in so the PSC inspector has nothing to write up — and that is exactly the reading that gets a chief engineer into trouble. The rule exists because fatigue has a specific and dangerous shape: it degrades judgement before it degrades visible effort. A tired engineer does not look tired in the way a drunk one looks drunk. He still turns valves, still writes in the log, still answers when spoken to — what goes first is the quality of the decisions behind those actions: the borderline reading he decides not to chase up, the short-cut that seems reasonable at 03:00 and would not at 15:00, the alarm he silences a fraction too quickly because he has silenced forty false ones that week. None of that shows up until the one time it matters.

The structure of the rule follows directly from that mechanism. Rest has to come in blocks long enough to actually be restorative — hence the requirement that if it is split, one of the two pieces must be at least six hours, because a string of short naps does not recover judgement the way one solid block does. The 14-hour interval caps how long any single stretch of work-plus-short-break can run before real rest is forced. And the seven-day total catches the slow accumulation that a single compliant day can hide — a person can pass every 24-hour check individually and still be dangerously short over a week. Practically, this means a job that will breach the limits has to be planned differently — shared out, retimed, reassigned — before it starts, not managed afterwards by writing down something other than what happened. Falsifying a rest record is treated as a serious matter in its own right, entirely separate from the fatigue it was covering up, because it removes the one tool — an honest record — that lets anyone else catch the problem before it does.

A brief is not a courtesy extended to the team before a job; it is where most of the risk in that job actually gets found, and it costs minutes. Run properly, it answers six things in order: what we are about to do; why, so people understand the intent and not just the instruction; who is doing each part of it; what could reasonably go wrong, drawn from experience rather than a generic checklist; what stops the job if that happens; and how the team will talk to each other while it is running — who calls what, on what channel, in what language. Skipping the brief does not save the five or ten minutes it would have taken; it moves the cost to later, where finding out mid-job that two people assumed different isolation points is far more expensive than asking beforehand.

The debrief is the less-loved half of the pair, mostly because by the time a job finishes everyone wants to be somewhere else. It does not need to be long. It needs to ask two questions honestly: what actually happened, as distinct from what the plan said would happen, and what should change next time — in the procedure, the brief itself, or who does what. A brief with no debrief afterwards is just an instruction; it teaches the team nothing about itself. Over a career, the accumulated debriefs of routine jobs are where a department's actual working knowledge lives — more of it than in any manual.

Training and appraisal are frequently treated as the same activity wearing different paperwork, and separating them properly is worth the effort. Training builds a specific skill against a task — show, supervise, let go, check. Mentoring is broader and slower: helping a junior officer build judgement over months, mostly by talking through decisions after the fact rather than by demonstration. Appraisal is different again — a structured, periodic look at how someone is actually performing against what the role requires, evidenced rather than impressionistic, and it works best when nothing in it is a surprise, because the good and bad of it should already have been said as it happened.

All three depend on communication actually landing, and on a multinational crew that cannot be assumed. Working language is a safety requirement under the ISM Code, not a courtesy: everyone aboard needs to understand and be understood in it for the tasks they perform, and a chief engineer's job is to verify that comprehension rather than take fluency on trust. Spoken competence for routine orders and written competence for a log entry, a permit, or a standing order are not the same skill, and a gap between them is common and easy to miss until it matters. Cultural background affects more than vocabulary — some crew members come from traditions where questioning a senior officer's decision reads as disrespect rather than good practice, which is precisely the assertiveness that resource management depends on. Building a department where that challenge is safe to make, across those differences, is a deliberate and ongoing piece of leadership, not something that happens on its own because everyone is professional.

Under-performance is examinable because most of the marks are lost at the start, not the end. The instinct, especially for a chief who is busy, is to let a small lapse go once, then twice, then address it in the moment it happens — often on the spot, sometimes in front of others, usually generally rather than specifically. That approach converts a coachable problem into a personal one. The correct sequence is to establish the facts first — what actually happened, on which occasions, against what standard — then decide whether the cause is capability or conduct, because the two need different responses: a skills gap needs training, an attitude problem needs a different conversation entirely. The conversation itself should be private, early rather than after it has become a pattern, specific about the evidence rather than a general impression of underperformance, and closed with a clear expectation and a timescale to review it. It is then recorded, not as a threat but so that if it does escalate, the escalation follows the company's procedure on facts that were captured at the time rather than reconstructed from memory later.

Conflict between crew members and decision-making under pressure share a common thread: neither waits for complete information. A chief engineer who insists on certainty before acting in an engine room emergency will act too late; the skill being tested is making the best call available on the evidence in hand, saying explicitly what is assumed versus known, and being willing to revise the call the moment better information arrives — rather than defending the first decision out of pride. That same willingness to revise, applied to people rather than plant, is what keeps a conflict between two crew members from calcifying into something neither side will back down from.

Both examples below are scenario-judgement walkthroughs of the kind asked orally in the examination room: a realistic situation, the facts as given, and the reasoning a candidate has to talk through out loud to reach a defensible decision — not a single formula, but a chain of judgement calls that has to hold together.