Ask for a working demonstration
Updated
BeginnerWhat you'll learn
~11 min- Ask for a demonstration set against how the work is done today, with the written plan first
- Compare a prototype with an operational system using four plain tests
- Decide between a vendor demo and a demonstration on your own data
You leave this lesson with: two sentences you can send today, one asking for the baseline comparison and one asking for the written plan first.
The request
Send this to the team or the vendor:
Show it working against how we do the work today. Show me the written plan before you build anything.
The first half asks for a baseline (Lesson 2.1: the current workflow, measured and sourced). Without one, a demonstration can only be admired. With one, you can compare time, errors and rework.
The second half gives you a plan you can read before any work is spent. AI-Powered Development (Module 10 Lesson 1, a separate training in this series) shows how the team prepares the written plan. You only need to ask for the result.
If the team has no baseline yet, the minimum to record is the elapsed days from request to result, how often work is redone, and the staff time it takes, each with its source and the period it covers. Until that exists, record the comparison as unavailable (Lesson 2.1: measure over an agreed period before funding).
What a returned plan looks like
A company operations group asked for a tool to sort incoming customer requests. This is the plan structure that came back, before anything was built:
PLAN: examine an approved export of closed customer requests.Suggest categories and owners; staff check the suggestions.Compare the suggestions with staff decisions and report disagreements.BOUNDARY: no live-system changes and no personal data.OPEN QUESTION: who decides when staff disagree about a category?You do not need to judge the technique. Read it as a manager: it names its steps, says what it will leave alone, and states what it cannot answer itself. Ask: “Who answers the open question, and who confirms that the proposed work stays within the stated boundary?” A plan that lists no boundary and no open question has left both for you to find.
Prototype or operational system
A demonstration shows a prototype. Do not read it as an operational system.
| Prototype | Operational system | |
|---|---|---|
| Data | A sample, often prepared | The live data, with all its flaws |
| Users | The builders | Staff who did not build it |
| Failure | Someone restarts it | Someone is responsible and has a route to fix it |
| Review | Informal | Security, privacy and accuracy review that matches the consequence |
A prototype is valuable evidence. It is not yet a service.
Before any decision, ask which column the demonstration sits in. A prototype on a sample answers whether the idea works. It does not answer who will run it on live data, who will fix it when it fails, or which review applies, and those answers belong in the funding decision.
A company finance team sees a vendor demo that classifies invoices in seconds. The vendor offers a contract this quarter, and the team lead asks you to approve it.
- Approve a contract with an early exit clause, and test the tool on live invoices in its first month.
- Decline for now, since the current process works, and look again next budget year.
- Before signing, ask the vendor to repeat the demo on a sample of your own invoices, and ask the team to bring their current error rate and handling time first and to name who would run it on live invoices and which review applies.
Pick one before you open What happens.
ℹWhat happensclick to expand
- Approve with an early exit clause: It limits the money at risk and gets the tool onto real invoices sooner. But the test starts after the commitment and the setup work, and with no recorded error rate or handling time, the first month has nothing to be compared with.
- Decline for now: It keeps a process that works and spends nothing, but it leaves unexamined a tool that might have held up on your invoices.
- Repeat the demo on your own invoices: It costs sample preparation and review time before signing, and returns a result on your own invoices that can be compared with today’s, so the answer can be yes, revise or not now.
Choice 3 holds up, because results from your own data have a baseline to be measured against before any contract is signed. A passing sample informs the decision; routine use is authorized later, at a review that confirms the conditions Lesson 5.1 sets (user acceptance, staff training, a support owner and an operating budget).
Which request gives a leader the most useful evidence from a demonstration?
Key takeaway
- LEADERSHIP DECISION
- Require every proposed pilot to show a baseline comparison and a written plan before funding.
- IMMEDIATE ACTION
- Send the two-sentence request to the team and ask for the current handling time and error rate for the workflow.
- SUCCESS MEASURE
- Handling time on a sample of your own data, against the measured current handling time, with error rate no higher.