# Use a small credible example before a broad promise

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Use a small credible example before a broad promise

ID: MHC-D-RESEARCH-9085 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/use-a-small-credible-example-before-a-broad-promise

A bounded demonstration can replace argument with evidence.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- When stakeholders doubt a new approach and a full rollout would be expensive to reverse.

### Avoid when

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

### Explanation

Choose a representative slice that tests the disputed mechanism, not an easy showcase. Define what result would support, weaken or stop the broader proposal.

### Example

Instead of promising automation for every market, test one market with realistic exception volume and measure manual fallbacks.

### Check

The example tests the uncertainty that matters to the broader decision rather than merely looking impressive.

### Limits

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

### Evidence and sources

- 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. — RS-A0FA5CC4C12B8253. Reflection competes with execution time and should be tied to a concrete adaptation question rather than become an always-on ritual. (Abstract and highlights)
- RS-A0FA5CC4C12B8253: A Meta-Analysis of Team Reflexivity: Antecedents, Outcomes, and Boundary Conditions — https://doi.org/10.1016/j.hrmr.2024.101042

### Vedokrok editorial review

Test the disputed assumption with a bounded example

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

#### 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.

**Editorial takeaway:** 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.

#### Editorial evidence

- supports: GOV.UK recommends doing enough prototyping to test risky assumptions and then making a separate decision about further development. — RS-2C632AD389104352. Selected official passages inspected on 2026-10-05. This is practice guidance; the invented-record example is an editorial application, not a tested intervention. (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. — RS-0563603D99A737E6. 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. (Using code prototypes)
- RS-2C632AD389104352: How the alpha phase works — GOV.UK Service Manual — https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works
- RS-0563603D99A737E6: Making prototypes — GOV.UK Service Manual — https://www.gov.uk/service-manual/design/making-prototypes

Editorial version: 1.0.0 · evidence checked 2026-10-05 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/ask-for-the-smallest-approval-that-unlocks-learning
