How to document a business process from an employee interview

Start with a specific case

“How does it all work?” often gets a broad answer: we receive, check, and fulfill requests. This hides where a request waits, who asks for details, and why work goes back. Ask the employee to recall the most recent completed request and walk through it in order.

The current process and a future design are separate documents. Reconstruct what happens today. Keep ideas such as automating a handoff or removing approval separate so the team can validate the actual process.

What to ask and how to use the answers

1. Set the boundaries

   Ask what event starts this work and what counts as completion. “From inquiry to shipment” is too broad for a first interview. “From receiving the request to handing a checked package to production” defines a segment and a verifiable output.

2. Reconstruct the handoffs

   After each action, ask who received the output, in what format, where it is stored, and how the next person finds out. An email sent and work accepted are separate events. A wait between them may be missing from the procedure.

3. Find the exceptions

   Ask for examples of incomplete data, a return for rework, and an urgent request. Record the branching condition, next action, and decision maker. Avoid writing “usually within a day” unless the recording establishes when the clock starts and what is excluded.

4. Check with a second participant

   Show the draft to the person who receives the output. Ask them to walk another real request through it. If the accounts differ, keep both and check whether the customer type, product, or work situation differs.

Receiving a request to make a sign

The example is fictional. Names, conditions, and outcomes illustrate the method.

There are two checks: dimensions must be present and confirmed. “Check the artwork” alone is too vague. The next person needs a clear indication that both checks are complete.

The branch in the diagram shows whether the package is complete. Customer confirmation is recorded separately in the handoff card. The manager forwarding an email does not replace it.

Process description card

Copy the template and fill it in for one case. Treat blank fields as questions to clarify.

Process name:
Trigger:
End boundary:
Case type and date:
Step / owner / input / action / output:
Who receives the result and how:
Where work waits:
Return condition and next step:
Source: recording and timecode:
Differences between participants’ accounts:
Who reviewed the description and when:
Improvement proposals, kept separately:

Walk a second case through the diagram

• Each step describes an action.
• Every handoff has a recipient and a sign of acceptance.
• A return leads to a specific action.
• The current state is distinct from proposals.