Skip to content

AUTOMATION BRIEFS · WHAT AI ACTUALLY DOES

Turning tribal knowledge into living SOPs

Make your team’s experience easier to share. Turn expert walkthroughs into useful instructions that help new colleagues learn and give experienced people more room for the work they enjoy.

Brief sections

The leak

Ask two people who do the same critical process to write down the steps, separately, and compare. The differences are your exposure, in writing. Most operating businesses run on knowledge that was never captured because capturing it was always someone’s spare-time job, and nobody has spare time. So onboarding means shadowing the veteran for a quarter, quality depends on which shift did the work, and when the veteran retires the next person has less context to work from. The binder on the shelf isn’t the fix; it was wrong within a month of being printed.

What AI realistically does here

It attacks the reason SOPs die: writing them is a second job. Instead of asking the veteran to author documents, the system captures how work actually happens — screen recordings, walkthrough interviews, the message threads where real exceptions get resolved — and drafts the SOP from evidence. The veteran reviews and corrects, which they’ll actually do, because editing is cheap and authoring is expensive. Then it keeps the documents living: when the process changes and the SOP no longer matches reality, the drift gets flagged instead of silently accumulating. What it can’t capture is judgment — knowing when to bend the rule is learned, not documented — so the goal is that facts and steps survive turnover, not that people become optional.

What has to be true first

  • The veterans are in. Agree what knowledge is useful to share, how it will be used, and how it will help the people contributing it. Have that conversation before recording anything.
  • One process to start, chosen because it’s critical and stable — not the one that changes weekly by design.
  • An owner for accuracy: someone signs their name to “this is how we do it.”

What we'd install

In a knowledge-capture engagement, the learning can support the wider business: the workflow gets mapped and redesigned as it’s captured, the SOPs land in a library that new hires and AI agents both draw on, and the value ledger tracks the numbers that actually move — time to competence for the next hire, and how many “quick question” interruptions the veteran still fields. Where it sits in the sequence is on the AI operating partnership.

Worth it?

Put a number on your last onboarding: months to independent work, times the loaded cost of both the trainee and the veteran carrying them. The calculator below turns the recurring hours into an illustrative annual range — illustrative math, not a promise. The one-time cost of a walk-out usually decides this on its own, and the scorecard tells you how exposed you are.

FAQ

Questions operators ask about this workflow.

01Won’t the veteran feel like they’re training their replacement?

If that’s how it’s framed, yes, and the project dies. The honest version is different: the SOP absorbs the interruptions — the same five questions every week — while the judgment calls still come to them. We involve experienced staff in shaping the workflow, reviewing its quality, and choosing where the time returned is most useful.

02How is this different from hiring a technical writer?

A writer produces a beautiful snapshot that starts rotting the day it’s delivered. The point here is the maintenance loop — capture as a by-product of normal work, drift flagged automatically — because staleness, not absence, is why your current binder is useless.

03What format do the SOPs take?

Searchable, linkable documents a new hire can follow and an AI agent can reference — not a PDF in a folder. The format matters less than two properties: findable in seconds, and correctable in minutes when reality changes.

04When is this NOT worth doing?

When the process is genuinely in flux — a line you’re re-tooling, a role you’re redesigning. Document the stable core and let the moving parts settle first; capturing churn just produces authoritative-looking wrong answers.

Score the leak before you build

Find out if this is the workflow worth fixing first.

The scorecard checks whether the value, data, risk, and adoption path are strong enough to move.