No chart contains everything needed for a safe passage. It may show depths, hazards,
aids to navigation, and established routes, but it cannot fully describe how a place
behaves under every combination of wind, tide, traffic, and local practice.

Experienced mariners rely on local knowledge to fill those gaps. Organizations depend on
the same kind of knowledge, although they do not always recognize or preserve it.

The Organization Beyond the Org Chart

Formal structures describe who is responsible. Policies describe how work should occur.
System diagrams show how information is intended to move. Procedures establish approved
steps.

None of these necessarily explains how the organization actually functions.

Local knowledge reveals:

• who understands a process well enough to resolve exceptions;
• which data sources people trust and which they quietly avoid;
• where approvals routinely stall;
• which workarounds keep operations moving;
• which definitions vary between departments;
• what previous initiatives attempted and why they struggled; and
• which informal relationships make coordination possible.

This knowledge often determines whether a proposed change works in practice.

Find the People Who Know the Water

The people with the most useful knowledge are not always those with the highest titles or
the most formal authority. They may be operators, analysts, coordinators, administrators,
technicians, or long-serving staff who understand how systems, processes, and people
interact.

Their value is not simply that they remember the past. They can explain why the present
environment developed as it did, where the apparent rules have exceptions, and what might
happen if one part of the system changes.

They should be treated as participants in shaping the work, not merely as sources to be
interviewed and then left behind.

Listen for the Exceptions

Standard processes are usually easier to document than exceptions. Yet exceptions often
reveal the most important requirements.

Statements such as these deserve attention:

• “That is usually how it works, except when…”
• “The system says one thing, but operations uses…”
• “Only one person knows how to correct that.”
• “We tried that before, but…”
• “That report is official, although everyone uses this spreadsheet.”
• “The procedure changed, but the system never did.”

These are not distractions from the main process. They often identify where risk,
dependency, and practical knowledge are concentrated.

Do Not Mistake Documentation for Understanding

Documentation is valuable, but it is not a substitute for observing the work and speaking
with the people who perform it. A procedure may be accurate and still omit the judgment
required to apply it. A system diagram may be technically correct while failing to show
the manual steps that make the process reliable.

Understanding develops by comparing several perspectives:

• what the policy requires;
• what the system supports;
• what the process describes;
• what the data shows; and
• what people actually do.

The differences between these perspectives are often more informative than any one of them
on its own.

Preserve What Matters

Local knowledge becomes an organizational risk when it remains concentrated in a few
individuals. Retirement, turnover, reorganization, and outsourcing can remove critical
understanding with little warning.

The answer is not to document everything. It is to identify the knowledge whose loss would
make work slower, less reliable, or more dangerous.

That knowledge may be preserved through:

• decision and assumption logs;
• known-issue registers;
• data definitions and ownership records;
• exception-handling guidance;
• process walkthroughs;
• cross-training and shadowing; and
• regular review with the people who perform the work.

The objective is not to eliminate the need for experience. It is to prevent essential
experience from disappearing unnoticed.

Respect the Limits of the Chart

Frameworks, architectures, standards, and leading practices provide useful structure.
They help organizations compare options and avoid known mistakes. They do not remove the
need to understand the waters in which they will be applied.

A solution that succeeds elsewhere may fail locally because authority, capacity, history,
risk, and operational conditions are different. Effective practice adapts the chart to
the passage rather than forcing the passage to resemble the chart.

The chart shows the route. Local knowledge explains how the water behaves.