Lesson 1 of 6
Who You Are Talking To: The People, What Each Needs and When
Meet the customer that runs through the course, list the people on their side and what each one needs from you, see what a discovery call, a demo and a status update are each for, and agree a rhythm of contact in the first week.
5 minForward Deployed Engineering
After this lesson you will be able to list the people a customer project depends on, say what each one needs from you, and set up a rhythm of contact that keeps them informed without wasting their time.
A forward deployed engineer (FDE) builds software inside a customer's organisation. The code is half of the work. The other half is conversation: finding out what is needed, showing what you have built, and keeping people informed while you build it. Projects with sound code fail on the second half more often than on the first. This course covers that half, and it follows one small project from the first call to a piece of bad news.
The case
One made-up customer runs through every lesson. Larchmont Vets is a group of nine veterinary practices. Each practice orders its own medicines and supplies once a week, by hand. Your company sells a stock tool that reads what a practice has on the shelf and what it has ordered before, and suggests the next order.
Larchmont has agreed to try the tool at two practices, Ashby Road and Mill Lane, for four weeks. The pilot is planned to start on Monday 22 June. You are the FDE who has to make that happen. It is now the last week of May, and you have met nobody at Larchmont yet.
The people
Before the first call, write down who you will be dealing with. An account manager at your company has given you four names. Use roles in your notes at first, because roles tell you what a person is likely to care about.
Person Cares about Needs from you
----------------------- ------------------------- -------------------------
Operations director cost of stock, emergency is it on track, and what
(the sponsor) orders, a clear result do you need from me
Practice manager, the practice running what changes for staff,
Ashby Road without disruption and when
Head nurse, placing the weekly order will it save time, and
Ashby Road without mistakes can it be trusted
IT manager access and security exactly what access you
want, and for how longThree roles in this table appear in almost every customer project, and they are rarely the same person.
- The sponsor pays for the work and will judge whether it succeeded. Here that is the operations director.
- The user will work with what you build every week. Here that is the head nurse. If she does not trust the suggestions, the pilot fails, whatever the sponsor thinks.
- The gatekeeper controls something you cannot work without. Here that is the IT manager, who must arrange access to the practice system.
Each of them needs something different from you. The sponsor does not want a description of the screens. The head nurse does not want a summary of the budget. Sending everybody the same message means most of them read something that is not for them, and they stop reading.
Three conversations
Most of your contact with a customer falls into three kinds. Each has one purpose.
- A discovery call is for understanding. You are there to learn how the work is done today and what would count as success. You talk less than they do.
- A demo is for a decision. You show something working so that the customer can decide something: to go on, to change direction, or to stop.
- A status update is for trust. It tells the sponsor where things stand and what is needed, so that nothing reaches them as a surprise.
Trouble starts when the purposes are mixed. A discovery call that turns into a sales pitch teaches you nothing. A demo with no decision attached is a show. A status update that hides a problem costs trust on the day the problem comes out.
Set the rhythm in the first week
Customers do not complain that an engineer told them too clearly what was going on. They complain about silence followed by a surprise. Agree a rhythm at the start, write it down, and keep to it even in weeks when there is little to say.
What Who When
---------------------- ------------------------- -----------------------
Discovery call all four Tue 2 June, 45 minutes
Notes and actions everyone on the call the same day
Demo all four Thu 11 June, 30 minutes
Written status update operations director, every Friday by 15:00
copied to the others
Urgent news operations director, by the day it is known
phone, then in writingThe last line matters most. It says that bad news does not wait for Friday. Lesson 6 depends on it.
Rules that hold in all three
A few habits apply to every conversation in this course.
- Write it down the same day. What is not written down will be remembered differently by each person who was there.
- Give every action one owner and one date. "We will look into it" is not an action.
- Use the customer's words. If they say "the Thursday order", you say "the Thursday order", not "the replenishment cycle".
- Say what you do not know. "I do not know yet, and I will tell you by Friday" is a good answer.
- No surprises. The sponsor should never learn something important about the project from somebody other than you.
Who is missing?
A list of four names from an account manager is a start, and it is seldom complete. Somebody approves spending. Somebody is responsible for how medicines are handled. Somebody at Mill Lane does the job the head nurse does at Ashby Road. Any of them may have a say that nobody has told you about.
So one question belongs in every first conversation: "Who else will need to agree to this before it goes ahead?" Keep it in mind. In the next lesson the call goes well, and that question is the one that does not get asked.
Key takeaways
- A project at a customer is carried by a few people. Write down who they are, what each cares about and what each needs to hear from you.
- A discovery call is for understanding, a demo is for a decision, and a status update is for trust. Do not mix their purposes.
- Agree in the first week how often you will be in touch, with whom and in what form, and then keep to it.
- The person who pays, the person who uses the thing and the person who can block it are often three different people.
- Ask early who else has to agree. A person you have not met can stop the work late.
Try it
Write the people table for a different case. A chain of five opticians wants your company's appointment tool tried at one shop for a month. Name at least four people on the customer's side by role. For each, write what they care about and what they need to hear from you. A good result includes someone who pays, someone who uses the tool every day and someone who controls access to a system, gives each a different need, and names at least one person you would ask about because nobody has mentioned them yet.
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.