Show how it works: a service demonstration without a staged miracle
A service demonstration should show the work and the conditions for using it. Separate the example, the presenter's help and working functionality so the client knows what they are evaluating.
Article language: English

In this article
At the demonstration, everything works. The presenter chooses the right file, types the perfect question and opens the correct result straight away. The client sees a smooth sequence but cannot tell how much preparation happened off camera. Will the service cope with ordinary material? What will a person do, and what will a tool do? When will someone need to ask for more information?
A good demonstration makes the actual work and conditions of use recognizable. It might show a working capability, a prototype or a service performed by people. Tell the audience which one they are watching. A striking presentation becomes troublesome when it blurs the difference between a prepared example and a capability the company has confirmed in practice.
Choose the question the demonstration should answer
Suppose a studio presents a new inquiry journey on a B2B website. A visitor chooses a use case, describes a need and receives information about the next step. The studio's client wants to know whether this journey will help its audience understand the offer and provide useful information. This is a fictional example, not a claim about an existing deployment or sales results.
Shape the demonstration around that question. You do not need to present every screen or setting. What matters is identifying the use case, the information needed for an inquiry and what happens after submission. If the presentation covers only a concept, describe the back-end operation accordingly.
The Cabinet Office's Test, Learn and Grow playbook of 19 October 2026 (English) describes a show and tell as showing completed work, explaining what was learned and answering questions. It is a way to collaborate in public administration, not a ready-made sales meeting script. The distinction between the result and knowledge of how it came about is useful.
In our example, the demonstration can answer how a visitor knows which option to choose, what information is required and what the confirmation means. That is more than moving a cursor through three attractive screens. The team should be able to explain the basis for each step and reveal where the solution still needs testing.
Ordinary material reveals more conditions
Choose a case similar to what the audience would actually bring. It might contain an incomplete description or a question that needs clarification. The aim is not to sabotage the demonstration. It is to see how the service handles an ordinary lack of information instead of showing only data arranged by the form's author.
Explain what was prepared in advance. If the presenter knows the route and has a set of answers ready, the client should understand the role of that help. In a service that prepares material, a specialist may carry out part of the investigation. That is valuable work in its own right. There is no need to conceal it behind the impression that everything appears after one click.
Label sample data clearly. Do not call it a client's completed project or a real result. In public materials, keep those labels on screens and in recordings as well. An oral explanation before a meeting may not reach someone who later sees a single screenshot.
Show the checks alongside the result. If a draft needs review before use, include that step in the presentation or make clear where it belongs. Measures focused on the number of results can hide a similar difference, as explained in the article on work measures (in Polish). Ten generated items do not automatically mean ten results ready to use.
With an incomplete inquiry, show where a request for clarification appears. In our prototype, the visitor may not yet know which service option they need. If the form requires them to choose one name without explanation, the demonstration should reveal that condition. A different contact route or information that helps begin a conversation without a finished specification may be needed.
It is also worth explaining how the example was chosen. If it is the simplest option, the viewer should know that limitation. If it includes an ordinary exception, explain what that is. There is no need to pretend it is a representative sample of the whole service. The aim is to explain honestly what this fragment can teach before a broader check.
Explain what is connected to real operation
In a form prototype, a button can lead to a confirmation screen without sending a message. That is useful for discussing the journey if its status is named. It does not prove that email or subsequent handling works. The client should know which parts are integrated and which merely represent planned behavior.
Likewise, a demonstration with a prepared result can show the form of the material but not how long it took to produce. To assess delivery speed, you need a different test. Do not assign the smoothness of the demonstration a meaning it did not test. Honest labeling helps focus the conversation on the question the example was actually prepared to answer.
Record the required conditions: the kind of data, the presenter's role, access to tools and the scope of checks. This need not be a technical specification displayed to the client in place of the service. Give enough information to understand what the company does and what the recipient must provide. A technical detail matters when it affects their decision.
If there is a material difference between the demonstration and the offer, correct both materials. The approach in the guide to correcting published information (in Polish) is useful when an earlier video or description suggested a working capability without sufficient basis. A new paragraph on the website may not explain the discrepancy to someone watching the old recording.
If something stops during the demonstration, name the current state. You can return to the last confirmed step or show a prepared result, explaining the substitution. Do not present that material as the result of the action just performed. The viewer can still assess the form of the result, but should not infer a successful live sequence from it.

In a recording, preserve information about shortcuts when they matter to the assessment. Edited-out waiting time or a manual correction can change the picture of the work. Not every edit needs a detailed log. The audience should nevertheless know whether they are watching the complete sequence, selected stages or an animation of planned behavior. The presentation format should not itself add capabilities to the service.
Watching and trying independently provide different information
Nielsen Norman Group's guide to usability testing (English) describes a participant performing tasks while a researcher observes their behavior. The material was last reviewed in July 2026. This research method is distinct from a demonstration led by the solution's author. Watching a skilled demonstrator alone does not establish that the audience can use it independently.
If the client wants to test understanding of the contact journey, prepare a separate trial with suitable participants and a task. In our example, a person is given a need to address, not a list of buttons to click. Their actions then show whether the labels and information help them find the right step.
Do not turn that trial into a hidden lesson. When the facilitator continually suggests what to choose, the result describes use with support. That can also be useful, but its scope must be preserved. Human support can be part of a service requiring consultation. It has a different meaning for a self-service form.
A short first-impression test of a website (see the guide to the five-second test (in Polish)) answers yet another question: what a visitor recognizes at first. It cannot replace completing a whole task. A demonstration, recognition of the first screen and an independent trial can support one another if the team knows what it learned from each.
Record when the facilitator had to help and what the help concerned. Pointing to a button means something different from explaining the service itself. The former may reveal difficulty finding an action; the latter, difficulty understanding the offer. That distinction helps select a change to the content or layout instead of summarizing the whole trial as “the client needed support”.
If the aim is to understand a particular condition, ask the participant to describe the next step in their own words. They may navigate the screen correctly while expecting a result broader than the offer. In our example, submitting an inquiry does not automatically mean a quotation or the start of delivery. The demonstration should preserve that meaning even when the sequence is smooth.
Show work on the website that the client can evaluate
A well-prepared excerpt of a demonstration can explain a complex service. Show the input material, a selected action and the result in its context of use. The description should make the company's contribution visible. If the client or a partner performs part of the task, retain that information. Also show the client's preparation and effort that made the sequence possible: data to gather, choices and necessary agreements (see the article on the client's time and effort (in Polish)). That way the demonstration supports evaluation rather than creating an illusion of completeness.
Aeneia Design helps design how a service or product is presented on a website. A starting point can be an ordinary case and a question the audience must resolve before making contact. The form of the demonstration should reflect the actual scope and label a concept, example and working functionality according to their status.
A B2B case study, as discussed in the guide to B2B case studies (in Polish), should instead concern work that was actually completed, with an appropriate basis. Do not substitute a demonstration called a client story. Both forms can be useful, but each should explain what it confirms. An example sequence helps explain operation, while a documented project shows specific experience.
For the evidence behind claims in an offer (discussed in the article on evidence for offer claims (in Polish)), check whether the demonstration supports the exact wording used. A prototype video can explain a planned journey. It is not enough to prove that complete order handling already works. The more specific the description, the easier it is for the audience to distinguish a useful example from a promise requiring further checking.
Add an explanation to a website video that remains understandable outside the sales conversation. The viewer should recognize the task, sample data and state of the solution without a presenter's introduction. A screen caption or short description beside the recording can preserve an important condition that was only said aloud in the meeting.
Also check whether the case still matches the current offer. After a scope change, an old video may remain convincing while describing an outdated journey. Assign an owner to the material and identify an event that triggers review. The publication date alone does not show whether the conditions were checked later.
For material intended for several audiences, choose the view to suit the question. A service buyer may need to see the result; the future person doing the work on the client's side may also need to see data preparation. Different excerpts of the same sequence can be shown with a shared indication of scope. Not every role needs to watch the whole workshop to recognize the condition that concerns them.
Prepare a short answer to what the demonstration has not yet tested. For a contact prototype, that could include actual delivery and handling of a message. For an example piece of material, it could be repeatability with another kind of data. This boundary should help plan a further trial and refer to something concrete rather than create a long list of generic caveats.
End with a recognized next step
After the demonstration, ask what the audience understood and what still needs assessment. Do not treat a compliment on appearance as confirmation of the whole solution. The result may be acceptance of a direction, a request to test a condition or a need to see another case. It should indicate what work is needed next.
If a referring partner leads the demonstration, prepare the same scope of explanations for them. In a B2B referral partnership (see the article on referral partnerships (in Polish)), the presenter should not expand the promise simply because the presenter wants to make a sale easier. The audience should understand what it saw, what it needs to use the service and what the company actually offers. Then even a modest demonstration can support a concrete decision about further work.







