Loop 032
The promise-to-proof loop
A product review that compares claims in marketing, documentation, demos, and AI answers with current evidence, then fixes or narrows unsupported promises.
Ready-to-use prompt
Copy the loop
List every customer-facing promise [product] makes in marketing, documentation, demos, and AI answers. Compare each promise with current product behavior and evidence, then label it proven, partly proven, misleading, unsupported, outdated, or missing evidence. Fix or narrow the riskiest mismatch and rerun the affected check. Repeat until no high-risk unsupported promise remains. Ask before changing production or public copy. Return the promises, evidence, fixes, and decisions needed.
Verify / stop
Every high-risk customer promise is supported, narrowed, or waiting on an explicit decision.
Each promise links to current evidence, and every high-risk mismatch is fixed, narrowed to what the product can prove, or clearly approval-gated.
Context and guidanceWhen to use it, steps, safety notes, and related loops
Use this when
Use this when what a product says it does may no longer match what it actually does across marketing, documentation, demos, support answers, or the live product.
How to run it
- List the promises customers can see and rewrite each one as a concrete expectation, such as a feature working, a limit being honored, or an answer being accurate.
- Compare each expectation with current product behavior, code, tests, documentation, examples, logs, or other direct evidence; do not guess.
- Rank mismatches by the harm they could do to customer trust, then fix the riskiest one or narrow the public promise to what the product can prove.
- Rerun the same check and repeat until no high-risk unsupported promise remains, progress is blocked, or the next action needs approval.
Why it works
This turns a vague question—can customers trust what we say?—into a list of promises that can each be checked. Fixing one risky mismatch at a time keeps the product and its public explanation aligned without turning the audit into an uncontrolled rewrite.
Implementation note
Evidence can include live product behavior, tests, documentation, logs, screenshots, or reproducible examples. A promise may be supported, narrowed, or removed; the product does not always need to change. Production changes and public publication still require approval.