The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We need a task checklist for launching the pricing page. List the steps in execution order: write…
Execute — do the immediate task
+We need a task checklist for launching the pricing page. List the steps in execution order: write copy, gather screenshots, implement responsive CSS, QA on mobile, update analytics events, and publish. Assign each item to Priya in Marketing, Diego in Design, Lena in Frontend in that order and set due dates so QA completes two days before launch. Verify each item has an acceptance criterion before assigning.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand this checklist to the team, make it approval-friendly: surface the three highest-risk…
Improve — make it easier to accept
+Before I hand this checklist to the team, make it approval-friendly: surface the three highest-risk items first, add an explicit acceptance criterion for each task so reviewers know when to sign off, mark who blocks whom, and flag any task lacking assets or a clear owner so Priya, Diego, and Lena can approve faster.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+Diego uploaded an iteration but said he’ll finish the final screenshots later, and QA is scheduled…
Decide — diagnose the stuck moment
+Diego left the design task without a final asset
Diego uploaded an iteration but said he’ll finish the final screenshots later, and QA is scheduled in two days. Diego is stretched across two launches and may deprioritize our assets. I can’t tell if his remaining work is a quick polish or a redesign. What’s the most likely situation, and what immediate step gets a reliable ETA or a fallback asset by tomorrow?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across multiple launches we keep losing time because checklists contain vague steps like 'design…
Become — change the pattern
+Checklists accumulate vague tasks that block launches
Across multiple launches we keep losing time because checklists contain vague steps like 'design screenshots' without acceptance criteria or backup plans. That creates last-minute chaos and missed release dates. Which single checklist habit should we adopt and enforce so tasks are unambiguous and release-ready, and who should own it?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other docs and databases work people do in Notion.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.