The short answer.

When only one person knows how a piece of work is done, ask that person how they do it, write their method down as a workflow, and have them check every line. The expert stays the expert and becomes the named owner of the method. The team gains a way to do the work to the expert’s standard when the expert is on leave, promoted or retired.

Capture is a conversation, not surveillance. We ask people how the work is done; nothing records or monitors them. The workflow then runs in the ChatGPT, Claude, Copilot or Gemini your company already pays for: the workflow prepares the work, and a person decides.

Capture is an interview and a few worked cases.

Capturing one person’s know-how takes one structured interview and three to five real cases the expert walks through out loud. The interview gets the method as the expert describes it. The worked cases get the judgment the expert no longer notices they use.

Four things matter in every capture, and the interview asks about each one directly.

  • What they start from.The documents, messages, records and notes the expert opens first, and the order they open them in.
  • What they look for.The handful of facts the expert checks every time, and the signal that tells them a case is routine.
  • What they do when something is odd.The exceptions, the cases they send back, the people they call and the point where they stop and ask.
  • What they would never send.The mistakes the expert catches in other people’s work. These become the workflow’s checks.

Worked cases matter because experts describe the normal case and forget the hard ones. Ask the expert to talk through a recent awkward case from start to finish, and the rules nobody wrote down appear. The questions that turn expert judgment into a workflow goes further into the interview itself.

The expert becomes the owner of the method.

The expert whose know-how is captured becomes the owner of the workflow that holds it, by name. Capture honors the expert and spreads their standard: the workflow is their method, in their words, checked by them.

Owning the method means three things in practice.

  1. The expert approves the workflow before anyone uses it.They read the written method, run it on real cases and say what is wrong. Nothing goes to the team until the expert says it matches how the work should be done.
  2. The expert decides what changes.When a rule, a supplier or a customer changes, the expert updates the method or tells whoever maintains it.
  3. The expert reviews the hard cases.The workflow handles the routine and flags the odd. The odd cases still come to the person who knows them best.

From one person’s know-how to a method the whole team runs follows one method from the expert’s account to the version a colleague can run.

What happens when they are on leave, promoted or retired.

When the expert is away, a colleague runs the same workflow and gets the work prepared the expert’s way. The colleague still makes the decision, and the workflow shows them what the expert would check and when to stop and ask.

  • On leave.The work keeps moving. The colleague runs the workflow, and the cases it flags as odd wait for the expert or go to the person the expert named as backup.
  • Promoted.The expert keeps ownership of the method from their new role and stops doing every case by hand. Their standard now reaches more of the work, not less.
  • Retiring.Capture well before the last day, so the expert can check the workflow on real cases and hand ownership to a named successor while they are still there to answer questions.

The best time to capture is before any of these is on the calendar. Capture done in the last fortnight before a departure is rushed, and the hard cases get skipped.

Ten questions for the capture interview.

Copy these ten questions and use them in your next conversation with the person who holds the know-how. Ask them about a recent real case, not the work in general.

  1. What arrives that tells you this work needs doing?
  2. What do you open first, and what next?
  3. Which facts do you check every single time?
  4. How do you know a case is routine?
  5. What makes a case odd, and what do you do then?
  6. When do you stop and ask someone, and whom?
  7. What would you never send, and why?
  8. What mistakes do you catch in other people’s versions of this work?
  9. What does finished look like, and who receives it?
  10. Who should decide this when you are not here?

Write the answers down in the expert’s own words. Then pick three to five recent cases, including one awkward one, and ask the expert to walk through each with the same questions in mind.

One example.

Take a 110-person food manufacturer where one quality manager approves every new ingredient supplier. Nobody else knows which certificates she accepts, which she sends back, or which suppliers she calls before signing off. She is due to be promoted to run operations at a second site.

Illustrative example.

The operations director puts supplier approval on the company’s plan as the quality team’s first workflow, with the quality manager as its owner. In one interview she answers the ten questions. She then walks through four recent approvals: two routine, one where a certificate had expired, and one where the supplier’s address did not match its paperwork.

The written workflow reads a new supplier’s documents, checks each against her list, and prepares an approval note with every gap marked. She runs it on old cases, corrects two steps and approves it. A quality technician now runs it on every new supplier, and the technician decides whether each supplier is approved. The odd cases still go to the quality manager at her new site. She owns the method; the technician does the work her way.

What is different in a company of under 200 people.

In a company of under 200 people, single-person know-how is the normal state of affairs, and the fix is a conversation, not a program. Most published advice on knowledge capture is written for large enterprises with knowledge teams and document systems. A smaller company has neither, and does not need them.

  • You already know who holds it.Ask any team lead which work stops when one person is out, and you have your list.
  • One person is often the whole function.The bookkeeper, the estimator, the compliance lead. Capturing their method is the only backup the company has.
  • The expert is in the room.You can sit with them this week. A large company has to find the expert first.
  • Ownership is a name, not a committee.The expert owns the method. Who should own AI in a company your size? covers who owns the plan above it.

Where to start.

Start by listing the work in each team that only one person knows how to do, and put those pieces near the top of your plan. How organizations plan their use of AI sets out the three steps: plan it, develop the workflows, deploy them. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, and choose what to build first.

To capture the know-how with us, FullyPowered Studio turns an expert’s method into a workflow your team runs. We ask; we never watch, and Asked or watched explains why. Once captured, We have a plan. How do we build the first AI workflow? covers the build, and How to deploy AI workflows to a whole team covers putting it in everyone’s hands.