Embed checklists at the point of delivery — integrate into templates, PR forms, or pre-send screens so skipping is harder than completing

Why This Is a Rule

A checklist stored in a separate document requires a voluntary action to access: open the document, read through it, then return to the delivery action. Under time pressure or completion momentum, this voluntary step gets skipped. The checklist exists but doesn't get used — it's a tool that requires discipline to access rather than a structural feature that's encountered automatically.

Embedding the checklist at the delivery point eliminates the voluntary access step. When the checklist is part of the PR template (you can't submit without filling it out), part of the email compose screen (a sidebar you see while writing), or part of the report template (checkboxes at the bottom before the "submit" button), engaging with it is the path of least resistance. Skipping it requires a deliberate action (deleting the checklist section, unchecking a "I've verified" box, scrolling past a modal). The friction has been inverted: default path includes the checklist; skipping requires extra effort.

This is the same environmental design principle as Place trigger objects at eye level in routine paths — visibility beats proximity for reliable activation (trigger placement) applied to quality verification: the intervention must intercept the natural workflow at the exact moment when it's relevant, not require a detour to a separate location.

When This Fires

• When designing the delivery workflow for any recurring output type
• When checklists exist but aren't being used — usually a placement problem, not a motivation problem
• When quality errors persist despite having checklists — verify the checklists are embedded, not stored separately
• Complements Mandatory quality pause between "I think this is done" and delivery — use an explicit checklist, not optional review when time permits (mandatory quality pause) and Limit checklists to 5-9 items targeting frequent + consequential errors, ordered catastrophic-first for partial execution under time pressure (checklist design) with the environmental integration

Common Failure Mode

The standalone checklist document: a beautifully designed quality checklist living in a shared drive folder, accessible to anyone who remembers it exists and voluntarily navigates to it. Usage rate: approximately zero under normal working conditions.

The Protocol

(1) For each delivery channel you use (email, PR, document submission, presentation), identify the last action before delivery (click "Send," click "Submit," share the file). (2) Embed the checklist immediately before this action: as part of the email template, as required fields in the PR form, as a sign-off section in the document template. (3) Make the checklist engagement harder to skip than to complete: required fields that block submission, modal confirmations ("Have you verified X?"), template sections that look incomplete if unfilled. (4) Test: can someone deliver this output type without encountering the checklist? If yes, the embedding isn't tight enough. (5) Keep the embedded checklist minimal (Limit checklists to 5-9 items targeting frequent + consequential errors, ordered catastrophic-first for partial execution under time pressure) so it doesn't create aversion. A 5-item checklist embedded in the workflow takes 60 seconds and will be completed every time. A 20-item checklist will be resented and circumvented.