500 free credits, no card. Try Smalt AI →

Operations

How do I write a process document for a task only one person knows

Record the expert doing the task while narrating, interview them for the why, have someone else write it up, then test it with a person who has never done it.

Smalt AI team ·

Don’t ask the expert to write it. Have them do the task once while narrating and record it, interview them about triggers, exceptions and reasons, and let someone else turn that into a draft. Then have a person who has never done the task follow the draft and fix every place they get stuck.

How to document a task only one person knows

We found no source on this exact case; the sequence below is our synthesis of guidance on the process document (often called an SOP) and on knowledge transfer, and each step says where it comes from. The sources are vendor and consultancy pages, not standards bodies.

  1. Set the scope. Write down the purpose, an actionable title (“Process the weekly vendor payment run”, not “Payments”), and what the process document does not cover. Atlassian’s guide (published 2024-11-21) lists purpose, title, and scope with exclusions as the first things to settle. It advises choosing a format up front: list, hierarchy, flowchart or checklist.

  2. Have the expert do it once, out loud, on a recording. Ask them to run a real instance of the task and say what they are looking at and why they take each action. TechSmith recommends narrated screen recording for this, so decisions get spoken instead of skipped. TechSmith sells recording software, so weigh that, and the page is undated. Atlassian’s guide likewise pairs the written steps with a recorded walkthrough.

  3. Interview them afterwards. The recording shows what they did on one day. It will not show the cases that did not come up. Ask what starts the task, what the usual exceptions are, what they check that is not obvious, and what they would do if a step failed. A white paper from Enterprise Knowledge (2025-10-14) makes the underlying point: step-by-step process documents alone miss the reasoning behind decisions, and the paper ranks decision rationale as the most important thing to capture, ahead of operational processes and project context. Its recommended method is recorded interviews, in its case between a departing employee and a successor.

  4. Have someone who is not the expert write the first draft. A person who does not already know the task will ask what a step means, and those questions are what make the process document usable. The expert reviews for accuracy afterwards, but does not hold the pen. This is our recommendation rather than something the sources prescribe.

  5. Write steps in active voice and assign roles by job title. “Finance lead approves the batch” survives a reorganisation; “Priya approves the batch” does not. The same Atlassian guide recommends active-voice steps, screenshots where they help, and roles by title, using a RACI chart if several people are involved.

  6. Test it with someone who has never done the task. Give them the process document and nothing else, and let them run it. Every question they ask and every point where they stall is a gap. Atlassian’s advice is to test with the people who will use it. Fix the gaps, then run it again with the expert out of the room if you can.

  7. Name an owner and a review date. Enterprise Knowledge suggests updating process documents during routine work rather than in a separate project. In practice that means whoever runs the task next is expected to correct the process document as they go, and one named person confirms it on a fixed date.

StepWho does itOutputSource
1. Set the scopeWhoever writes the process documentPurpose, title, exclusions, formatAtlassian
2. Record the expertThe expertNarrated recording of a real runTechSmith, Atlassian
3. Interview themThe expert, asked by the writerTriggers, exceptions, reasonsEnterprise Knowledge
4. Write the first draftSomeone who is not the expert; the expert reviewsFirst draftOur recommendation
5. Write steps and rolesThe writerActive-voice steps, roles by job titleAtlassian
6. Test itSomeone who has never done the taskList of gaps, fixed draftAtlassian
7. Name an ownerOne named personOwner and review dateEnterprise Knowledge (updating during routine work); owner and date are our wording

A finished step in the process document should carry its trigger, its action and its exception. This one is illustrative only, not taken from a real document:

Step 4. Release the vendor payment batch. Trigger: the finance lead has approved the batch. Action: the payments clerk uploads the approved file to the bank portal and records the confirmation number. Exception: if the bank portal rejects the file, do not re-upload; send it back to the finance lead with the error message.

Doing it with an AI coworker

If you already have raw material, such as the emails where the expert explained the task to someone, the checklist they keep for themselves, or notes from the recorded walkthrough, you can give it to Smalt and ask it to write up how the process runs. You would ask for numbered steps with roles by job title, and for the process document to be saved to Notion so the owner can edit it there.

Ask it to call out the places where your sources disagree, for instance an email that says invoices go to one approver while the checklist names another. Saving to Notion is not held for approval the way an email or Slack message is, so the process document appears in your workspace as soon as it is written. Treat it as a draft until the expert and a first-time user have gone through it.

What to check before you rely on it

The process document is only as good as the day you recorded. If the expert ran a routine case, the exceptions are missing, so ask them to walk through the last time something went wrong. If you can, record a second run on a different kind of case.

Experts also skip steps that feel automatic, such as which login to use or which folder a file lands in. A first-time tester usually catches these, so don’t skip the test because the draft reads well.

Check the roles against your current org chart, since titles drift, and confirm the owner knows they are the owner. Keep the recording too, because it holds the expert’s explanations when a written step later turns out to be unclear.

Smalt is an AI coworker that takes jobs like this end to end and hands back the finished file.