Translating a showroom demonstration into online kit choices

In a showroom, an adviser can explain a kit tangibly: this is the base, this component connects to it and this addition suits your use. Online, that direct explanation is missing. A kit configurator therefore needs to translate the logic of the demonstration into understandable choices. Do not just copy the parts list; investigate what the adviser explains during the conversation.

Observe the sequence of the advice

Ask an adviser to demonstrate a typical set and note which questions come first. These often concern the intended use, available space or existing equipment. Specific components come afterwards. That sequence can be a useful starting point for the online journey. The website does not need to recreate the exact conversation, but it does need to gather the same essential information.

In a fictional showroom for video workstations, an employee demonstrates a camera setup with lighting and mounting equipment. They first establish where the customer wants to work, then choose the components. An online configurator that immediately shows twenty mounting products skips the most important advice step. A recognisable question about the setup can make the choice much easier to understand.

Also note the gestures and comparisons that carry the explanation. The adviser may point to the space beside a desk or show how an arm moves. Online, that information may need a clear image or short explanation. A product photo alone does not always show the characteristic that was convincingly visible in the showroom.

Make implicit product knowledge explicit

Ask why the adviser offers some components and not others. Sometimes it is a firm compatibility rule, sometimes a practical recommendation and sometimes a personal preference. Those three meanings need different treatment online. A recommendation should not become a mandatory choice without explanation. A necessary condition must not be presented as an optional extra.

For a digital product experience the customer needs to understand what the configurator does. Explain the reason for an important limitation in plain language. For example, say this mount fits the chosen position, instead of only option unavailable. The explanation helps the customer reassess their situation if the result is unexpected.

Check the translation with several advisers. One demonstration may contain personal habits that do not apply to the whole range. Have differences discussed on their merits before recording them in software. The configurator needs to support the agreed product advice, rather than accidentally making one employee’s approach permanent.

Assess the online journey with a customer who did not see the demonstration

Use a fictional setup and ask a new customer to work through the configurator. Ask which application they think they are putting together and why the chosen components belong in it. Compare the result with the showroom explanation. The two journeys may differ in form, but they need to convey the same important product meaning.

Also ask a showroom adviser to use the online summary to explain the proposal back. If they need to ask additional questions that the configurator should already have answered according to its design, information is missing. That finding may lead to a better question, clearer explanation or an explicit route to personal advice.

Using a showroom demonstration as a starting point lets you explore how Yindle Kit Configurator could be applied. Specific product rules may make additional development necessary. The aim is an online choice that makes the quality of the advice recognisable, even when the customer has not yet held the components.

A showroom demonstration can continue with Yindle Kit Configurator. Keep online choices tied to real products and explain which information still needs an advisor.

Previous insight
Next insight

Start with your question

Where does your team get stuck?

Your first enquiry does not need to be a technical brief. Tell us which systems you use and where work gets stuck. Together we discuss what is possible and which step you can take next.

Discuss my project