How do I document a process so someone else can follow it?

Start with the handoff, not with every detail you know. Identify the reader, the task’s purpose, and what “done” looks like. Then list the conditions that must be true before they begin. Use numbered steps in the order they happen, with one main action per step. For each important step, explain what to do and what result to check for.

A useful guide answers four questions: What do I need? What do I do? How do I know it worked? What should I do if it didn’t? Avoid relying on phrases such as “do the usual thing” or “send it to the right person”; replace them with an observable action or a placeholder that your team can fill in.

Use this copyable template and adjust the headings to fit your team:

Process name: [Task name] Purpose: [Why this task is done] Owner or contact: [Role or team] Last reviewed: [Date or version]

Before you begin

• Who should use this guide: [Role or situation]
• Prerequisites: [Access, materials, information, or approvals needed]
• Start when: [Trigger or timing]
• Finish when: [Observable completion condition]

Steps

1. [Action]. Expected result: [What you should see or have afterward].
2. [Action]. Expected result: [What you should see or have afterward].
3. [Action]. Expected result: [What you should see or have afterward].

If something goes wrong

• If [specific problem], check [relevant observation] and then [approved next step or contact]. Don’t guess if the next action is unclear; ask [role or team].

This separates setup from the sequence, so readers can check prerequisites before they start. Use role names or bracketed placeholders rather than personal contact details, and point to the team’s approved location for current forms or instructions.

Assuming your team already has an agreed meeting time and a place to store its agenda, turn each vague instruction into an action and a check. For example:

Purpose: Prepare a draft agenda so attendees can review the topics before the weekly meeting. Before you begin: Confirm the meeting date and use the team’s designated agenda document.

1. Review the notes from the previous meeting. Expected result: Any unfinished items that need discussion are identified.
2. Ask topic owners for proposed items by [team-agreed deadline]. Expected result: Each proposed item has a topic, an owner, and the decision or discussion needed.
3. Add the items to the agenda in the team’s agreed order. Expected result: The draft includes the date and each topic’s owner.
4. Check the draft against the team’s meeting format. Expected result: Required sections are present and unclear items are flagged for follow-up.
5. Share the draft using [team-approved location or method]. Expected result: The draft is available where attendees expect to find it.

Those deadlines and storage choices are placeholders, not claims about your team’s rules. Replace them with your actual agreements. Notice that the steps describe actions, while the expected results let a new person check their progress.

Write a small decision path, not a guess. Name the condition the reader can observe, the permitted next action, and when to stop and ask for help. For the agenda example, you might write: “If a topic has no owner or a clear purpose, mark it ‘needs clarification’ and ask the topic submitter to complete those details before adding it as a confirmed agenda item. If the submitter is unavailable, ask [role or team] how to handle it.”

Keep recovery notes within the reader’s authority. If you don’t know what the approved next step is, leave a placeholder for the process owner to fill in rather than inventing one. Include a contact role or escalation route that will still make sense if a particular coworker changes roles.

Ask someone who hasn’t done the task to follow the draft using the same normal resources they would have on the job. Observe where they stop, interpret a phrase differently, or need information the guide doesn’t mention. Don’t coach them through a gap and then assume the written instructions were clear: note the gap and revise the guide.

For the agenda process, check whether they can identify the right starting point, add a topic with enough detail, recognize an item needing clarification, and find the draft in the agreed location. After the tryout, make the smallest useful edits and ask the process owner to review any team-specific decisions. Add a review date or version so readers can tell which guide they have. Update it when the agreed process changes or a tryout reveals a missing or confusing step.