The chart table is where the navigator brings together information from different sources.
Charts show the known hazards and established routes. Bearings indicate position. Weather
forecasts describe changing conditions. Logs record what has already occurred.

None of these sources determines the course by itself. They must be interpreted together,
with an understanding of their age, accuracy, purpose, and limitations.

Organizations need a similar place where evidence can be examined before action is taken.
The Chart Table is not a particular room, system, dashboard, or governance committee. It is
the shared discipline of making the basis for a decision visible.

Begin with the Question

Organizations often begin at the wrong end of the problem. They ask what data is available,
which reports already exist, or what a new platform can display.

This produces a familiar bottom-up search for relevance. Information is assembled first,
while the decision it is meant to support remains unclear.

A useful chart table begins with a more disciplined set of questions:

• What are we trying to understand or decide?
• Why does the question matter now?
• Who is responsible for acting on the answer?
• What evidence would materially affect the choice?
• How much confidence is required?
• When must the decision be made?

These questions define the information requirement. They prevent the available data from
quietly determining which questions the organization is willing to ask.

Put the Evidence on the Table

Decision-makers rarely suffer from a complete absence of information. More often, relevant
evidence is distributed across systems, reports, documents, spreadsheets, professional
judgment, and institutional memory.

Bringing the evidence together may require:

• operational and performance data;
• financial and capital information;
• regulatory obligations and engineering standards;
• asset condition and risk assessments;
• process maps and system architecture;
• staff experience and local knowledge;
• previous decisions and lessons learned; and
• external conditions that may affect timing or feasibility.

The objective is not to collect everything that might be relevant. It is to assemble enough
evidence to distinguish a defensible course from an attractive assumption.

Know the Source

A chart is useful partly because it identifies its scale, survey basis, publication date,
and intended purpose. Without that context, apparent precision can be misleading.

Organizational information needs comparable context. Important measures should be accompanied
by enough metadata to answer practical questions:

• Where did the information originate?
• How was it calculated or transformed?
• Which definition was applied?
• What period does it represent?
• Who is responsible for maintaining it?
• What quality checks have been performed?
• What known limitations or exceptions remain?

This context does not make the information perfect. It allows people to use it with an
appropriate level of confidence.

Separate Observation from Assumption

Charts contain surveyed information. Passage plans also contain assumptions about weather,
vessel speed, crew endurance, and future conditions. Confusing one with the other creates
false certainty.

Organizational discussions routinely mix several kinds of statements:

• verified facts;
• estimates derived from incomplete evidence;
• professional judgments;
• forecasts about future conditions;
• constraints accepted for planning purposes; and
• preferences presented as though they were requirements.

Each may be useful, but each should be identified for what it is.

A simple assumption log can record the statement, its basis, its owner, the consequence if
it proves wrong, and the point at which it should be revisited.

Make Definitions Visible

Many disagreements that appear to concern numbers are actually disagreements about meaning.
Two groups may report different results because they define the population, time period,
asset, customer, project, or completion status differently.

A shared definition should clarify:

• the term or measure;
• its intended business meaning;
• what is included and excluded;
• the calculation or decision rule;
• the authoritative source;
• the responsible owner; and
• the contexts in which the definition applies.

Agreement does not require forcing every part of the organization to use one definition for
every purpose. It requires making the differences explicit enough that results are not
compared as though they mean the same thing.

Trace the Lineage

A plotted position is more trustworthy when the observations used to establish it can be
traced. Organizational measures need the same transparency.

Data lineage describes the path from the original source through transformations,
adjustments, calculations, and reports. It helps explain:

• where an error may have entered;
• which systems and processes affect the result;
• how frequently the information is refreshed;
• where manual intervention occurs;
• which downstream reports depend on the same source; and
• what must change when a definition or system changes.

Lineage does not need to document every technical detail. It should be detailed enough to
explain how the evidence came to be and where its reliability depends on human or system
controls.

Apply Quality Control Where Consequences Are Highest

Not every data element requires the same degree of scrutiny. The level of review should
reflect how the information will be used and the consequence of being wrong.

Quality assurance establishes repeatable processes for producing and maintaining reliable
information. Quality control checks whether particular outputs meet the required standard.

A proportionate approach may include:

• automated completeness and validity checks;
• reconciliation with authoritative records;
• comparison with prior periods and expected ranges;
• review of high-impact assumptions and calculations;
• sampling of records and transformations;
• subject-matter review of unusual results; and
• documented resolution of exceptions.

The purpose is not to declare all information universally accurate. It is to establish
whether it is sufficiently reliable for the question on the table.

Show the Options

A chart table supports navigation because it permits more than one route to be considered.
Organizational decisions should also make the available options visible.

The meaningful choices may include:

• proceeding now or waiting for better conditions;
• repairing an existing capability or replacing it;
• addressing the entire problem or beginning with one bounded workflow;
• automating the current process or redesigning it first;
• accepting a known risk or investing to reduce it;
• building internally, purchasing a product, or combining both; and
• continuing the initiative, changing its course, or stopping it.

A credible comparison includes the expected value, cost, timing, dependencies, risks,
reversibility, and capacity required for each option.

The purpose is not to create an artificial score that makes the decision appear objective.
It is to expose the tradeoffs that judgment must resolve.

Record the Decision and Its Basis

Organizations often record what was decided without preserving why. Months later, the
original evidence and constraints are forgotten, making a reasonable decision appear
arbitrary or an outdated decision appear permanent.

A concise decision record should capture:

• the question considered;
• the decision made;
• the accountable decision-maker;
• the principal evidence and assumptions;
• the alternatives considered;
• the important tradeoffs and risks accepted;
• the actions and owners that follow; and
• the conditions that would trigger reconsideration.

This creates continuity without requiring future leaders to agree automatically with the
original choice.

Keep the Table Shared

A decision process becomes fragile when each group works from a different chart. Operations,
engineering, finance, technology, and leadership may each possess part of the necessary
evidence while interpreting the situation through different priorities.

A shared chart table does not mean every participant needs access to every technical detail.
It means the essential evidence, definitions, assumptions, options, and decision rights are
visible enough to support a common understanding.

This shared view helps participants distinguish between:

• disagreement about the evidence;
• disagreement about the assumptions;
• different assessments of risk;
• different organizational priorities; and
• a decision that belongs to a specific accountable role.

Making these differences explicit is more useful than forcing premature consensus.

Update the Chart

Information loses value when it is separated from the process that keeps it current.
Dashboards, dictionaries, inventories, lineage diagrams, and decision registers all begin
to age as soon as they are created.

Each important artifact therefore needs:

• a defined owner;
• a source and refresh method;
• a review frequency;
• a process for correcting issues;
• a record of material changes; and
• a clear purpose that justifies its continued maintenance.

The chart table should evolve with the passage. Otherwise, it becomes another collection of
documents describing waters that no longer exist.

A defensible decision makes its question, evidence, assumptions, and tradeoffs visible.