Heuristic

Test the disputed assumption with a bounded example

A useful demonstration answers a question. A polished demonstration can leave the important question untouched.

About 2 min read

Before you use it

Use when
  • When stakeholders doubt a new approach and a full rollout would be expensive to reverse.

Keep this limit in mind

  • Influence should remain evidence-based and transparent. Do not hide material risks, manufacture urgency or manipulate stakeholders into consent.

Current editorial reading

Choose the smallest informative slice

Name the uncertain assumption and choose a case that could expose its failure, including the awkward conditions relevant to that question. Before trying it, state what result would support, weaken or stop the proposal. In an illustrative file-conversion trial, include invented records with missing and unusual fields, rather than only tidy examples. Report failures and manual work as well as successes.

Say what the example did not test

A prototype that clarifies a workflow does not establish production security, capacity or demand. GOV.UK’s alpha guidance focuses prototypes on risky assumptions; its prototype guidance separates experimental code from production-quality code. Apply that distinction to the question at hand, without treating one successful slice as approval for a wider rollout.

Take it with you

Record the question answered, the conditions tested and the important conditions still untested. Keep risks visible rather than using the demonstration to pressure people into consent.

Sources and evidence (2)

What we checked

Supports

GOV.UK recommends doing enough prototyping to test risky assumptions and then making a separate decision about further development.

Selected official passages inspected on 2026-10-05. This is practice guidance; the invented-record example is an editorial application, not a tested intervention.

How the alpha phase works — GOV.UK Service Manual · Opening guidance; Focus on testing your riskiest assumptions; Deciding whether to move on to beta

Challenges

Prototype code can be assumed to meet production security and performance requirements.

The official guidance explicitly distinguishes prototype code from production code. It does not establish the performance of any particular pilot. This mapping replaces the original reflexivity citation, which did not directly support pilot design.

Making prototypes — GOV.UK Service Manual · Using code prototypes

Editorial sources (2)

Editorial version 1.0.0 · Evidence checked 2026-10-05

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingTest the disputed assumption with a bounded example

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

A 2024 meta-analysis concluded that team reflexivity can support team performance but that benefits vary with team design conditions, and participation-supportive leadership is related to reflexivity through psychological safety.

Reflection competes with execution time and should be tied to a concrete adaptation question rather than become an always-on ritual.

A Meta-Analysis of Team Reflexivity: Antecedents, Outcomes, and Boundary Conditions · Abstract and highlights

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details