THE CHALLENGE

A kiosk pilot is a learning protocol.

Installing hardware is not enough to validate an experience. The pilot must connect the customer journey, operational readiness, error cases and field observations to a clearly stated decision about what comes next.

1. Define the pilot question

The pilot must answer a precise hypothesis about the journey, operations or organization. Without an initial question, every observation may seem important without guiding the next step.

IN PRACTICE

State what the pilot should help you understand: use of the journey, catalog readiness or exception handling.

2. Select a representative location

The chosen location should reflect a meaningful part of the target operation while remaining manageable with support. Document its particularities so a local lesson is not generalized.

IN PRACTICE

Select a location whose flows, team and environment match the intended deployment.

3. Walk through every customer-facing step

Review the experience from arrival to confirmation, including comprehension, accessibility, error correction and the ability to get help.

IN PRACTICE

Test finding a product, editing the basket, going back and resuming after hesitation.

4. Prepare the catalog and payments

Labels, options, availability and payment rules shape the journey. An inconsistency here can be mistaken for a kiosk defect.

IN PRACTICE

Review the catalog as a customer, then verify the expected statuses across ordering, payment and operational handling.

5. Prepare the team and operation

The pilot changes the questions teams receive and how certain orders arrive. Roles, instructions and support paths must be known before go-live.

IN PRACTICE

Rehearse how the team should handle a request for help, an unavailable item and an interrupted order.

6. Organize observation

System events do not replace field observation, and impressions do not replace facts. The pilot should combine both without turning every comment into an immediate conclusion.

IN PRACTICE

Bring journey events, team feedback and customer observations into one shared review framework.

7. Prepare the close-out decision

The pilot ends with a decision: proceed, adjust, extend observation or stop. Criteria must be known in advance, and remaining reservations must be recorded explicitly.

IN PRACTICE

Hold a review connecting every initial hypothesis to observations, proposed changes and the deployment decision.