How to write down what is in someone's head

Why asking people to write it down fails, and what to ask them instead

By The Human Union team · 14 Nov 2026 · 4 min read

Every company makes the same request sooner or later. A manager notices that one person knows how something works and nobody else does, and asks them to write it down. A month later there is either nothing, or two pages that read like the manual. Neither helps the next person.

This is not because people are unwilling. It is because "write it down" asks for the wrong thing.

Why "write it down" fails

Writing a procedure means turning what you do into a list, from a blank page, on your own. That is hard for anyone, and hardest for the people who know the most. When you have done a job hundreds of times the steps stop feeling like steps. You notice something, adjust, and move on, and none of it seems worth saying.

So the expert writes what they think a procedure should look like. That is usually the official version: the steps anyone could have guessed. The parts that make the job work are missing. The check they always do first. The exception they handle without thinking. The reason they never trust a particular report. Not hidden, just invisible to the person who holds them.

Then there is the blank page itself. Most people, asked to write about their work in general, go vague. Asked about one specific time, they get precise.

Ask, and ask about a real case

Knowledge comes out much more easily in conversation than in writing. The skill is in what you ask. Four kinds of question do most of the work.

The last time it happened. Not "how do you do the month-end accruals" but "talk me through the last time you did them". A real case has real detail: what came in late, what did not match, who they had to chase. General questions get the textbook. Specific questions get the job.

A real example of it going wrong. "When did this last not go to plan, and what did you do?" The exceptions are where most of the knowledge sits. The normal case is often written down somewhere already. The awkward case is not.

The why behind each step. Each time someone describes a step, ask why. Why that order? Why check that first? Why not trust the figure from the system? The why is what lets the next person handle a case the procedure does not cover. A list of steps without reasons only works until something changes.

What a new person gets wrong. "If someone new did this tomorrow, where would they trip up?" Experts are good at answering this, because they have watched it happen. The answer is often the most useful line in the whole procedure.

Keep each conversation short and about one task. Fifteen or twenty minutes on one job is worth more than an hour on "your role".

Many people, one procedure

One person's answer is a good start, but it is one person's version. Ask three or four people who do the same work and you get something better, and something more honest.

Lay their answers side by side and three things appear.

  • The steps everyone agrees on. These are the backbone of the procedure. When five people describe the same check in different words, it belongs in.
  • The steps only one person does. Sometimes that is a habit worth spreading: the person whose work rarely needs redoing is doing something the others are not. Sometimes it is a workaround for a problem nobody has fixed.
  • The places they disagree. Two people do a step in a different order, or one skips it. Do not smooth this over. Write it down as an open question and settle it with the people involved. The disagreement is often where the next mistake will come from.

Then write the procedure in plain words, in the order the job happens, with the reason next to each step and the common mistakes called out. Keep the original answers alongside it, so anyone can see where a step came from and who to ask.

Keep it alive

A procedure written once starts to drift the week after. Systems change, people find better ways, a supplier changes a form. The fix is not a yearly review that nobody does. It is to keep asking: when someone new joins, when something goes wrong, when the process changes. Each new answer either confirms the procedure or shows where it has gone out of date.

Where we fit

This is the work our product does. You describe the problem, it drafts the questions, and each person gets a personal link to talk or type with an AI interviewer for five to twenty minutes, on their phone or laptop, in their own language. You read every answer in English, and the answers become step-by-step procedures, handover docs and a knowledge base, with a ranked list of what goes wrong and how many people raised each point. Nobody is rated, and answers are kept as text, not recordings.

You can do all of this with a notebook and some patience. The questions are the part that matters.


See it with your own example. Thirty minutes with our team, using a question from your own work. Book a demo, or try the ROI calculator first.

See it with your own example

Thirty minutes with our team, using a question from your own work.

Book a demo