Pilot One Customer Promise Before Commissioning a Transformation Programme

A transformation programme can become large before the organisation has proved that it understands the problem. Workstreams multiply, the roadmap acquires dates and the team begins reporting activity. Yet the central assumption, that the proposed changes will improve something customers value, remains untested.

A focused pilot can reduce that uncertainty. Choose one important customer promise and test the connected changes needed to deliver it more reliably. The purpose is to learn enough to make a better investment decision, not to manufacture a small success that justifies a programme already approved in principle.

Choose a promise with a visible consequence

The pilot should address a real customer outcome. In a hypothetical premium retailer, that might be a dependable collection appointment: the order is ready, the colleague understands the purchase and the customer knows what will happen. That is more useful than a pilot described only as “improving collaboration”.

Define where the pilot begins and ends. Include the handovers that determine the outcome, even if they cross departments. Excluding the booking or fulfilment stage because it belongs to another team may make the pilot easier to manage while removing the source of the problem.

Choose a setting that is manageable but credible. A quiet site with unusually experienced staff may help develop the process, but success there should not be mistaken for evidence that it will work across the group at peak demand.

Establish the starting position

Record how the promise is currently delivered, where it fails and what employees do to recover. Include the effort involved, not just whether the customer eventually receives a satisfactory result. A process that succeeds through repeated management intervention may not be ready to scale.

Decide what you expect the change to improve and what must not deteriorate. Faster collection should not create more errors or transfer extra work to another team without acknowledgement. The pilot needs a view of the complete trade-off, rather than a single favourable measure.

Use enough evidence to inform the decision, while recognising the limits of a small test. Avoid presenting a short trial as a precise forecast of annual financial return.

Test the operating conditions as well as the idea

Specify the changes in information, responsibility, capability and capacity. Who will act differently? What will they need? What happens when the usual person is absent? A pilot that relies on constant attention from the project team may show that an idea can work, but not that the organisation can sustain it.

Ask participants to record friction and exceptions. Protect space for honest feedback, including evidence that the proposed solution is making work harder. Suppressing that evidence to preserve momentum defeats the purpose of testing.

Make the next decision explicit

Agree a review point and possible outcomes before launch: continue, revise, expand or stop. Expansion should depend on what has been learned about the customer outcome and the resources required, not simply on whether the pilot met its launch date.

This is a practical application of FUSION: connect the promise, the people and the operating design in a bounded piece of work. A useful pilot does not remove every uncertainty. It makes the next commitment more informed and exposes what the wider business will need to change.

Illustrative photograph; pictured people and businesses are not case studies in this article. Photo source: Pexels.