Skip to content

Lesson 4 of 6

Plan and Run a Demo: One Story, Their Data, Their Words

Decide what the demo is meant to settle, plan it on one page around a single story from the customer's own work, handle questions and requests without losing the thread, deal with a person nobody invited, and turn the feedback into actions.

7 minForward Deployed Engineering

After this lesson you will be able to plan a demo that leads to a decision, run it so that the customer's own people do the convincing, and leave with every piece of feedback written down against a name.

It is Thursday 11 June. The order history arrived a week ago, the head nurse sent her list on Tuesday, and you have the tool producing suggestions from Ashby Road's orders for May. The read-only key has not arrived. It was due yesterday. The demo goes ahead on the data you have.

Decide what the demo is for

A demo is not a tour of features. It exists so that the customer can settle one question. Write that question down first, because everything else in the plan follows from it.

For Larchmont the question is this: would the head nurse trust these suggestions enough to use them for four weeks? The operations director has already agreed to the pilot. The IT manager cares about access, not suggestions. The person whose judgement decides whether the pilot works is the one who places the order every Thursday.

The plan on one page

Demo plan, Thu 11 June, 14:00, 30 minutes

Question  Would the head nurse trust these suggestions enough
          to use them for four weeks?
Audience  head nurse, practice manager, operations director,
          IT manager
Data      Ashby Road's own orders for May
Story     The order of Thursday 28 May, twice: as the head nurse
          placed it, and as the tool would have suggested it.

 3 min    What we heard on 2 June, in their words
12 min    The 28 May order, side by side. Head nurse at the
          keyboard.
 5 min    The never-suggest list: no controlled drugs appear
10 min    Questions, and what happens next

If it breaks  Screenshots of every step, taken the day before.
Not shown     Settings, the other seven practices, anything
              that is not built yet.

Three choices in this plan are worth copying.

  • One story. The whole demo is a single order that the head nurse remembers placing. She knows what she ordered that day and why. She can judge the tool's suggestion against her own, line by line, without taking anything on trust.
  • Their data and their words. The screen shows Ashby Road's items under the names the practice uses. The opening three minutes repeat what Larchmont said on the discovery call: two hours every Thursday, two emergency orders in May. An audience that hears its own problem described accurately is ready to look at an answer.
  • A list of what is not shown. Deciding in advance what to leave out is what keeps a demo to thirty minutes.

Rehearse it once from start to finish, aloud, on the machine you will use. Then take the screenshots. A demo that fails in front of a customer is recoverable if you can carry on from pictures, and it is a lost meeting if you cannot.

In the room

Start with the result, not the explanation. Put the two orders side by side before you say how the tool works. Then hand over the keyboard.

Asking the head nurse to drive feels risky, and it is the most persuasive thing you can do. When you click through a prepared path, the audience watches a performance. When she scrolls through her own order and says "yes, I would have ordered that", the practice manager and the operations director hear it from a colleague.

While she reads, stay quiet. When she finds something wrong, do not defend it. Ask her to say more. Her corrections are the most valuable thing the demo will produce.

Answer it, park it or take it away

Questions and requests arrive throughout a demo, and each one can pull it off course. Sort each as it comes into one of three kinds.

  • Answer it now, if the answer is short and you are sure of it.
  • Park it, if it is outside what this pilot is for. Say so plainly and write it where everyone can see: "That is beyond these four weeks. I have noted it for the review at the end."
  • Take it away, if you do not know or if it needs somebody who is not present. Give a date: "I do not know. I will come back to you by Tuesday."

What you must not do is agree to something in the room because agreeing is the easiest way to move on. A promise made to get past an awkward moment is still a promise, and the customer will remember it.

One correction came early. The tool suggested seven syringes, and syringes come in boxes of a hundred. The head nurse was right, and the answer was short: "You are right. It should round up to whole boxes. I will have that changed by Tuesday." That became an action for you.

The person nobody invited

Ten minutes in, a fifth person joined: Larchmont's head of clinical services, who had heard about the demo from the practice manager. She watched in silence and then asked one question. "Who approves these orders? A nurse cannot order medicines on a tool's suggestion without a vet signing it off."

Nobody had an answer. The pilot as planned had the head nurse accepting suggestions on her own.

This is the cost of the question that was not asked in lesson 2. The head of clinical services is responsible for how medicines are handled across all nine practices. She has the standing to stop the pilot, and until this moment you did not know she existed.

How you respond matters more than the gap itself.

  • Do not treat her as an obstacle. She has just saved the pilot from a failure in its first week.
  • Thank her, and repeat the concern in her words, so that she knows it was understood.
  • Do not invent an answer. The decision is Larchmont's to make, not yours.
  • Turn it into an action with an owner and a date, and say it aloud: "Could you decide who approves each order during the pilot, by Monday 15 June?"
  • Add her to the status update from this week on.

She agreed to the date. Because the pilot cannot start without her decision, the action is marked as blocking it.

Turn feedback into actions

Before the day ends, put everything the demo produced into the log. Replace actions.csv with this version. It records what has been done since lesson 3 and adds four new actions.

id,raised,side,owner,action,due,done,blocks
A01,2026-06-02,us,FDE,Send notes and actions from the discovery call,2026-06-02,2026-06-02,
A02,2026-06-02,customer,Practice manager,Send May's order history for the two pilot practices,2026-06-05,2026-06-04,
A03,2026-06-02,customer,Head nurse,List the items that must never be suggested for reorder,2026-06-08,2026-06-09,
A04,2026-06-02,customer,IT manager,Get a read-only key for the practice system from its supplier,2026-06-10,,Pilot start
A05,2026-06-02,us,FDE,Demo reorder suggestions on May's order history,2026-06-11,2026-06-11,
A06,2026-06-04,customer,Operations director,Confirm the start date with both practice managers,2026-06-09,2026-06-08,
A07,2026-06-11,us,FDE,Round every suggestion up to whole boxes,2026-06-16,,
A08,2026-06-11,customer,Head of clinical services,Decide who approves each order during the pilot,2026-06-15,,Pilot start
A09,2026-06-11,us,FDE,Write the one-page guide for the pilot practices,2026-06-18,,
A10,2026-06-11,customer,Practice manager,Book 30 minutes of training at each pilot practice,2026-06-17,,
python actions.py 2026-06-11
Action log at the end of Thu 11 Jun 2026: 5 done, 5 open, 1 late
With Larchmont
  A04  due Wed 10 Jun  LATE 1d  IT manager: Get a read-only key for the practice system from its supplier [blocks: Pilot start]
  A08  due Mon 15 Jun           Head of clinical services: Decide who approves each order during the pilot [blocks: Pilot start]
  A10  due Wed 17 Jun           Practice manager: Book 30 minutes of training at each pilot practice
With us
  A07  due Tue 16 Jun           FDE: Round every suggestion up to whole boxes
  A09  due Thu 18 Jun           FDE: Write the one-page guide for the pilot practices

Read it the way the operations director would. Five actions are done and five are open. Two of the open ones block the start of the pilot, and one of those, the key, is already a day late. The demo itself went well: the head nurse said she would use the suggestions once they came in whole boxes. But the log shows that the pilot is in more danger this evening than it was this morning.

That is what tomorrow's status update has to say.

Key takeaways

  • A demo exists to settle one question. Write the question down before you plan anything else.
  • Tell one story from the customer's own work, on their own data, in their own words.
  • Let the person who will use it sit at the keyboard. Their trust decides the outcome.
  • Sort each request as it comes: answer it now, park it, or take it away with a date.
  • A concern raised by someone you did not expect is information. Thank them, write it down and give it an owner.
  • Feedback that is not in the action log by the end of the day is lost.

Try it

During the demo three more things were asked. The head nurse asked, "Can I still add an item that it did not suggest?" You know the tool, and the answer is yes. The practice manager asked, "Can it place the order by itself, without anyone pressing a button?" The IT manager asked, "Where is our order history kept, and who at your company can see it?" You are not certain of the answer. For each, decide whether to answer now, park it, or take it away, and write the sentence you would say. A good result answers the head nurse at once in one sentence, parks automatic ordering as outside a four-week pilot without calling it a bad idea and says where it has been noted, and takes the IT manager's question away with a named day for the answer, because a guess about where a customer's data is kept is worse than a short wait.

Official documentation

Ready to use this in a job?

Rolebound applies to matching roles for you.

Start now

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.

    Cookies on Rolebound

    We use necessary cookies to sign you in and keep the site working — those cannot be turned off. We would also like to set analytics and advertising cookies so we can see which pages help people get interviews and which adverts brought them here. Nothing optional is set unless you say yes, and you can change your mind at any time from “Cookie settings” in the footer. Read our Privacy Policy.