The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Reorder the lists on the Q3 Roadmap board so they read: Backlog, Ready, In Progress, Blocked,…
Execute — do the immediate task
+Reorder the lists on the Q3 Roadmap board so they read: Backlog, Ready, In Progress, Blocked, Review, Done. Keep card order within each list unchanged. Confirm the new sequence and tell me if any active automations depend on the previous order.
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 reorder lists on the Q3 Roadmap board, make it easy for the product lead to approve. Show…
Improve — make it easier to accept
+Before I reorder lists on the Q3 Roadmap board, make it easy for the product lead to approve. Show current list order and proposed order side by side, flag any boards or automations that reference list names or positions, and highlight cards that will move visually out of workflow so the lead can sign off without combing every list.
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 just reordered the lists on the Q3 Roadmap board and several automations triggered unexpectedly,…
Decide — diagnose the stuck moment
+I dragged lists and now automations fired incorrectly
I just reordered the lists on the Q3 Roadmap board and several automations triggered unexpectedly, moving cards and reopening work. I’m worried we’ve created noise and lost context for reviewers and clients. I don’t know which automations used list position versus name. What immediate steps stop further incorrect moves, how do I assess what changed, and how should I notify stakeholders about any exposed errors?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time someone reorders lists across our program boards, automations and team expectations…
Become — change the pattern
+List reorders repeatedly break workflows
Every time someone reorders lists across our program boards, automations and team expectations break and we lose credibility with stakeholders. I want a single habit change that prevents this pattern. What operational rule should we adopt about when and how lists can be reordered, and what lightweight approval or test should be mandatory to protect automations and reviewers?
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 kanban boards work people do in Trello.
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.