How to map a business process from employee interviews

To map a process from interviews, talk with each person who touches the work, one at a time, about the last real case they handled, not about how the process is supposed to run. Write down each step with who did it, the system they used, how long it took, and who told you. Then compare the accounts, settle where they disagree, mark what nobody knows, and have each person confirm their part before an owner approves the map.

Why interviews, and why the last real case

A written procedure says how the work should go. A manager sees how it looks from above. The people who do the work know how it goes today, with the workarounds that grew over the years.

The Lean Enterprise Institute calls the place where value-creating work happens the gemba, and notes that standardized work “cannot be written at a desk.” In an office process, the gemba is the shared inbox, the order screen and the phone call with the customer.

How you ask matters as much as whom you ask. Nielsen Norman Group’s guide to interviewing users warns that people asked how they usually do a task will often describe “an idealized workflow without the many shortcuts and deviations that characterize real projects.” So ask about one case: “Walk me through the last order.”

John Flanagan, who described the critical incident technique in a 1954 paper, asked for the most recent case for a related reason. Otherwise people report only the dramatic cases, or the ones that fit what they already believe.

Who to talk to, and in what order

Follow the work. Each interview tells you what to ask in the next one.

1. The process owner, briefly. Agree where the process starts, where it ends, and what “done” means. Treat their account as a draft to check, not as the map.
2. The person who receives the trigger. The first step is where the work arrives: an inbox, a phone, a paper form.
3. Each person who receives a handoff, in order. Ask what arrives, from whom, and how they know it is there.
4. The people who handle exceptions. Credit holds, missing items, complaints. They see the cases that break the flow.
5. The person who closes the loop. Often billing. They see what was missing at the end.

Talk to at least one person in every role that touches the work. Talk to two where most of the volume sits, or where shifts or sites differ. If two people in the same job do it differently, that is a finding, not noise.

Interview people one at a time. Alone, people describe what they do. In a group, they describe what the room expects.

What to capture for each step

Use the same fields for every step, from every interview. Copy this template:

Field	What to write	Example
Trigger	What starts the process	An order email with a PDF attached
Step	A verb and an object	Type the order into the order system
Who	The role, and the person who told you	Order desk (Sam)
System	Where the step happens	Email, order system
How	By hand, with a tool, or typed twice	Typed twice: from the PDF into the order system
Handoff	To whom, and how they find out	Warehouse, by chat message
Time	Work time and waits, with the unit	About 10 minutes of work per order
Exceptions	What goes differently, and how often	Unknown item codes, “sometimes”
Source	Who said it, and where in the interview	Sam, interview 1, minute 4
Status	Confirmed, estimate, conflicting, or unknown	Estimate

The “how” field is where improvements hide. A step that copies information from one system into another is typed twice. Information that travels by message, outside any system, is easy to lose.

Map the information as well as the work. The Lean Enterprise Institute’s description of value-stream mapping includes the information flow that “tells each process what to make or do next and when to do it.” In an office, that flow is often an email or a chat message.

Keep a source for every detail

Every line on the map should answer one question: who said this, and where? Write the source next to the detail, not in a separate notes file.

Sources pay off when two accounts disagree, when the owner checks a surprising detail, and when someone asks where a number came from.

Keep the person’s words when they give a number. “About ten minutes” goes on the map as “about 10 minutes, estimate.” It does not become “10 minutes.” Never fill a gap with what must happen. If nobody said it, it is not on the map yet.

Example: customer orders at Example Supply Co.

Example. Example Supply Co. is invented: a 40-person distributor of cleaning supplies to offices and hotels. Nothing here comes from a real interview.

Sam works in customer service. Asked about the last order, he said: “It came in by email, a PDF from a hotel. I typed it into our order system. That takes about ten minutes. Then I message the warehouse so they can pick it.”

Dana runs the warehouse. Asked about the last order she picked, she told it differently: “We pick from the pick list. The order system prints it at 10 and at 2. I don’t watch the messages, unless someone writes ‘rush.’”

The two accounts disagree on what starts the picking. Sam believes his message does. Dana says the printed list does. This is how it was settled:

1. Check whether both are true. Each person described what they see. Sam sees the message he sends. Dana sees the list she picks from.
2. Look at the last case. The order was entered at 10:40 a.m. The message went out a minute later. The order was picked from the 2 p.m. list.
3. Ask one short follow-up, about that case. Dana confirmed she reads the messages only when they say “rush.”
4. Map what happened, and say why. The pick list starts the picking. The message matters only for rush orders. An order can wait up to four hours for the next list.

There was a second disagreement. Sam thought invoices go out with the delivery. Priya, the bookkeeper, said she invoices everything that shipped at month end, typing each invoice from its delivery note. For what happens inside a step, the person who does the step is the main source, so Priya’s account sets the invoicing step.

One detail stayed open. Sam said a PDF “sometimes” has an item code the order system does not know. Nobody could say how often. The map marks it as unknown, with a question for Sam: count them for one week.

The settled map:

#	Step	Who	How	Time reported	Status
1	Order arrives by email, as a PDF	Customer	Email	–	Confirmed (Sam)
2	Order typed into the order system	Order desk	Typed twice	About 10 minutes per order	Estimate (Sam)
3	Warehouse told by message	Order desk	Chat message	–	Settled: acted on for rush orders only
4	Order picked from the printed list	Warehouse	Paper list, printed at 10 a.m. and 2 p.m.	Waits up to 4 hours for the next list	Confirmed (Dana, print times)
5	Order delivered with a delivery note	Warehouse	Paper	Leaves on the next morning’s route	Estimate (Dana)
6	Invoice sent	Bookkeeper	Typed twice, from the delivery note	Waits until month end	Confirmed (Priya)
?	PDF with an unknown item code	Order desk	–	How often: unknown	Open question for Sam

Settle conflicting accounts

Use this checklist for any disagreement:

• Put the accounts side by side, step by step, with their sources.
• Ask whether they really conflict. Often two people describe the same moment from two sides.
• Prefer the person who does the step for what happens inside it. For a handoff, ask both sides.
• Look at the last case. Times in the email, in the order system or on paper often settle it.
• Ask a short follow-up about that case, not about the process in general.
• If people really work differently, map both ways, and say who does which.
• Never average two accounts into a version nobody described.

Mark what is unknown

A map that says what it is missing is more useful than one that guesses. Give every detail one of four labels:

• Confirmed: said by the person who does the step, or checked against the case.
• Estimate: a number someone gave as approximate. A sum of estimates is still an estimate.
• Conflicting: two accounts disagree, and it is not settled yet.
• Unknown: nobody knew, or nobody was asked yet.

Every unknown and every conflict becomes a question, with the name of the person who can answer it. That list is the work left before the map can be approved.

Confirm, then approve

Send each person a short summary of what you understood from them, close to their own words. Ask them to correct it. A wrong detail is easiest to fix before anyone acts on it.

The summary also shows people that the interview was about the work, not about them. Nothing is used until they have seen it.

Then the process owner approves a version of the map. Approval means “this is how the work goes today,” not “this is how it should go.” Date the version and keep it. When the process changes, compare the next version with this one.

A checklist you can copy

• Scope agreed with the owner: where it starts, where it ends, what “done” means
• Interviews follow the flow of the work, one person at a time
• Each interview is about one recent, real case
• Every step has a who, a system, a how, a time and a source
• Estimates are marked as estimates, in the person’s words
• Conflicts are listed, each one settled or open
• Unknowns are listed, each with a question and a name
• Each person has seen and corrected their summary
• The owner has approved a dated version

Bondi Discovery runs this kind of interview as a voice conversation of up to 12 minutes with an AI interviewer that says it is AI, and shows the words each detail on the map came from, with a link to the interview.