A passage plan may be technically sound and still be wrong for the conditions. The route,
vessel, and crew may all be capable, but timing matters. Leaving because the calendar says
it is time can turn an ordinary passage into an unnecessary struggle.

Organizations make the same mistake when they treat schedules as fixed while readiness,
capacity, leadership attention, and external conditions continue to change.

The Calendar Is Not the Weather

Sailors sometimes describe the calendar as one of the most dangerous pieces of equipment
aboard a boat. The danger is not the calendar itself. It is the pressure to depart, arrive,
or continue according to a date that was chosen before the conditions were known.

Organizational plans create similar pressure. A project may be expected to begin because:

• funding has been approved;
• a contract has been signed;
• a leadership commitment has been announced;
• a vendor is available;
• a fiscal deadline is approaching; or
• the schedule says the next phase should start.

None of these conditions demonstrates that the organization is ready to proceed.

Readiness Is Part of the Plan

Readiness is often treated as something that will emerge after implementation begins.
Ownership will be clarified later. Requirements will become apparent during configuration.
Data problems will be resolved during migration. Staff will find time to participate once
the project is underway.

This approach substitutes optimism for preparation.

A useful readiness assessment considers whether:

• the problem and intended outcome are understood;
• the people who own the work can participate;
• key definitions and requirements are sufficiently clear;
• dependencies and constraints are visible;
• leadership will resolve issues when they arise; and
• the organization can absorb the change alongside its other obligations.

The objective is not to eliminate every uncertainty. It is to understand the conditions
well enough to choose a reasonable course.

Wait for a Window

Waiting for better conditions is not the same as avoiding action. A vessel waiting for a
weather window is still preparing. The crew checks systems, studies forecasts, adjusts the
route, provisions the boat, and identifies alternatives.

Organizations can use the same period productively. Before launching a major initiative,
they can clarify ownership, examine source information, test a small workflow, document
assumptions, or resolve a critical dependency.

The work done while waiting may shorten the eventual passage and reduce the likelihood of
having to turn back.

Conditions Change Underway

Even a well-chosen weather window does not guarantee that conditions will remain favourable.
Forecasts change. Systems behave differently than expected. Staffing shifts. New information
emerges.

A plan should therefore include opportunities to reassess. These are not merely status
meetings. They are points at which the organization asks whether the original assumptions
still hold and whether the intended course remains appropriate.

Changing course in response to evidence is not a failure of planning. Continuing blindly
because the plan was approved is.

Know When to Heave-To

Sometimes the safest action is to pause without abandoning the passage. Heaving-to creates
time to restore order, examine the situation, and decide what should happen next.

A project may need the same deliberate pause when:

• the intended outcome is no longer clear;
• critical participants are unavailable;
• new risks have appeared;
• the solution is advancing faster than organizational understanding; or
• activity is continuing without meaningful progress.

The pause should have a purpose, a defined question, and a clear basis for resuming. Used
well, it protects the objective rather than delaying it.

A schedule describes the intended passage. It does not overrule the conditions.