THE WATERLINECompanion · Gabor Szorad

Chapter 3 · Descend: find and map

Turn a voice memo into a process map

Nobody wants to write down how they work. Everybody can talk about it.

The sequence

  1. Sit with the person who does the work. Tell them you are not building a policy document, you just want to hear how they think about it.
  2. Record them walking through the work out loud, in their own words. A voice memo on your phone is fine. Let them ramble.
  3. Transcribe the recording. Use an approved tool and follow your data rules.
  4. Hand the transcript to AI with the prompt below.
  5. Walk back through the map with the person and fill the holes.

What comes back is about 80% right on the first try. The other 20% is the good part. It shows you the steps the person does automatically and never mentioned, and the decisions they make without noticing they are making them. Within an hour you have a written version of how the work is done, rather than how the manual says it works.

Count work and waiting separately

For the most recent real example, record hands-on minutes and elapsed waiting time. A fast task may still be stuck in an approval queue. Have the person doing it correct your map.

The prompt

Works in Claude, ChatGPT, Copilot and Gemini. Nothing to install.

Below is a transcript of someone walking through how they actually do [the process], start to finish, in their own words.

Turn it into a process map:
1. Number each step in order.
2. For each step give me: what triggers it, what they do, which system or tool they use, what they produce, and who gets it next.
3. Mark every point where they make a judgment call, and say what information they use to make it.
4. Flag every "it depends" and every step they described vaguely or skipped past.
5. Separate active hands-on time from elapsed waiting time at each step. Do not count two days waiting as two days of labor. Ask for missing durations rather than guessing.
6. Identify the knowledge held by only one person and prioritise what to capture before they leave.

Then list the 3 to 5 things I would need clarified before this process could run without them in the room.

Transcript:
[paste]

A worked example

The warehouse

A client needed to capture the man who had run their intake process for eleven years. He had never drawn a flowchart in his life and was never going to start. But he could walk the floor with a phone recording and describe every decision he made at every point, because he had made those decisions ten thousand times.

We recorded him, transcribed it, and dropped it into the AI. We had a working process diagram before we left the building. Eleven years of knowledge that had existed nowhere except in one head, out in the open.

The stop rule
Sometimes you go to map a process and discover there is no process. Nobody can walk it through, because everyone does it differently and it is a tangle of chat threads and “well, it depends.” When that happens, stop. Do not automate it. You would be building a fast, expensive machine for producing the confusion you have now. Fix the process by hand first, simplify it until a person can explain it, and only then think about automating it.

Then name the case

Write the process down as one plain sentence that a colleague who knows nothing about AI could read back to you. For example: read our incoming invoices, pull out the amounts and suppliers, and create the records for the accountant to check. If you can say it that plainly, it is ready. If you cannot, it is not clear enough to build yet.

AI says wrong things with total confidence. Check what it gives you against the person who does the work.
The Waterline companion. Everything here works in Claude, ChatGPT, Copilot and Gemini. Nothing to install. Last reviewed 5 November 2026.