This prompt does the interview before the build. It asks what actually goes wrong, who owns each failure mode, when an item counts as late, and what happens when the owner does not respond. What you get back is a specification, not an app.
Why This Matters
Exception boards fail on the definitions, not the layout. If "late" means something different to two people, the board reports fiction. Answering the prompt's questions is how you find that out before it becomes a column.
What This Prompt Asks For
- Failure modes: The real exception types, in your team's words, not generic categories.
- Ownership: One accountable name or role per type, with no shared ownership.
- Aging thresholds: The day count that turns an open item into a late item.
- Escalation path: Who hears about it next, and after how long.
Honest boundary
You end up with a design and a set of decisions, not a running board. The prompt cannot tell you whether your thresholds are right. It can make sure you picked them on purpose.
How To Use The Prompt
- Copy the prompt from this page.
- Answer its questions with your real categories and day counts.
- Keep the returned specification as your build checklist.
- Build from the checklist, or paste the specification into Taskade Genesis to generate the board.
Copy the prompt in Taskade, then hand the routing to automations.
