Every week, the same work waits for the same person.

A proposal sits in draft until they can inspect it. A customer exception pauses in a private message. A team brings three reasonable options to a meeting, then postpones the choice because the one person trusted to see the hidden risk is not there.

That person may be exceptional. The operating pattern is not.

They know which request is routine and which one is a warning. They remember why a seemingly arbitrary constraint exists. They can hear the difference between a customer asking for a feature and a customer revealing that the operating model is broken. But when all of that judgment lives in their calendar and memory, the organization can use it only by interrupting them.

Exceptional people do not scale through availability. Their expertise can scale only when the organization makes its structure usable.

That structure is richer than documentation.

Most documentation captures conclusions: the approved policy, the current process, the final architecture, the sales playbook. Expertise also includes the conditions around a conclusion. What evidence changed the decision? Which alternative was rejected, and why? Where does the rule stop applying? What should happen when two trusted sources disagree? Which choices require a named person because the consequence is too material to delegate?

Without those boundaries, a knowledge base can make an organization sound consistent while leaving its judgment inaccessible.

Make the expert’s judgment usable as an operating interface.

  • the source of truth the expert relies on;
  • the decision the work requires;
  • the evidence that supports it;
  • the boundaries and exceptions that limit it; and
  • the person who owns escalation when the system reaches those limits.

Together, those elements make expert reasoning legible while preserving uncertainty and accountability.

An illustrative decision

The expert does not begin with the deadline. They notice that the request would change the order of two dependent steps and that the customer's named approver has not signed off. Those details turn an apparently simple scheduling favor into a decision about rework and authority.

The evidence changes the judgment. The current implementation plan shows the dependency. The approval record shows who may accept the resulting risk. A prior exception looks similar, but its approval came from a different role and therefore cannot simply be copied.

What can be reused next time is the shape of the decision: check the dependency, identify the authorized approver, compare the exception with prior cases, and record why the default sequence is being changed. What must escalate is the actual acceptance of material delivery risk. The system may assemble the evidence and draft the options; the accountable person decides.

If the customer later corrects the deadline or the expert finds that the two steps are not dependent, the record changes too. The new evidence is attached to the decision, the earlier rationale is marked as superseded rather than silently erased, and the reusable instruction is updated. Correction is part of the expertise, not a cleanup step after it.

Fluency creates the failure mode: it can carry the answer into the next draft, workflow, or software change while dropping the exception or authority that made the answer valid. Controlled reuse keeps the source and boundary attached, lets the system handle work inside explicit limits, and returns consequential or ambiguous decisions to a person.

This changes the role of an exceptional person.

Instead of answering the same class of question repeatedly, the expert defines how that class of question should be handled. Instead of being the hidden dependency, they become the designer of the interface: naming the controlling sources, exposing the decision logic, marking the exceptions, and deciding where authority ends.

The organization still depends on the expertise; it no longer depends on the expert’s constant presence.

Book a 30-minute interview with the expert and bring one recently completed decision—not a blank template and not a request to explain everything they know.

Walk through the evidence in the order it appeared. Pause whenever the expert says “it depends,” rejects an apparently reasonable option, or reaches for a source. Capture the answers in the working record:

  1. What did the expert notice that others missed?
  2. Which evidence changed their judgment?
  3. Which parts of the reasoning can be reused next time?
  4. Which decision must still escalate, and to whom?
  5. If new evidence proves this answer wrong, how will the correction update both the record and the reusable instruction?

Before the interview ends, play the captured model back to the expert using a new example. Mark what held, what broke, and what needs a clearer boundary. Then put the record where the next person doing the work can actually use it.

Test the next decision, not the imitation: can it move with the expert’s reusable reasoning, stop at the right boundary, and get better when corrected?