The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create task templates for recurring design work: a 5-step template for new feature designs, a…
Execute — do the immediate task
+Create task templates for recurring design work: a 5-step template for new feature designs, a 3-step template for microcopy changes, and a QA checklist for handoff to engineering. Each template should create fields for owner, due date, related project link, and required attachments, and they should appear in the team’s task database. Name them New feature design, Microcopy update, and Engineering handoff and have them ready by Thursday for the sprint planning meeting.
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 add these templates to the shared task list, make them easier for teammates to use. Put…
Improve — make it easier to accept
+Before I add these templates to the shared task list, make them easier for teammates to use. Put the acceptance criteria and required attachments at the top of each template, add a quick-estimate field with three choices, and flag any step that needs cross-functional approval. Also mark which template to use for bug fixes so reviewers won’t pick the wrong one.
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
+I published standardized task templates but engineers and product keep creating their own tasks…
Decide — diagnose the stuck moment
+People keep using ad-hoc tasks instead of the templates
I published standardized task templates but engineers and product keep creating their own tasks instead. I’m afraid the templates are either hard to find or missing fields they actually need. What’s the most likely reason they ignore them and what small change will drive adoption this sprint?
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 sprints we repeatedly spend 2–3 hours clarifying poorly written tasks because people don’t…
Become — change the pattern
+We lose time re-specifying tasks each sprint
Across sprints we repeatedly spend 2–3 hours clarifying poorly written tasks because people don’t use templates or the templates miss key fields. That causes missed deadlines and blame. Which two habits—about how we create and review tasks—should we change to stop rework, and what enforcement step makes those habits stick next sprint?
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.