# Pilot Program

A bounded real-world implementation used to test whether a product, service, or operating model can deliver intended outcomes before broader rollout.

- Type: method
- Domain: Market & business
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/pilot-program/>)

## What it means

A pilot program is a small-scale deployment in a real operating environment. Unlike a test focused mainly on product defects, a pilot examines the wider system: workflows, staffing, training, integrations, governance, customer behavior, support, costs, and measurable outcomes. Its boundaries make experimentation and recovery manageable.

## Why it matters

Many adoption failures arise outside the interface. A solution may work technically but create unmanageable training, procurement, policy, or service burdens. A pilot helps teams learn about those interactions with limited exposure, producing evidence for redesign, implementation planning, or a decision not to scale.

## When to use it

Use a pilot before broad deployment when operational uncertainty, switching cost, safety, regulation, organizational change, or integration complexity is substantial. A pilot is less useful when the sample cannot resemble future conditions or when leaders have already committed to expansion regardless of results.

## How it works

1. Define the decision the pilot must inform, the theory of change, baseline, success measures, guardrails, scope, and stopping rules.
2. Select sites and participants that illuminate important conditions without claiming they statistically represent everyone.
3. Prepare training, support, data collection, governance, escalation, and a safe rollback or continuity plan.
4. Run for enough time to observe normal operations, exceptions, costs, outcomes, and adaptation rather than launch enthusiasm alone.
5. Compare evidence with the baseline and criteria, document context, then stop, revise, repeat, or scale deliberately.

## A practical example

A hospital pilots digital wayfinding in one outpatient building. The team measures late arrivals, staff interruptions, accessibility barriers, kiosk uptime, and navigation confidence against a baseline. It changes landmark wording and maintenance procedures before considering deployment across the campus.

## Where it breaks

Small pilots can miss rare failures, seasonal effects, and scale-dependent costs. Highly supported participants may perform better than future users, and local champions can mask weak processes. Results should therefore be interpreted in context rather than treated as proof that broad rollout will succeed.

## Common mistakes

- Running a miniature rollout without a learning question or baseline.
- Choosing only the easiest or most enthusiastic site.
- Scaling from positive anecdotes while ignoring operating cost and guardrails.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/pilot-program/#visualization-pilot-program>)

## Sources

1. [How the Beta Phase Works](<https://www.gov.uk/service-manual/agile-delivery/how-the-beta-phase-works>) — GOV.UK Service Manual · Government service-delivery guidance
2. [The Magenta Book: Central Government Guidance on Evaluation](<https://www.gov.uk/government/publications/the-magenta-book>) — HM Treasury · Government evaluation guidance

## Related topics

- [Beta Program](<https://wiki.soroush.uk/topic/beta-program/>)
- [Experimentation](<https://wiki.soroush.uk/topic/experimentation/>)
- [Customer Success](<https://wiki.soroush.uk/topic/customer-success/>)
