Set a quality and verification bar

For create a seven-minute decision deck for a six-week customer-support pilot, define quality across accuracy, completeness, usefulness, safety, and reproducibility. Weight dimensions according to harm. A cosmetic miss can be revised; an unsupported claim, broken calculation, privacy leak, or rights violation blocks release.

Translate each dimension into observable checks. Accuracy means a claim, value, behavior, or frame agrees with an authoritative source. Completeness means every required field or stage appears. Usefulness means department leaders with little technical background can take the intended action. Safety includes the boundary that you must remove confidential strategy, customer names, internal forecasts, and unreleased product information before using an external tool. Reproducibility means the prompt, input version, settings, and review evidence are saved.

Use checks from cheapest to strongest:

1. Contract check: required sections, schema, length, and prohibited content.
2. Source check: trace claims and values to supplied evidence.
3. Edge check: run normal, boundary, missing, and adversarial cases.
4. Independent check: calculate, test, rehearse, listen, inspect, or open the original.
5. Human gate: a responsible reviewer approves consequential use.

In this chapter, the concrete verification is to read titles alone for logical flow, trace every number to a source, inspect chart axes, rehearse to seven minutes, and test contrast, font size, and alt text. The expected candidate is A title-only story that moves from current support delay to bounded pilot, measurement plan, risk controls, and a final staffing decision. Record actual evidence, not a checkbox copied from the prompt.

Score each criterion 0 (fails), 1 (partly), or 2 (passes). Any zero for factual correctness, permission, privacy, or required disclosure is an automatic stop. A total score is useful for comparing iterations, but it must never average away a blocking defect.

Create a six-slide outline for leaders deciding whether to assign two staff to a six-week support pilot. Use only my evidence. Each title must be a complete takeaway sentence; add 2–3 support bullets, a suggested visual, and speaker notes under 40 words. Mark missing evidence; never invent metrics or quotes.

After generation, sample beyond the happy path. Failures such as decorating before structuring; invented metrics; slide titles that name topics rather than conclusions; overcrowded notes; unlabeled generated imagery often survive a superficial review because the output has the right shape. Use a counterexample designed to expose the riskiest assumption.

Store the rubric result, reviewer, date, input version, failed cases, and unresolved limitations. If the artifact changes, rerun affected checks. A deck is a guided argument, not prose divided into rectangles. If the titles alone do not tell the story, visual polish will not rescue it. Quality assurance is part of the work, not an apology added at the end.