How to run a workflow interview with the person who does the work
What to ask, what to watch, what to write down and which mistakes to avoid when you interview the person who actually does the job.
The person who does a task every day knows things nobody else does: which field in the form is always wrong, which customer needs a phone call, which spreadsheet is the real source of truth. Their manager usually knows how the work is supposed to go. The person doing it knows how it goes.
A workflow interview is how you get that knowledge out. Done well, it takes under an hour and tells you more than a month of reading process documents. This guide covers how to run one, whether you are a business owner looking at your own team or a consultant looking at a client.
Before the interview
Pick the right person. Choose someone who did the task in the last week. Not their manager, not the person who designed the process, not someone who did it two years ago. If two people do the task differently, interview both.
Set the expectation in writing. Send a short note a few days ahead. Say what the session is for, how long it will take, and what you need from them. Here is wording you can adapt:
We are trying to understand how [task] works in practice, so we can find what is slow or frustrating. This is about the work, not about how anyone is performing. Please bring a real, recent example open on your screen, and if there is a messy one, even better. It will take about 45 minutes.
The line about performance matters. People who suspect they are being evaluated, or that the interview is about replacing them, will describe the official process and hide the workarounds. Those workarounds are what you came for. Be honest about the purpose. If the goal is to remove repetitive work, say so, and explain that the interviewee's knowledge is what makes that possible.
Prepare a blank template. Before you start, set up a page or spreadsheet with the fields you need (shown below), so you are filling it in rather than inventing structure while the person talks.
Plan the timing. Forty-five to sixty minutes is enough for one workflow. Cover three in one sitting and you get the headlines of each and the detail of none.
The structure of the session
A sound interview has five parts.
- Warm-up (5 minutes). Ask about their role and how long they have done it. This is not small talk. You are learning where their expertise sits and letting them get comfortable.
- The walk-through (20 to 25 minutes). They share their screen and do a real example from start to finish. You mostly watch and ask short questions.
- The exceptions (10 minutes). Ask about what goes wrong.
- The numbers (5 to 10 minutes). Volume, time, waiting.
- Closing (5 minutes). Ask what you did not ask, and what they would change.
What to ask
Start open and get specific. Questions that work:
- "Walk me through the last one you did, from the moment it landed on your desk."
- "What happened right before you started?"
- "Why did you click that?" or "What are you looking for there?"
- "What do you do when [the price is missing / the customer changes the request / the approver is out]?"
- "Where do you copy information from one place into another?"
- "What do you check that is not written down anywhere?"
- "Who do you wait on? How long does that usually take?"
- "What do you do when it goes wrong, and what was the last time that happened?"
- "How many of these do you do in a typical week? What about the busiest week?"
- "What is the most annoying part of this?"
- "If you could change one thing, what would it be?"
Ask for the last time, not the usual time. "How do you usually handle this?" gets you the idealized version. "Tell me about the last time" gets you a real case with real details, and people have a harder time rounding off a specific memory.
Ask "why" gently. "Why do you do that?" can sound like criticism. "Help me understand what that step does" is friendlier and gets the same answer.
What to watch
The person's words are one source. Their screen and their hands are another, and they often disagree.
Watch for:
- Copy and paste. Every time information moves by hand between systems, there is an integration to build, and a place for errors.
- Tab switching. Count the number of systems they open. Five tabs for one task is a finding.
- Personal tools. A private spreadsheet, a notes file or sticky notes on the monitor all mean the official system is missing something.
- Hesitation. When someone pauses, they are making a decision. Ask what they are deciding and what they are looking at.
- Waiting. Time the work sits still, for an approval, a reply, a file.
- Things they skip. If they do not mention a step you would expect, ask. It may be automatic, or it may be skipped.
- Corrections. Retyping, undoing or fixing something means rework is built into the workflow.
Do not interrupt every few seconds. Let them get through a step, then ask about it.
What to write down
Use a consistent template for every interview so you can compare across people and workflows.
| Field | What to record |
|---|---|
| Workflow name | A plain label with a start and a finish |
| Person and role | Who you watched, and how long they have done it |
| Trigger | What starts it |
| Steps | In order, as they really happened, not as the manual says |
| Systems touched | Every tool and file |
| Manual handoffs | Each copy, paste, retype or message |
| Decisions | Each point where the person used judgment, and what they based it on |
| Exceptions | What goes off script, how often, and what they do |
| Volume | Per week, typical and busiest, as stated by the person |
| Time | Per run, typical and worst case, as stated by the person |
| Waiting | Who or what they wait on, and for how long |
| Pain points | In their words |
| Quotes | Short phrases that capture what is hard |
| To verify | Claims you need to check against records |
Two habits help. First, write down what you saw and what they said in separate columns. "She said it takes 20 minutes" and "I timed 34 minutes" are different facts and both are useful. Second, record decisions, not just steps. A step like "check the pricing sheet" is easy to automate. A decision like "knock off 10% if it is a repeat customer, unless the job is over a certain size" needs a rule written down, and the person may never have said it aloud before.
If the person agrees, record the screen and take the transcript. Ask first, and say what the recording is for and who will see it.
After the interview
Within a day, while it is fresh:
- Clean the notes and fill gaps while you remember them.
- Send a short summary to the person and ask them to correct it. This catches misunderstandings and shows them their input was taken seriously.
- Check the claims. The person said they handle 40 a week. Count the records. They said it takes 20 minutes. Time a few. A good interview produces numbers you then verify.
- Compare across people. If two people do the same task in two ways, ask why. One of them may have a better method.
Common mistakes
- Interviewing the manager instead of the worker. You get the policy and miss the practice.
- Leading questions. "Don't you find the CRM clunky?" invites agreement. "What is the CRM like to use for this?" does not.
- Offering solutions during the interview. The moment you say "we could automate that," the person starts defending the step or worrying about their job. Collect now and propose later.
- Taking stated times at face value. People round and forget the bad days.
- Only hearing the happy path. Always ask for the messy one.
- Talking too much. If you are speaking more than a quarter of the time, you are not learning. Silence after an answer often gets a better second answer.
- Skipping the follow-up. An interview that is not checked against records is an anecdote.
- Making it feel like an audit. Sit beside the person, not across from them. Thank them for their time and tell them what happens next.
A short pre-interview checklist
- The person did the task in the last week.
- They have a real, recent example ready, ideally including a messy one.
- They know the purpose and that it is not a performance review.
- A template is open and you know which records you will check afterward.
- There is time set aside afterward to clean notes and send a summary.