TECHNICAL EXPLANATION BRIEF
Audience and roles:
What they already know:
What they need to understand or decide:
User or operating consequence:
Mechanism in three to five steps:
Terms that must be defined:
Evidence: source, period, sample and measurement definition
What the evidence does not establish:
Proposal and alternatives:
Trade-off or failure condition:
Decision requested, owner and next evidence:
Appendix references:

SIX-SLIDE NARRATIVE — ADAPT TO YOUR PROJECT
1. Consequence: what the current behavior means for the user or operation.
2. Mechanism: what changes, shown as a short labeled sequence.
3. Evidence: the result and what was actually measured.
4. Trade-off: what the change makes harder or leaves unresolved.
5. Next step: the bounded action and evidence needed to continue.
6. Decision: who should choose what and when the decision will be reviewed.

ILLUSTRATIVE REPORTING EXAMPLE
Consequence: users currently wait on a page while a report is created.
Mechanism: accept request -> store pending job -> process job -> show completed result.
Distinction: request accepted is not report ready.
Practice data only: 90 of 100 requests finish within 60 seconds; 10 take longer.
Interpretation: 90% finish within 60 seconds. This is below the illustrative 95% target. It does not establish an improvement over the current system because no baseline is supplied.
Next evidence: representative baseline, completion times, failures and recovery behavior.
Decision example: authorize a limited pilot with agreed entry/stop conditions and an accountable owner, rather than claiming readiness for full rollout.

REWRITE PROMPT
Use only the supplied brief. Explain the consequence, mechanism, evidence and trade-off for [audience]. Define unfamiliar terms in context. Preserve units, denominators, uncertainty and limits. Flag unsupported claims instead of supplying missing evidence. Return six slide titles with short spoken explanations and references to supporting material.