Build a repeatable workflow

Use this topic-specific sequence: brief → spine → evidence → design → rehearse → decide. Give each stage one input, one output, and one gate. The first run should be narrow and reversible. Later automation is earned by measured reliability, not by how easy it is to connect tools.

For create a seven-minute decision deck for a six-week customer-support pilot, begin with the job card and sanitized packet. Run the constrained prompt:

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.

Save the response beside its prompt and input version. Then apply the quality rubric and 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. A failed check returns to the smallest responsible stage; do not regenerate everything. If the source was missing, repair context. If the instruction was ambiguous, repair the prompt. If the candidate violates policy, stop and escalate rather than prompt around the policy.

Name an owner for source approval, generation, verification, and release. One person may hold several roles on a small project, but the role changes should remain visible. The reviewer needs the evidence packet, not merely the final artifact.

Define operational states: draft, needs evidence, blocked, approved, released, and rolled back. This vocabulary prevents a plausible draft from being mistaken for an approved result. Attach timeouts, retry limits, and an off switch to any automated stage.

Log the defect category rather than just “bad output.” This chapter's recurring defects are decorating before structuring; invented metrics; slide titles that name topics rather than conclusions; overcrowded notes; unlabeled generated imagery. Track their rate on representative cases. Review false positives and false negatives separately when classification is involved; track factual, continuity, or rights defects when producing media.

The end product is a presentation packet containing the brief, title spine, source ledger, accessible visuals, timed notes, and Q&A prep. 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. Periodically rerun a stable set of cases after changing models, prompts, source material, formulas, or settings.

Imagine the independent check fails after release. Identify how to stop distribution, identify affected outputs, restore the last approved version, notify the owner, and preserve enough evidence to learn. A workflow without rollback is only a happy-path demo.