Process discovery interview questions that get beyond the job description.

The most useful discovery question often starts with a recent example, not a request for a complete procedure. “Walk me through the last case” gives the person something concrete to explain and gives the reviewer a sequence to check.

Use the question bank below as a guide. Do not send every question to every employee. Select a few that fit the person's role and the workflow being examined.

Download the adaptable employee request.

Ask what the business is trying to accomplish, which operating stages contribute to that goal and where leadership believes work is getting stuck. Name the workflow boundaries and the people likely to have different parts of the story.

Useful prompts include: What decision should this review help you make? What is outside the scope? Which responsibilities are known, and which are uncertain? What information are participants permitted to share? Who can resolve disagreements about the process?

Record leadership's account as leadership's account. Do not use it to pre-fill an employee's answer as fact.

1. Walk through a recent example. What started the work, and what did you receive?
2. Explain the actual steps. What did you do, in what order, and which tools did you use?
3. Describe a judgment call. What was unclear, unusual or dependent on an approval?
4. Explain the handoff. Who needed the result, and what made it usable for them?
5. Tell us what the official process leaves out. What workaround, repeated question or frustration matters?

Invite the participant to talk naturally or write. The prompts are context cues, not a script to recite. A person who does not know an answer should be able to say so.

When a person says “I check it,” ask what they check against and what makes a result acceptable. When they say “it goes to finance,” ask who receives it and what happens if information is missing. When they say “we always do it this way,” ask about the most recent exception.

Avoid leading questions such as “Would automation save you time?” Start with the work. Evaluate a proposed solution after the operating details are understood.

“I wish the system notified me” describes a possible improvement. “The system sends a notification” describes current behavior. The distinction matters when an interview is converted into a process map.

Use separate fields for reported current state, proposed change and supporting source. Preserve disagreement rather than asking AI to choose a single neat narrative.

Illustrative: “The request arrives by email. I check the part number in the inventory system. If the description does not match, I ask sales before giving an answer. Operations receives the confirmed list, but they send it back when the delivery location is missing.”

That explanation contains a trigger, input, system, action, exception and return loop. It still leaves questions: who in sales confirms the mismatch, and who owns completeness of the delivery details?

A useful interview does not eliminate uncertainty. It reveals which uncertainty deserves the next question.

With DutyGraph, the leadership context and known duties help shape private requests. Participants respond by voice or text and review the task descriptions drawn from their account. Advisors reconcile the responses and reserve live follow-up for the questions that need it.

Read about capturing tribal knowledge or explore the advisor program. For a client deliverable, pair these questions with the operations audit checklist.

For each gap, record who can clarify it and what evidence would help. Do not schedule another broad interview simply because some fields remain blank. Ask the smallest question that moves the review forward.

Discuss advisor-led process mapping.