Lesson 2 of 6
Run a Discovery Call: Prepare, Ask, Listen and Play It Back
Send an agenda the day before, open the call so that everyone knows why they are there, ask open questions and let the customer talk, say back what you heard, and close with actions that each have an owner and a date.
6 minForward Deployed Engineering
After this lesson you will be able to prepare and run a discovery call that leaves you with facts, the customer with confidence, and everyone with a short list of actions.
The first call with Larchmont Vets is on Tuesday 2 June. Four people from Larchmont will give you 45 minutes. Together that is three hours of their working time, and it is the only time you will have all of them together before the demo. A call like this is won or lost before it starts.
The day before: send an agenda
An agenda tells people why they are invited and lets them come prepared. Send it the working day before. Keep it short enough to read on a phone.
Subject: Tuesday's call on stock ordering: agenda
Purpose Understand how ordering works today at the two pilot
practices, so that the pilot tests the right thing.
When Tue 2 June, 10:00 to 10:45
5 min Who is here, and what we want from the call
20 min How the weekly order is done today
(head nurse, practice manager)
10 min What would make the pilot a success
(operations director)
5 min Access to the practice system (IT manager)
5 min Actions, owners and dates
To bring Nothing to prepare. If last week's order is to hand,
it would help to look at it together.Look at what it does. The purpose line is about their work, not your product. Each part names who will speak, so the IT manager knows that five minutes are theirs and the rest is not. The largest share of time goes to the people who do the ordering. And the last five minutes are kept for actions, which is the part that is lost first when a call runs over.
The first five minutes
Open by saying three things: who you are, what the call is for, and what will happen afterwards. For example: "I am the engineer who will set up the pilot. Today I want to understand how ordering works now. I will not be showing the tool. You will have my notes and a list of actions by the end of today."
That last promise matters. People speak more freely when they know that what they say will be written down and sent back for correction.
Then ask if you may take notes, and ask each person what they want from the call. Their answers often tell you more than the agenda does.
Ask, then stop talking
The middle of the call belongs to the customer. Your part is to ask good questions and listen to the answers.
- Ask open questions. "How do you decide what to order?" brings a description. "Do you check the shelves?" brings a yes.
- Ask about the last time. "Talk me through last Thursday's order" brings what really happened. "How does ordering usually work?" brings the official version.
- Ask one question at a time. Two questions in one breath get an answer to the easier one.
- Follow up on anything vague. When you hear "sometimes we run out", ask "When did that last happen, and what did you do?"
- After an answer, wait. A pause of two or three seconds feels long to you. It is often when the other person adds the detail that matters.
- Do not solve anything yet. When the head nurse describes a problem, the temptation is to say "our tool does that". Write the problem down and keep listening.
A useful check for yourself: if you have spoken for more than a quarter of the time, you are presenting, not discovering.
What Larchmont said
Here is what the call produced, in the order it came.
- The head nurse places the order every Thursday afternoon. She walks the shelves with a printed list and orders what looks low, "and a bit extra of whatever we ran out of last time". It takes her about two hours.
- The practice manager said Ashby Road ran out of a common item twice in May and had to pay for next-day delivery both times.
- The head nurse said some items must never appear on a suggested order. Controlled drugs are ordered under a separate procedure, and she would not trust a tool that listed them.
- The operations director said the pilot succeeds if there are fewer emergency orders than in May and the weekly order takes less of the head nurse's time.
- The IT manager said the practice system is run by its supplier. A read-only key has to be requested from the supplier, and that "usually takes about a week".
Notice the words in quotation marks. Write down the customer's own phrases where you can. "About a week" is a claim from memory, not a promise from the supplier, and your notes should keep that difference visible.
Play it back
With ten minutes left, stop asking and say back what you heard. "Let me check I have this right. The order goes in on Thursday afternoons and takes about two hours. Ashby Road ran out twice in May. Controlled drugs must never be suggested. And the pilot counts as a success if there are fewer emergency orders than in May and the order takes less time. Have I missed or misheard anything?"
A playback does two jobs. It catches your mistakes while the people who can correct them are still on the call. And it shows the customer that they were listened to, which does more for trust than anything you could have presented. On this call the practice manager corrects one point: Mill Lane orders on Wednesdays, not Thursdays. Without the playback you would have found that out in the first week of the pilot.
Close with actions
Use the last five minutes to read the actions aloud, each with a name and a date, and ask each owner to agree to the date.
- The practice manager will send May's order history for both practices by Friday 5 June.
- The head nurse will list the items that must never be suggested by Monday 8 June.
- The IT manager will get a read-only key from the supplier by Wednesday 10 June.
- You will send the notes today and demo the suggestions on May's orders on Thursday 11 June.
A date that the owner has said aloud in front of colleagues is far more likely to be kept than one you put in an email afterwards.
The question that was not asked
The call ended on time and everyone left with something to do. One thing went wrong, and nobody noticed. The question from lesson 1, "Who else will need to agree to this?", was not asked. The time ran out, and the four people present seemed to be everyone.
They were not. Lesson 4 shows what that costs. For now, take the habit from it: write that question at the top of your own copy of every agenda, and do not end a first call without asking it.
Key takeaways
- Send a short agenda the day before, with a purpose, timings and the name of whoever speaks to each part.
- Ask about the last time the work was done. People describe a real Thursday more accurately than a typical one.
- Ask one question at a time, then stop talking. The useful detail often comes after a pause.
- Play back what you heard before the call ends, so that mistakes are corrected while everyone is still there.
- Close with actions, each with one owner and one date, read aloud.
- Do not present your product on a discovery call. You are there to learn.
Try it
Prepare a discovery call for the opticians from lesson 1, who want an appointment tool tried at one shop for a month. Write a 45-minute agenda with a purpose line and timings, and five open questions, at least two of which ask about a particular recent day. A good result has timings that add up to 45 minutes, leaves the last five minutes for actions, contains no question that can be answered with yes or no, and includes the question "Who else will need to agree to this?"
Official documentation
Written with AI and checked automatically. Nobody has run these steps by hand, and tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.