Back to Publications
PUB-017/Whitepaper/Aug 2026

What we will not claim from a beautiful prototype

A public evidence framework for separating live experiences, prototypes, concepts, simulated data, measured outcomes and future validation work.

Business value

Clear evidence boundaries help partners decide what to fund, test or govern next. They protect trust while allowing a prototype to demonstrate real product and workflow potential.

Evidence and measures
  • - Live, Prototype, Concept and Internal demo are treated as different maturity states.
  • - Interface evidence is separated from outcome evidence such as safety, clinical impact, efficiency or return on investment.
  • - Every public record should state its data boundary, measurement conditions, limitations and next validation step.
Research Questions
  1. 01What can a prototype prove about an interaction or workflow?
  2. 02Which claims require a governed pilot or independent evaluation?
  3. 03How can evidence boundaries remain visible without making research material feel defensive?
Method
  1. 01Label the maturity of each artefact before describing its capability.
  2. 02Separate simulated scenarios, interface behaviour and measured operational outcomes.
  3. 03Record data sensitivity, assumptions, known limitations and the next decision the evidence should support.
Evidence
  1. 01Simam research note: What we will not claim from a beautiful prototype.
  2. 02NHS Operations Twin public R&D record, explicitly independent and based on simulated data.
  3. 03Current Simam case-study labels across live, prototype, concept and internal-demo work.
Next Steps
  • Add evidence-boundary labels to every future case-study record.
  • Create a one-page partner checklist for prototype review.
  • Use the framework before publishing any performance, safety or business-impact number.
Related live work
Evidence boundaries research note ->NHS Operations Twin R&D record ->
Related Whitepaper records