What Is a Process Discovery Interview?

A process discovery interview is a structured 1:1 conversation designed to uncover how work actually happens in practice, not how it is documented or how management assumes it works.

Unlike generic stakeholder interviews, a process discovery interview focuses on:

• - Sequential steps and their order
• - Decisions and the criteria behind them
• - Systems and tools used at each step
• - Handoffs between people, teams, or systems
• - Exceptions, workarounds, and edge cases
• - Delays, bottlenecks, and points of rework

Why Start With 1:1 Process Discovery Interviews

Many teams jump directly into process discovery workshops. Workshops have their place, but high quality business process discovery almost always starts with individual interviews first.

The reason is straightforward. In group settings, social dynamics suppress detail. People are less likely to contradict a colleague, admit that the documented process is not what they actually follow, or describe the workaround they have been using for three years. In a structured 1:1 process mapping interview, that nuance emerges.

Specifically, 1:1 interviews work better for discovery because:

• - People speak more openly without colleagues or managers present
• - They describe real workarounds rather than the official version
• - They admit where documentation differs from reality
• - They explain edge cases and exceptions that never appear in process maps
• - In some organisations and cultures, people will not contradict an established practice publicly, but will describe reality privately

How to Run a Process Discovery Interview: Step by Step

Step 1: Start with a concrete trigger, not a broad question

Never open with "How does this process work?" It produces summaries, not detail. Instead, anchor the conversation in a real event:

• - "Walk me through what happens from the moment a new order is received."
• - "Take me through a typical claim submission from start to finish."
• - "What is the first thing you do when a priority escalation lands in your queue?"

Process discovery interviews work best when grounded in specific, recurring reality rather than hypothetical flows.

Step 2: Follow the process chronologically

Stay focused on sequence and resist the urge to jump ahead. At each step ask:

• - What do you do first?
• - What system or tool do you open?
• - What information do you need at this point?
• - What happens next?
• - Who do you interact with, and how?

Document the current state. Do not jump to improvements yet.

Step 3: Probe for variation and friction

The most valuable part of any process discovery interview is what goes wrong, not what goes right. Ask:

• - Where does work typically wait?
• - What causes rework or re-processing?
• - When does the process differ from the official version?
• - What do you do when the system behaves unexpectedly?
• - What is the most common reason a task gets sent back?

These questions surface operational risk, improvement opportunities, and the gap between documented and actual processes.

Step 4: Capture decisions, not just tasks

Business process discovery is incomplete without decision logic. A process without its decisions is just a checklist. Ask:

• - How do you decide whether to escalate this?
• - What criteria determine whether this needs approval?
• - Who has override authority, and when is it used?
• - What would cause you to handle this differently?

Common Process Discovery Interview Mistakes

Even experienced practitioners make these errors. Watch for:

• Accepting high-level summaries. "We process the request and send a confirmation" is not discovery. Push for step-by-step detail every time.
• Allowing the conversation to drift into complaints. Acknowledge the frustration and redirect: "That is helpful context. Can you walk me through exactly what happens at that point?"
• Ignoring rare exceptions. Edge cases often reveal the most important operational risks. If it happens even occasionally, document it.
• Talking more than listening. A well-run process discovery interview should feel like the interviewer is barely present, just guiding and probing.
• Starting with the documented process. Showing people a flowchart before they describe their experience biases the output toward the official version, not the real one.

When to Use a Process Discovery Workshop

Process discovery workshops are valuable, but for alignment rather than initial extraction. If you use a workshop before individual interviews, you risk producing a consensus view that papers over the variation and friction that actually matters.

Use workshops to:

• - Validate a draft process map built from interview findings
• - Reconcile conflicting accounts from different interviewees
• - Identify cross-functional bottlenecks that no single person can see end to end
• - Prioritise improvement opportunities as a group

Workshops are most effective when participants are reacting to something concrete rather than building from a blank board.

How to facilitate an effective process discovery workshop

1. Bring a draft process map. Never start from nothing. Use interview insights to anchor the discussion. A draft map makes disagreement visible and productive.
2. Encourage visible disagreement. When someone says "that is not how we do it in my region," that is a discovery signal. Pursue it, do not smooth it over.
3. Focus on end-to-end flow. Always ask: "What happens after your step?" Departments often have clear visibility into their own work and limited visibility into what comes before or after.
4. Separate discovery from solutioning. Workshops drift into redesign discussions quickly. Document current state first. Improvement comes second.

The Traditional Limits of Business Process Discovery

Manual process discovery has structural constraints that become more visible as organisations scale:

• - Scheduling and calendar coordination across multiple stakeholders
• - Workshop logistics and the cost of bringing the right people together
• - Limited participation, usually only senior or available staff rather than those closest to the work
• - Heavy dependency on experienced facilitators who are expensive and scarce
• - Manual note taking, synthesis, and diagramming after every session

There are also cultural constraints. In many organisations, individuals will not speak openly in front of colleagues or managers. They will not publicly contradict an established practice or admit that the documented process is not what they follow. This means group-heavy discovery approaches can produce polished, inaccurate representations of how work actually happens.

As transformation programmes scale across regions and business units, these constraints make discovery slow, expensive, and inconsistent.

How Famla Changes Process Discovery at Scale

AI powered platforms are changing what is possible in business process discovery, particularly for organisations running large or geographically distributed programmes.

Famla accelerates process discovery by:

• - Capturing structured workflow input from multiple stakeholders asynchronously, without heavy scheduling logistics
• - Allowing individuals to contribute privately, which surfaces the honest operational detail that group settings suppress
• - Generating process diagrams automatically from captured input and existing documentation
• - Performing structured process analysis grounded in Lean Six Sigma and Operational Excellence principles

The core principle of process discovery does not change: understand how work actually happens before you try to improve it. Famla accelerates and scales how organisations get there.