Discovery interview questions for forward-deployed engineers
Updated
Short answer
Good discovery questions are specific, recent, and about what happened, not what should happen. Ask “Walk me through the last time this went wrong,” not “What are your pain points?” Interview the people who do the work, not only the sponsor. Check every claim against the data. Never open with automation or replacing staff, because people stop telling you the truth.
Principles
- Ask about the last time, not the usual time. People describe the procedure when you ask how things work. They describe reality when you ask about yesterday.
- Separate the sponsor's fix from the sponsor's problem. “Hire two more people” and “add AI” are solutions. Ask what result they want.
- Go to the front line. The people who answer the phones and do the jobs know where the time goes.
- Follow the handoffs. Delays hide where work moves between people or systems.
- Check claims against data. An interview gives you a hypothesis. The data confirms or rejects it.
- Protect trust. If staff think you are there to replace them, they protect themselves. Talk about the work, not about headcount.
Question bank
For the sponsor
- What made you start this project now?
- If this works, what number changes, and by how much?
- What have you tried already? What happened?
- Who else must agree before anything changes?
For the people who do the work
- Walk me through the last request you handled, from start to end.
- What did you have to wait for?
- Who do you ask when the system does not have the answer?
- What do customers ask you most often?
- What do you do that is not in any procedure?
For managers in the middle
- Where do requests come to you that should not?
- What do you check by hand every day?
- What report do you trust least?
For the data
- Which requests take the longest? What do they have in common?
- What share of contacts are about the same question?
- Where do records show a gap between two steps?
Mistakes that end the conversation
- Asking a yes-or-no question when you need a story.
- Asking a general question, such as “Any other issues?” You get a general answer.
- Suggesting the answer inside the question.
- Talking about replacing roles or reducing headcount.
- Interviewing only the sponsor.
Practice discovery with characters who hold things back
In FDE Workbench, eight characters at a fictional plumbing and HVAC company share some facts freely. The other facts come out only when you ask a specific, well-aimed question. Talk about replacing staff and they stop talking. After the readout, each character you interviewed rates how you treated them, and that rating counts in your score.
Questions
What is a discovery interview?
It is a structured conversation with a customer or a member of their staff to learn how the work really happens and where the real problem is, before you propose a solution.
How many people should I interview in discovery?
Interview at least the sponsor, one manager, and two or more people who do the work. Stop when new interviews no longer change your process map.
What is the best first discovery question?
Ask the person to walk you through the last time they handled the process, from start to end. It gives you real steps, real waits, and real workarounds.