Build to Learn brief
Name the decision pressure, unknown, candidate slice, stakeholders, and evidence needed.
Artifact library
A field-ready collection for creating the records RDD depends on: briefs, loop logs, delivery baselines, Reality Checks, and evidence ledgers.
The collection includes print-designed HTML files, PDF exports, and a README. The HTML files can also be opened in Word when a team wants editable working copies.
Mini preview
Name the decision pressure, unknown, candidate slice, stakeholders, and evidence needed.
Capture observed behavior, discrepancy, accepted behavior, rejected alternatives, and next move.
Record the evidence-backed boundary between Build to Learn and Build to Deliver.
Challenge accepted behavior against architecture, security, data, operations, and compliance.
Trace accepted behavior, decisions, rejected alternatives, checks, and production evidence.
Use when the team needs to name the uncertainty a working candidate must expose.
Use during sessions where stakeholders operate the candidate reality.
Use when a slice is ready to cross from learning to engineering.
Copyable artifact structures
Decision to improve:
Unknown:
Stakeholders required:
Candidate reality slice:
Constraints:
Evidence needed:
Decision after loop:
Observed behavior:
Discrepancy found:
Accepted behavior:
Rejected alternative:
Changed assumption:
Open risk:
Next loop or Freeze Gate:
Scope accepted:
Evidence carried forward:
Reality Checks required:
Known risks:
Architecture questions:
Production handoff owner:
Build to Deliver readiness:
Template collection
The download includes printable HTML and PDF versions of the five templates. Use them in workshops, delivery reviews, or early Reality Loop sessions.