Quality Checklist Design
Catches the skipped step rather than the unknown one, and stays short enough to actually be used.
Free — no card needed
Create a free account
to open Quality Checklist Design — and the other 364 prompts across 21 categories.
Already have an account?
Running it, start to finish
- Identify which past failures a checklist could actually have caught.
- Cut to the handful of items where omission causes real harm.
- Define what happens when an item fails.
What you get back
The output this produces, every time.
- Sorts your failures into the ones a checklist can catch and the ones it cannot.
- Chooses read-do or do-confirm, which determines whether experienced people will use it.
- Keeps it short, since a long checklist gets ticked rather than checked.
Getting better results
Where this usually goes wrong, and how to avoid it.
- Use do-confirm for experienced staff. A read-do checklist handed to an expert is condescending and gets abandoned, taking the useful items with it.
- Include only the killer items. A checklist of every step is a procedure document and will not be used at the moment it matters.
- Prune it regularly. Items accumulate after every incident until the checklist is too long to use, which removes the protection entirely.
More Operations prompts
All Operations →- Operations
Incident Runbook
Writes a runbook usable at 3am by someone who did not build the system and is not thinking clearly.
ClaudeChatGPT000Open → - Operations
SOP From How It Actually Works
Documents a process as it is really performed, including the undocumented workarounds, so the SOP describes reality rather than intent.
ClaudeChatGPT000Open → - Operations
Vendor Evaluation Scorecard
Evaluates suppliers against weighted criteria set before the demos, so the decision is not made by whoever presented best.
ClaudeChatGPT000Open →
Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.