Lesson 2 of 6
Discovery: Who to Talk To and What to Ask
Choose the four kinds of people to talk to, ask about real days so that the answers are facts, and sort what you hear into facts, claims and unknowns.
5 minForward Deployed Engineering
After this lesson you will be able to plan the first conversations with a customer, ask questions that bring out what really happens, and write down what you heard in a form you can check.
Who to talk to
The person who brought you in is seldom the person who has the problem. For almost any piece of customer work you need to hear from four kinds of people.
- The sponsor asked for the work and will judge whether it succeeded. At Harrow this is the operations director.
- The people who do the work live with the problem every day and know details nobody else does. At Harrow this is the order desk, six people who take the orders.
- The owner of the systems knows what can be read, what can be changed, and how long a change takes. At Harrow this is an outside IT contractor.
- The person who can say no has a rule that your build must not break. It is often someone in finance, security or legal. At Harrow this is the finance director.
If you speak only to the sponsor you will build the sponsor's idea of the problem. If you never find the person who can say no, you will meet them in the week you try to go live.
Ask about last Tuesday
Ask people what usually happens and you get a tidy summary with the awkward parts left out. Ask what happened on one real day and you get facts.
So do not ask the order desk "how do you handle email orders?". Ask "can you show me the first email order you dealt with this morning, and what you did with it?". Then ask what happened to the one after it, and to the worst one of the week. Follow one order from the moment it arrives to the moment the truck is loaded.
A few questions work with almost any customer:
- Can you walk me through the last time this went wrong?
- What happens next, and who does it?
- How many of these are there in a day?
- How do you find out that one has gone wrong, and how long after?
- What have you already tried?
- If this were fixed, what would you notice first?
- Is there anything a new tool must never do?
Listen for numbers, for names of systems, and for the words "it depends". Each "it depends" is a case your build will meet.
What Harrow told you
You speak to all four. This is what each one says.
The operations director: Harrow takes about three hundred orders a day. Customers choose Harrow because an order placed in the morning is delivered the same day. An order entered into the order system after 12:00 goes out the next day. Complaints about late deliveries have been rising, and the director believes email orders are the cause.
The order desk: orders arrive by email, through a web portal and by phone. Portal orders go into the order system by themselves. Email orders are read by a person and typed in by hand. On Monday mornings the inbox runs two or three hours behind. Mistakes happen when a product code is mistyped, or when a customer uses its own name for a product. A few large customers send emails that look exactly the same every time, because their purchasing systems send them automatically.
The IT contractor: the order system can import a file of orders, which is how portal orders get in. Any change to the order system itself takes months. An export of past orders, with the channel and the times each order was received and entered, is easy to produce.
The finance director: every order is checked against the customer's credit limit when it is entered, and nothing may skip that check. Order emails contain agreed prices, so they may be processed only by services that IT has approved.
Facts, claims and unknowns
Write up what you heard on the same day, and sort it into three lists.
A fact is something a person told you from direct knowledge, or something you saw. "Portal orders need no typing" is a fact: the order desk does the work and knows.
A claim is something believed and not yet measured. "Email orders are the cause of the late deliveries" is a claim. It may well be true, and the director has not counted. Treat claims with respect and check them.
An unknown is a question nobody could answer. At Harrow there are several. How many orders miss the 12:00 cut-off, and through which channel did they arrive? How many orders have to be corrected after entry? How much of the email comes from the few customers whose emails always look the same? Does a file import run the credit check?
The unknowns are the most useful list. Each one is either a question for a named person or something to measure, and the build you propose will depend on the answers.
Ask for evidence before you leave
Do not end a discovery conversation with only notes. Ask for something you can examine.
- From the IT contractor: an export of the last two days of orders, with the channel, the customer, the time received, the time entered, and whether the order was later corrected.
- From the order desk: ten real order emails, including two from the large customers and two that were hard to read.
- From the operations director: permission to sit with the order desk for an hour on a Monday morning.
Asking for evidence does two things. It gives you data for the next lesson. It also shows the customer early how you work: you will check before you build, and you will ask for their time and their data. A customer who cannot give you an export in the first week will not be able to give you access in the fourth, and it is better to learn that now.
Key takeaways
- Talk to four kinds of people: the sponsor, the people who do the work, the owner of the systems and the person who can say no.
- Ask about a real day, such as last Tuesday, and not about what usually happens.
- Sort what you hear into facts, claims and unknowns; a claim is something believed and not yet measured.
- Leave every conversation having asked for evidence: an export, examples, or an hour watching the work.
Try it
In plan.md, under "Evidence", write three short lists for Harrow Building Supplies: facts, claims and unknowns, using what the four people said in this lesson. Then write the three questions you would still ask, and beside each one the person you would ask. A good result has at least two claims that data could confirm or overturn, and no question that is addressed to "the customer" in general.
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.