Unconscious Competence: Documenting the Expert Who Can't Explain It

Your best person can do the job flawlessly and cannot describe it accurately, and both things are true for the same reason. To document a process from an expert who cannot explain it, stop asking for the explanation and watch the work: record them running a real job, interrupt with why at the decision points, and put a newcomer in the room to catch the steps nobody else can see. What you cannot get out of an expert's mouth comes out of their hands.

Key takeaway: An expert who cannot explain their own process is not being difficult. They have reached unconscious competence, where the steps run below awareness, so the fix is to record the real work, ask why instead of what, and build the document from the footage. Budget 2 to 4 expert hours per documented process.

Why Your Best Person Is Your Worst Explainer

Ask a commuter to list every turn, merge, and brake tap on the drive home and you get a blank stare. They made the trip yesterday and will make it again tonight while thinking about dinner. The better someone gets at a job, the less access they have to how they do it, because expertise compresses steps into instinct.

This is a different problem from the expert who guards knowledge on purpose. When your expert will not document their work, you have a motivation problem. When your expert cannot, you have a wiring problem, and it deepens with every year of experience.

The expert is not hiding the process from you; the process is hiding from the expert.

Owners are not exempt. A founder of three companies told us: "There are a lot of things that I know that nobody knows but me, and I do not even know what I have told people and what I have not." The same blind spot is why new hires still take 6 months when the training plan is shadow someone: the person being shadowed narrates almost nothing.

What Is Unconscious Competence?

Unconscious competence is the final stage of skill, where a person performs work correctly without conscious awareness of the steps. Skills climb a familiar ladder: unaware, aware but unable, able with effort, and finally able without thinking. The last rung is the goal of all practice and the enemy of all documentation.

The knowledge moved out of words and into hands, eyes, and judgment, and an interview only tests whether it still exists in words. When people talk about capturing tribal knowledge, this is the hard layer: not the steps your team can recite, but the ones they cannot.

How Do You Document a Process From an Expert Who Cannot Explain It? Watch the Work

You document it by recording the expert doing the actual job, on a real case, narrating whatever surfaces. Never ask an expert to write down how they do their job; record them doing it. The truth lives in execution, not memory, and with the practitioner rather than the manager.

Two people run the session. One builds a visual map live while the expert shares a screen and works, the other takes notes and asks the occasional deep question. The standing instruction we give the expert first: "We want you to say, no, it does not look like that, I am actually doing this." The corrections are the process.

When an air duct cleaning client's exiting bookkeeper walked us through the weekly commission run, describing it took 85 minutes: two reports merged by hand because the export destroys job IDs, chat threads screenshotted to find who the helper was, receipts hunted through a login she did not have. The owner watched his own process for the first time in years and said quietly that this was a 3-day job, every week.

Nobody could have written that from memory, including the person who ran it weekly. That is what happens when a process only lives in someone's head.

Interrupt With Why, Not With What

The what takes care of itself. The screen shows every click and the recording keeps it, so asking what someone just did only breaks the flow. Save your interruptions for why: why that report before this one, why the pause before approving that job.

Why questions surface decision points, the moments where the right answer depends on context. They never appear in an expert's own writeup, because the expert does not experience them as decisions. When a why gets answered with a story, keep pulling until the story becomes a principle.

Emotion is the metal detector. If there is feeling behind an answer, it has already hardened into a law for them, formed by a first boss, a grandmother in a kitchen, or a mistake nobody wants to repeat. Surfacing that layer is what wisdom interviews are built for.

Use the Newcomer as a Detector

An expert cannot see their own invisible steps, and neither can an owner who has watched the job for years. Bring an instrument that can: the person who learned the work most recently. A newcomer is still consciously competent, so every question they ask marks a step the document is missing.

Interview both ends of the tenure scale, the veteran who has done the work longest and the newcomer who learned it last. When we ask an owner who belongs in the room, we ask two things: who does this well, and who is new enough to still see the problems. Casting the room is half of interviewing a subject matter expert well.

In one nonprofit client's largest department, teammates discovered mid-interview that they had each been running the same process a different way. "I did not really know that you were doing that" is a sentence worth the whole session, because it turns a private habit into a public decision about the one right way.

Turn the Recording Into the Document

The recording is raw material, not a deliverable. Nobody will scrub 85 minutes of footage to remember how to run a report, so here is the run we use.

1. Transcribe the session. The transcript is the searchable index and the source text for the SOP.
2. Map the segments. Break the footage into steps and decision points, each with a timestamp.
3. Pull annotated frames. Take the sharpest frame per step and mark the click target with a red box.
4. Assemble and gate. Write the SOP from the recording, never from memory, and run quality checks before it ships.

The output is a written SOP with annotated screenshots, plus short video modules cut from the same footage. Hold every step to the glance test: a reader should glance at one step and know what to do. AI earns its keep on transcription and formatting, but it cannot capture what it has never seen.

Recording buys you the truth at the cost of production time, and it only works on work someone can run while you watch. A quarterly close or an annual audit means waiting for the next real cycle, because a staged run gives you the tidy version you were trying to escape. Field work is the other limit: there is no screen to share, so someone has to stand there with a camera.

---

The Trust Trap: Competence You Cannot See

Unconscious competence has a second cost, and it lands on the owner. One owner spent two full days mapping every step a dispatcher's role carries. Then the dispatcher missed a meeting because he never checked his calendar: "How can we trust someone to do all the steps I sat with him for two days on, when he cannot even look at his calendar?"

That is the trust trap. When the work runs below awareness, the owner cannot see it being done right, so trust attaches to the person instead of the process, and one visible miss outweighs a hundred invisible successes.

Competence you cannot see is indistinguishable from competence that is not there.

Documentation is the way out. Once the steps exist where anyone can check them, a missed meeting becomes a checklist fix instead of a character verdict. It is also why this belongs inside a knowledge transfer plan built before you need one rather than a notice period. Sitting in the room while an expert works, then turning that footage into training people actually follow, is the work The Systems Effect does with clients.

Start small. Pick the one process only your best person can run, book an hour, and record them doing it for real. Do not ask them to explain the drive home. Turn the camera on and let them drive.

Frequently Asked Questions

What is unconscious competence?

Unconscious competence is the final stage of skill, where a person performs a task correctly without conscious awareness of the steps. The tell is a gap between performance and description: the work runs clean, and the account of it comes out short, tidy, and missing every workaround. It is the goal of every training program and the reason an interview alone never produces a usable SOP.

How do you document a process someone does automatically?

Record them doing the real work instead of asking them to describe it. Run a live session where the expert performs an actual case while narrating, with one person mapping the steps and another asking why at each judgment call. Build the SOP from that transcript and footage, and expect 2 to 4 hours of the expert's time.

Why can experts not explain their own work?

Expertise compresses steps into instinct, so the better someone gets at a job, the less access they have to how they do it. Asked to explain, they answer from a tidied memory rather than the process itself, which is why a walkthrough of the real thing always runs longer and messier than the description.

Who should watch an expert work during documentation?

Two people at minimum: one leading a live visual map, and one capturing notes and asking why at the decision points. Add the person who learned the job most recently, because they still see the steps the veteran no longer notices. Record the practitioner, not the manager describing the work.