Is a pilot ready to scale?

A new process, tool or working method may have been tested by a small team. Its findings need to be considered alongside the size of the next commitment. Record the scope in which it worked, the support it required and the effects it had elsewhere in the business.

Define the decision before the pilot starts

What decision should the pilot inform? Continuing with the same team, adding another business unit and rolling out company-wide require different evidence. Tie success criteria to the intended decision.

Record the starting position, measurement method and observation period. Changing the acceptance criteria after seeing the outcome obscures what the pilot tested. If new learning justifies a change, retain both the original and revised definitions.

Make special conditions visible

Initial users may be volunteers or experienced staff. The supplier may provide additional support, a manager may check progress daily, or the test may run during a low-volume period. These conditions do not invalidate the result; they help define its scope.

List differences in:

• Experience between pilot participants and later users.
• Workload, product mix and number of exceptions.
• Training and day-to-day support.
• Temporary manual steps and corrections behind the scenes.
• Integration requirements and dependencies on other processes.

The Magenta Book addresses the need to assess whether findings can hold in other contexts. Magenta Book 2026.

Measure workload and errors alongside the main result

Suppose a new order-entry method reduces processing time. During the pilot, however, an experienced employee corrects errors outside the recorded workflow. Measuring entry time alone would understate the total work required.

Alongside the main outcome, examine correction time, error types, user support and work passed to subsequent processes. Check whether an apparent improvement could reflect the period, customer group or another change introduced at the same time. Without an appropriate comparison, avoid attributing the whole difference to the pilot.

Test the conditions needed for expansion

For each material pilot condition, record the state required at scale, the evidence supporting it and the test still needed. If daily support cannot continue, for example, a bounded follow-up trial with less support may be more informative than immediate expansion.

Define the scope of the next step and how it can be reversed or reduced. Changes involving technical safety, regulatory obligations or personal data require the relevant specialist review. A general pilot assessment does not replace those reviews.

Record a clear next decision

If the evidence is adequate, proceed within the defined scope. If a specific gap remains, describe the additional trial needed to examine it. If the outcome or conditions are unsuitable, change the approach or stop. Record the reason, owner and review date for each decision.

This gives the pilot report a continuing role: it records the evidence behind the next commitment and the conditions that management has accepted.

For a second opinion on the assumptions behind an expansion plan, Countersign provides a written review before commitment. Describe what your pilot tested and the decision that follows.