Process discovery interview questions that reveal the real work

A process discovery interview should establish what starts the work, who performs each step, what information and tools are involved, where decisions happen, and how the work finishes. Walking through a recent example helps reveal details that a general description can miss.

Start with one recent case.

Ask the person to describe a piece of work they actually handled. Do not begin by asking them to invent the ideal process.

Use a routine example first, then an exception. Agree what information can be discussed and how any recording or notes will be handled before the session begins.

Questions about the start

1. What caused this piece of work to begin?
2. How did you find out it needed attention?
3. What information was available at that point?
4. What had to be clarified before you could start?

These questions help define the trigger and expose missing inputs. “The customer contacts us” may turn out to mean several channels with different information.

Questions about the steps

1. What did you do first, and what happened next?
2. Which tool or record did you use?
3. What decision did you make at that step?
4. What told you it was ready to move on?

Record the steps in the person’s words before normalizing them into a process map. If they mention a spreadsheet, note what it contains and why it is needed rather than assuming it is unnecessary.

Questions about handoffs

1. Who needed to do something next?
2. How did they know it was their turn?
3. What information did you pass to them?
4. How could you tell whether they had picked it up?

A handoff has both information and responsibility. Capturing only the movement of data may miss why work waits.

Questions about exceptions

1. When does the normal path not work?
2. Who decides what to do differently?
3. What information is commonly missing or wrong?
4. What happens when the usual person is unavailable?

Ask for an actual example. The exception can reveal a business rule that would otherwise remain implicit.

Questions about completion and improvement

1. What tells you the work is finished?
2. Who checks that the outcome is correct?
3. Where did this case wait or need rework?
4. What would you change first, and why?

Treat a proposed fix as an idea to assess. It may be useful, but the interview alone does not prove its cause or value.

Separate three kinds of notes.

Note type	Example	How to use it
Reported fact	“I copy the approved details into a second system.”	Confirm in the process review
Interpretation	“The second entry may create rework.”	Label as a hypothesis to investigate
Proposed improvement	“Connect the handoff between the systems.”	Assess feasibility, cost, and controls

This separation helps avoid turning a plausible explanation into an unsupported conclusion.

Check the map with the people doing the work.

Read the process back. Confirm the order, ownership, information, and exceptions. Ask what is missing and where another participant might describe the work differently.

A reviewed current-process map is more useful than an impressive diagram that nobody recognizes.

What to leave with

The process boundary; the steps and owners; the tools and information; the handoffs and decisions; reported bottlenecks; open questions; and the statements supporting the findings.

Only then move to prioritizing changes.

Explore the AI Process Analyst ↗

Next step: Choose which improvements to make with Discovery Studio → /solutions/discovery-studio/