A capable vessel does not navigate itself. People observe conditions, interpret information,
maintain equipment, make judgments, and respond when the passage does not unfold as planned.

Organizations depend on the same human capability. Systems can automate tasks and models can
suggest answers, but people still define the problem, weigh consequences, resolve exceptions,
and accept responsibility for the course taken.

The strength of the crew lies not only in individual expertise, but in whether people can work
together with sufficient knowledge, authority, and trust.

Names on the Crew List

Projects usually begin by identifying sponsors, owners, subject-matter experts, technical
leads, and stakeholders. The resulting list may look complete while leaving the practical
roles unresolved.

A title does not establish:

• who understands how the work is actually performed;
• who can make binding decisions;
• who will resolve disagreements between departments;
• who is responsible for the quality of the information;
• who will maintain the result after implementation; or
• who will be accountable when the intended outcome is not achieved.

A useful crew list describes the contribution and authority required from each role, not merely
the names of people expected to attend meetings.

Responsibility Needs Authority

Organizations frequently assign responsibility without providing the authority needed to carry
it. A data owner may be expected to improve quality but lack influence over the systems and
processes that create the data. A project manager may be responsible for delivery but unable to
secure the participation of critical staff.

This creates accountability in name while leaving the underlying decisions unresolved.

For each important outcome, it should be clear:

• who recommends a course;
• who provides operational and technical evidence;
• who makes the decision;
• who performs the work;
• who accepts the resulting risk; and
• who maintains the capability afterward.

These roles may be shared, but they should not be assumed.

Include the People Who Do the Work

The people closest to daily operations often understand conditions that are invisible in
policies, system diagrams, and management reports. They know which exceptions occur, which
information can be trusted, and which workarounds keep the process functioning.

Their participation is essential when defining requirements, evaluating options, testing
changes, and determining whether a proposed approach will work in practice.

Involvement should be meaningful. Asking staff to validate a nearly completed solution is not
the same as giving them a role in shaping it.

Do Not Rely on a Single Hand

Critical knowledge often becomes concentrated in one person. That person may know how to
correct the report, reconcile conflicting records, restart the interface, interpret an unusual
result, or navigate an undocumented approval process.

This expertise is valuable, but dependence on one individual creates operational risk.

The answer is not to replace expertise with documentation. It is to reduce unnecessary
dependence through:

• cross-training and shadowing;
• documented definitions and decision rules;
• recorded exception-handling procedures;
• shared access to tools and information;
• peer review of critical work; and
• planned succession for essential roles.

A resilient crew preserves specialized knowledge while ensuring the passage does not depend
on one person remaining continuously available.

Participation Has a Cost

Projects often treat staff participation as though it were freely available. Workshops,
reviews, testing, data preparation, training, and implementation support are added to existing
responsibilities without reducing other obligations.

The result is predictable. Decisions are delayed, reviews become superficial, and the people
with the most relevant knowledge have the least time to contribute.

A credible plan accounts for the real cost of participation. It identifies when key people are
needed, what they must contribute, and which other work may need to pause or shift.

Build a Common Language

Different members of the crew may use the same words to mean different things. Terms such as
customer, asset, project, risk, completion, and compliance can vary across operational,
financial, engineering, and technology contexts.

These differences are not merely semantic. They affect requirements, calculations, system
design, accountability, and the interpretation of results.

A common language develops through practical agreement on:

• the outcome being pursued;
• the meaning of critical terms and measures;
• the boundaries of the process;
• the assumptions being made;
• the evidence that will be accepted; and
• the conditions under which a decision will be revisited.

The objective is not to eliminate professional differences. It is to make them visible enough
that the crew can coordinate its actions.

Make Disagreement Useful

A crew that never disagrees may not be examining the conditions closely enough. Operations,
engineering, finance, technology, and leadership view the passage from different positions.
Those perspectives can reveal risks that would otherwise remain hidden.

Disagreement becomes useful when it is tied to evidence, assumptions, consequences, and
decision authority. It becomes destructive when important conflicts remain implicit or are
repeated without a clear means of resolution.

Good governance does not prevent disagreement. It gives the organization a disciplined way
to work through it.

Prepare the Crew for What Follows

Training is often scheduled near the end of implementation, after the important choices have
already been made. By then, the focus is usually on operating the new system rather than
understanding the new responsibilities and ways of working.

Preparation should begin earlier. People need opportunities to understand the intended
outcome, participate in design, test assumptions, practise new workflows, and see how their
role will change.

Adoption is more likely when the crew recognizes the course, understands why it was chosen,
and has helped prepare the vessel for it.

A crew is ready when responsibility, knowledge, and authority can meet at the point of action.