Protocol

Ask for a bounded trial with explicit permissions

A small budget is not permission to use any data. Name the trial’s limits before asking someone to approve it.

About 2 min read

Before you use it

Use when
  • When stakeholders resist a large commitment but useful evidence could be gathered with a smaller reversible step.

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

Make the request checkable

State the learning question, activity, time and spending limit, and the people, systems and data involved. Identify the decision-maker for each required permission. For an illustrative workflow mock-up, request two days of design work with invented records if those can answer the question. State that real-data access, external sharing and production changes remain outside the request.

Keep the next decision separate

Record what was actually authorized and what result will trigger a stop, revision or request to expand. Do not begin a dependent action while its permission is missing. Calling work a sandbox or prototype grants no access; deleting a prototype cannot recall information already disclosed. GOV.UK guidance supports bounded assumption testing and distinguishes prototypes from production systems. The permission checklist here is an editorial planning aid, not a claim that a prototype source grants authority.

Take it with you

Before acting, can you identify the authorized activity and its boundary? A useful small trial preserves required checks and honest risk disclosure.

Sources and evidence (2)

What we checked

Supports

A prototype can focus on a limited set of uncertain assumptions before a separate development decision.

Selected official passages inspected on 2026-10-05. The request format is an editorial adaptation; no universal approval process or effectiveness estimate is inferred.

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

Calling an activity a prototype establishes its readiness for live use.

The guidance distinguishes prototype and production conditions. It does not authorize data access or sharing. This replaces the unrelated reflexivity evidence mapping; actual permissions must come from the responsible owner and applicable process.

Making prototypes — GOV.UK Service Manual · Using code prototypes; Sharing 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 readingAsk for a bounded trial with explicit permissions

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