How do I capture knowledge before an experienced coworker becomes unavailable?
Quick answer
Start with the work that would be hardest to pause or hand over, then ask your coworker if they are willing to explain how they do it. Capture the steps, decision points, exceptions, and where to find current information. Check your notes with them, mark anything uncertain, and agree who can maintain the guide. Keep the request focused and respectful; do not assume why or when they may become unavailable.
The question, the details, the next step.
An experienced coworker may not be available for some of their usual work at some point, but I don’t know the circumstances. How can I start capturing what they know without making it awkward?
Treat this as a practical continuity conversation, not an inquiry into their personal circumstances. Ask whether they would be open to sharing how they handle a specific recurring task. Explain what you hope to preserve: for example, helping another person cover the work or making a process easier to follow. Give them room to decline, suggest another time, or choose what to discuss.
A focused request is easier to answer than “Tell me everything you know.” You might say: “Could we spend 30 minutes walking through the monthly [task]? I’d like to capture the steps and the points where you use judgment, so someone else has a useful starting point if needed. Is there a part you’d rather start with?”
Before meeting, list the tasks that are frequent, time-sensitive, difficult to hand over, or especially dependent on this person’s judgment. Ask which ones they think are most important. Agree on what can be written down and who should review or maintain the notes.
Once we have picked a task, what should I ask so I capture more than a basic list of steps?
Ask them to talk through one ordinary example from start to finish. Follow the sequence, but pause at the choices: what tells them it is time to begin, what information they check, and how they decide what to do next. Invite them to describe common exceptions and what they do when information is missing or the usual route does not fit. You are capturing their explanation, not asking them to reveal every unrecorded detail in one sitting.
A reusable question list:
- What starts this task, and how often does it come up?
- What do you need before you begin? Where is that information kept?
- What are the main steps, in order?
- Which decisions require judgment? What signals guide those choices?
- What exceptions or common snags should a new person watch for?
- When should someone pause and ask for help rather than guess?
- How do you know the task is complete, and who needs to know?
- What existing guide, example, or contact should the next person consult?
If a detail is unclear, mark it as a question for follow-up rather than filling the gap with your own guess.
How should I organize the notes so someone else can actually use them?
Keep each guide centered on one task, use plain language, and distinguish confirmed steps from open questions. A practical outline is:
Task: [name] Purpose and trigger: [why it is done; what starts it] Owner or reviewer: [role or team] Before starting: [inputs and where to find them] Steps: [numbered actions] Decision points: [condition or question] → [usual next action] Exceptions: [situation] → [what to check or whom to ask] Completion: [how to check it is done; who to notify] References: [existing internal document or system name] Open questions / last reviewed: [items to verify; date]
For example, a placeholder decision point might read: “If [required information] is missing, pause and ask [role] before continuing.” That is a structure, not a claim about your workplace’s procedure; fill it in with your coworker’s confirmed explanation. Don’t include passwords or other sensitive access details in a general guide. Point to the appropriate approved place for access instructions instead.
After drafting, read the guide back with your coworker. Ask them to correct missing steps, unclear wording, and places where the notes make a judgment call sound automatic. If possible, ask a suitable colleague to follow the notes and flag where they get stuck. Keep unresolved items visibly unresolved.
What if they are busy, or I cannot finish documenting everything before their availability changes?
Make the work small and prioritize a useful first version over an exhaustive manual. Offer a short session on one high-priority task, or ask whether they would prefer to talk while you take notes and send a draft for correction. If a live meeting is difficult, ask whether they are comfortable reviewing a short list of specific questions asynchronously. Do not record a conversation or circulate their notes without their agreement and without following your workplace’s practices.
If time is limited, capture the task’s trigger, essential inputs, main steps, judgment points, common exceptions, completion check, and where to find current guidance. Label anything not confirmed and identify who could verify it later. Agree on a next step, such as reviewing one draft or naming a role to maintain it. The result should help a colleague know where to begin and when not to guess—not pretend to replace the experienced person’s judgment or all local context.
A practical checklist
Choose one recurring or difficult-to-cover task and agree it is a useful priority.
Ask permission and explain the practical purpose without asking about personal circumstances.
Capture triggers, inputs, steps, decision points, exceptions, and completion checks.
Mark uncertain details as open questions rather than inventing instructions.
Review the draft with the coworker and agree who can update it.
A few more useful answers
Should I try to document every task the coworker handles?
Usually start with a small number of high-priority tasks rather than attempting an exhaustive record. Ask the coworker which work would be most useful to make easier to cover.
What if my coworker does not want to share or document their process?
Respect their choice and ask whether there is a smaller topic or different format they would be comfortable with. You can also ask an appropriate manager or process owner what existing guidance is available, without presenting unconfirmed details as fact.
How do I keep the notes from becoming outdated?
Name a role or person to review them, and make unresolved questions and the last review date visible. When the process changes, update the affected steps rather than assuming the old guide still applies.