Stakeholder and Employee Process Interviews for SMEs

Process interviews help you understand what people know about the work that is not visible in a procedure or system report. Employees know where customers get stuck, where approvals slow down, which forms are confusing, and which exceptions happen so often they are no longer really exceptions. Stakeholders know what they need from the process and whether the output is useful.

The direct answer is this: interview the people who do the work, manage the work, supply inputs to the work and receive outputs from the work. Ask about reality, variation and consequences. Keep the tone curious and practical. The purpose is to improve the process, not judge the person.

Who to Interview

Interview group	What they can reveal	Example question
People doing the work	Actual steps, shortcuts, missing information and frustration points.	What usually makes this task harder than it should be?
Process owner or manager	Standards, targets, constraints and performance concerns.	What outcome are you accountable for?
Internal customer	Whether outputs are complete, timely and usable.	What do you need from this process to do your work well?
Supplier of inputs	Why inputs arrive incomplete or late.	What would help you provide better information earlier?
External customer	Experience, expectations and moments of dissatisfaction.	Where does the experience feel unclear, slow or unreliable?

Interview Flow

Stage	Purpose	Example
Open	Set safety and purpose.	We are studying the process, not reviewing individual performance.
Describe	Let the person explain normal work.	Walk me through what happens from the moment you receive the request.
Probe	Explore exceptions and pain.	What happens when information is missing?
Evidence	Ask for examples.	Can you show a recent case where this went smoothly or badly?
Improve	Invite practical ideas.	If you could change one thing safely, what would it be?
Close	Confirm understanding.	Here is what I heard; did I miss anything important?

Question Bank

What starts the process for you?
What information do you need before you can do the work well?
Where do you usually wait?
What mistakes or rework happen most often?
Which step depends on one person’s knowledge?
What do customers or colleagues complain about?
What workaround do people use because the official process does not fit reality?
What would make the process easier without creating new risk?

Do and Do Not Matrix

Do	Do not
Ask open questions and listen for patterns.	Interrogate people as if they caused the problem.
Separate facts, opinions and assumptions.	Treat the loudest opinion as proof.
Ask for examples and evidence.	Rely only on memory or general statements.
Include people across the process.	Interview only managers.
Summarise findings without personal blame.	Quote sensitive comments in a way that damages trust.

Panith Illustrative Case Study

Panith Illustrative Case Study: A small construction contractor has delays between site surveys and customer quotes. The owner thinks the estimator is too slow. Interviews reveal that survey notes often arrive without photos, measurements or access constraints. The estimator spends time calling site staff to reconstruct missing details.

The interview process changes the diagnosis. The bottleneck is not only estimator speed; it is input quality from the site-survey process.

Worksheet: Process Interview Template

Field	Notes
Interviewee role
What part of the process they touch
Normal steps described
Inputs they need
Outputs they create or receive
Common delays
Common errors or rework
Improvement ideas
Evidence to verify

Common Mistakes

Interviewing only senior people.
Asking leading questions that confirm your assumption.
Ignoring quiet employees who know the real work.
Failing to distinguish rare exceptions from frequent patterns.
Collecting complaints without tracing them back to process causes.

Self-Assessment Questions

Who would you interview first for a process that crosses sales, operations and finance?
How would you ask about mistakes without creating defensiveness?
What evidence would you request after an interview?
How would you handle two people describing the same process differently?

References and Further Reading

Next Lesson

Continue with Lesson 9: SIPOC and High-Level Process Mapping.

SEO improvement pass: expanded depth and practical application

Expanded Practical Guidance

Strong process interviews are structured but not scripted to death. Start with the person’s role in the process, then ask them to walk through a real recent example. Good interviewers listen for differences between the normal path, the difficult path and the workaround path.

The best questions avoid blame. Instead of asking “Who caused the delay?”, ask “What usually has to be true for this step to move smoothly?” That question helps people talk about inputs, systems, rules and handoffs.

Interview Risk Controls

Risk	How to manage it
People become defensive	Explain that the work system is being studied, not individual performance.
Managers dominate the conversation	Interview frontline staff separately where appropriate.
Opinions replace evidence	Ask for recent examples, records or screenshots.
Confidential comments damage trust	Report patterns, not sensitive personal remarks.

Practical Next Step

After three to five interviews, compare the stories. If people describe the process differently, that difference is itself a finding. It usually means the process is not standard, not visible or not owned clearly.

Visual Learning Aids

The following visual structures translate this lesson into practical management tools. They are designed for SME use and can be copied into a workshop, team meeting or improvement plan.

1. Process Diagram

Input	Work system	Output	Owner	Main risk
Customer need or business trigger	Stakeholder and Employee Process Interviews applied to the business process	Reliable customer or internal outcome	Process owner	Rework, delay or quality failure

2. Flowchart

[Start] Trigger received
   |
   v
[Understand] Work is mapped
   |
   v
[Decide] Bottleneck or waste is identified
   |
   v
[Act] Improvement option is selected
   |
   v
[Review] New way of working is tested
   |
   v
[Improve] KPI review confirms next action

3. Decision Tree

Is the issue clear and evidence-based?
- No: clarify the problem, collect examples and involve the people closest to the work.
- Yes: does it affect customers, cost, quality, risk or growth?
  - No: document the learning and monitor lightly.
  - Yes: assign an owner, choose a practical method, define success measures and review progress.

4. Priority Matrix

	Low effort	High effort
High impact	Do first: quick operational improvement	Plan carefully: strategic improvement project
Low impact	Do only if it removes friction	Avoid or defer unless required for risk, compliance or learning

5. Implementation Timeline

Stage	Typical SME timing	Output
Diagnose	Week 1	Problem statement and evidence
Design	Week 2	Chosen method, owner and measures
Test	Weeks 3-4	Small pilot or controlled trial
Standardise	Weeks 5-6	Checklist, SOP, dashboard or decision rule
Improve	Monthly	Review notes and next improvement action

6. Illustrative Performance Chart

Illustrative example: replace these sample scores with real business data before using the chart for decisions.

Measure	Current score	Target score	Visual gap
Clarity	2/5	4/5	2 blocks to 4 blocks
Ownership	2/5	5/5	2 blocks to 5 blocks
Measurement	1/5	4/5	1 block to 4 blocks
Consistency	3/5	4/5	3 blocks to 4 blocks

7. Maturity Model

Level	Maturity stage	What it looks like	Next improvement
1	Informal work	Informal work is visible in the way the business manages this topic.	Documented process
2	Documented process	Documented process is visible in the way the business manages this topic.	Measured process
3	Measured process	Measured process is visible in the way the business manages this topic.	Controlled process
4	Controlled process	Controlled process is visible in the way the business manages this topic.	Continuously improved process
5	Continuously improved process	Continuously improved process is visible in the way the business manages this topic.	Sustain and refine through periodic review

8. Comparison Table

Dimension	Current-state process	Future-state process
Decision basis	Experience, urgency or individual memory	Evidence, agreed criteria and visible trade-offs
Accountability	Unclear or dependent on the founder	Named owner with clear responsibility and review rhythm
Measurement	Discussed only when something goes wrong	Tracked using cycle time, first-time-right rate, cost and customer impact
Scalability	Works only while the team is small	Can be taught, repeated and improved as the business grows