Kept AI, Inc.Visit Website →
← Back to blog

Managers’ Process Interview Questions: Four Stages That Catch Gaps

October 12, 2026
Managers’ Process Interview Questions: Four Stages That Catch Gaps

Ask SMEs to tell the process story before you ask them a single checklist question, then convert what they tell you into anchor points, a SIPOC, and a simple map. This article gives you a categorized bank of process interview questions, grounded in expert-elicitation research and ISO documentation guidance, plus the short workflow we use to turn an interview into a usable process map with the decision logic intact.

TL;DR:

  • Match documentation depth to risk: high risk compliance processes need detail, while low stakes weekly tasks may need three bullets and a named owner.
  • Ask what threshold changes a decision, when the process last deviated from routine, and who receives each output; these answers expose judgment and handoff risks.
  • Have multiple SMEs compare accounts side by side; this checks errors and reveals differing assumptions about steps treated as standard.
  • Keep the first map to five to nine boxes, use a single page for one clear owner, and reserve swimlanes for repeated handoffs between roles.
  • Validate frequent tasks through live observation and rare procedures through simulation; rely on recall only when neither option is practical, because it is least reliable.
Kept
Keep process knowledge in the workflow
Kept uses guided conversational AI to turn employees’ process descriptions into structured workflows, preserving context that can be lost when people leave.
Explore Kept

Table of Contents

Before you schedule a single conversation, decide how deep the documentation needs to go. ISO guidance on documented information is explicit that organizations should maintain information "to the extent necessary," not exhaustively. That single phrase should shape your entire prep. A high-risk compliance process earns a detailed write-up; a low-stakes weekly task might need three bullet points and a named owner.

Once scope is set, pick participants deliberately. You want the person who actually does the work, not just their manager, plus anyone who hands work to or receives it from them.

  • Identify the primary SME and at least one upstream or downstream handoff partner.
  • Set recording and consent rules in advance: opt-in only, explain storage and deletion, and confirm who reviews the output before it's finalized.
  • Prepare a simple worksheet with space for a "process story" and a column for anchor points, so notes stay structured as you listen.

Pro Tip: Send the worksheet template to the SME a day ahead so they can think through tricky steps before the interview, not during it.

Eliciting tacit knowledge: verbal, textual, graphic, discussion

Most process interviews fail for the same reason: they jump straight to "what are the steps," which produces a tidy but incomplete list. Research on expert knowledge elicitation describes a better sequence, one that moves an expert from loose memory to a structured, checkable model.

  1. Verbal first. Ask the SME to narrate the whole process as a story, start to finish, before you interrupt with specifics. This surfaces their mental image of the work, including the parts they'd otherwise skip as "obvious."
  2. Textual anchor points next. Name the key states, thresholds, or decision moments mentioned in the story, and ask what data or reasoning sits behind each one.
  3. Graphic elicitation. Have the SME sketch or plot the anchor points on a rough timeline or flow. Pay attention to inflections and odd shapes rather than smoothing them into a clean line, since irregularities usually mark where judgment gets applied.
  4. Discussion phase. When you have more than one SME, compare their verbal, textual, and graphic accounts side by side.

The MIT study notes that this verbal-to-graphic sequence, followed by a discussion phase, increases error checking and reveals where multiple experts hold different assumptions about the same process. That discussion step is often where you discover a step everyone assumed was standard but that one team quietly handles differently.

Categorized question bank: story, decisions, exceptions, handoffs

Organize your questions by the artifact they feed, not by the order they feel natural to ask. Each category below maps to something you'll build later: a flow, a decision log, or a RACI.

Opening story prompts get the full arc on the record before you drill into detail.

  • "Walk me through this process from the moment it starts to the moment it's considered done."
  • "What triggers this process, and how do you know it's finished?"

Decision-capture questions force the SME to name their anchor points and the reasoning behind them, rather than letting judgment stay implicit.

  • "At what point do you decide to escalate, and what tells you it's time?"
  • "If two requests look similar but you'd handle them differently, what's the difference you're actually reacting to?"
  • "What number, document, or signal makes you stop and check before continuing?"

Exception and variant prompts reveal the nonstandard paths that formal documentation usually omits entirely.

  • "What's the last time this process didn't go the usual way, and what did you do instead?"
  • "Is there a version of this you only run once a quarter or in an emergency?"

SIPOC-aligned prompts gather the inputs, outputs, suppliers, and tools you need for a governance-ready artifact. APQC's process mapping guidance recommends pairing interview narrative with a lightweight SIPOC early, rather than waiting until the map is finished.

  • "What do you need in hand before you can start, and who provides it?"
  • "Which systems or tools do you touch at each stage?"

Handoff and validation clarifiers close the loop on timing and ownership.

  • "Who receives your output, and what do they do with it next?"
  • "If you were out for two weeks, what would the person covering for you most likely get wrong?"

Pro Tip: Save "who's accountable here" questions for the end. Asking them too early can make SMEs defensive about steps they've never had to justify before.

Convert interview output into maps and controlled documentation

Raw interview notes are not a process document. Converting them takes a short, repeatable workflow.

  1. Extract anchor points from your notes: every decision, threshold, and exception the SME named.
  2. Draft a high-level map first, five to nine boxes, before attempting any detail.
  3. Fill in a SIPOC and a RACI using the inputs, outputs, and handoff answers from the interview.
  4. Annotate the map with exceptions and the reasoning behind each decision point, not just the decision itself.

On map type: a single-page flow works for processes with one clear owner, while a swimlane map earns its complexity only when multiple roles hand work back and forth. APQC advises starting high-level and drilling down only where a step hides real variation.

On how much to keep: ISO's standard is documenting "to the extent necessary," so your checklist for "enough" should ask three things:

  • Does this document capture every decision point an untrained replacement would get wrong?
  • Does it name the exceptions that occur regularly enough to matter?
  • Would a reviewer sign off that nothing load-bearing was left out?

A quick reviewer pass against those three questions catches most gaps before the document goes live. For a deeper walkthrough of workshop steps, see our guide to making process mapping work.

Validate and iterate: observation, simulation, and follow-up

A single interview, however well run, gives you one person's account. Validation closes the gap between what was said and what actually happens.

Choose your observation mode based on frequency. Direct observation guidance distinguishes three levels of accuracy: real-time observation for frequent tasks, simulation or role play for rare ones, and perception-based recall only when neither is practical, since it's the least reliable of the three.

  • Watch the process happen in real time whenever it runs often enough to schedule around.
  • Ask the SME to simulate or walk through rare procedures step by step when you can't catch a live instance.
  • Run a short workshop where two or more SMEs compare their maps side by side, which is the discussion phase in practice.

Pro Tip: During observation, record only what you see and save your questions for afterward. Interrupting mid-task changes the timing you're trying to measure.

Build in a follow-up interview and a version number on every map, so updates don't silently overwrite the reasoning behind an earlier decision.

Why decisions matter more than steps

Why decisions matter more than steps — overview diagram

Most process documentation fails quietly, not because the steps are wrong but because the reasoning behind them never made it onto the page. A checklist tells a new hire what to click. It doesn't tell them why a careful person would sometimes click something else. That gap is where knowledge actually lives, and it's the part interviews are suited to capture, if you ask for it directly and record it with the SME's opt-in consent, not as an afterthought.

If you're starting from zero, resist the urge to document everything. Start with a small number of processes or a few subject matter experts, and expect a usable first pass within a few weeks of effort.

— Anthony

Kept as a solution: capturing the conversation, not just the checklist

Everything in this guide works with a notebook and a recorder, but it takes real discipline. We offer a conversational AI platform that runs guided interviews, listens for anchor points and exceptions in the SME's own words, and turns conversations into structured workflows without flattening the reasoning behind each decision.

Kept

  • Interviews can stay opt-in, with workspace-level controls over who can view, review, or delete what's captured.
  • Both personal and business workspaces support verbal-to-structured conversion, so individual contributors or entire teams can document workflow in this way.
  • Captured context and judgment support onboarding, helping replacements inherit the "why," not just the "what."

If you want to see how this plays out for a specific handoff, our expert handoffs use case walks through it. When you're ready to try it with your own team, our pricing page covers both Kept for You and Kept for Business.

FAQ

What makes a good process interview question?

A good question asks for a decision or a threshold, not just a step, since steps are easy to observe but reasoning is not. Start with an open "tell the story" prompt, then follow up on anything that sounds like a judgment call.

How long should a process interview take?

Most process interviews run well within an hour once you've scoped the process ahead of time and prepared your worksheet. Complex processes with several handoffs may need a follow-up session rather than a longer single sitting.

How much should we document per ISO 9001?

ISO's guidance on documented information directs organizations to maintain information "to the extent necessary" to support the process and demonstrate it runs as planned, not to document every detail. In practice, that means prioritizing decision points and known exceptions over routine, self-evident steps.

How do we handle employees who struggle to describe their own process?

Ask for a recent specific instance instead of a general description, since most people recall a concrete case more easily than an abstract routine. Pair the verbal walkthrough with a short observation session if the gap persists, since watching the task often surfaces steps the person forgot to mention.

Can conversational AI replace a human interviewer?

A guided conversational tool can run the structured interview and capture answers in the SME's own words, which is what platforms like Kept are built to do. It works best as a consistent first pass, with a human reviewer confirming the resulting map before it becomes the documented process.

Sources