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're running a pre-demo whiteboard at 9 a.m. tomorrow with design, product, and the demo lead.…
Execute — do the immediate task
+We're running a pre-demo whiteboard at 9 a.m. tomorrow with design, product, and the demo lead. Start a whiteboard session, add the persona map, the user-journey sketch, and a slot for 'open risks'. Invite Priya, Diego, and Samir and pin the session link in the channel so the demo lead can run through it at 9:15.
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 open the whiteboard with stakeholders, make it easier for reviewers to act. Put the…
Improve — make it easier to accept
+Before I open the whiteboard with stakeholders, make it easier for reviewers to act. Put the decision we need in the top-left, add numbered prompts that ask reviewers to vote on feasibility, usability, and risk, and leave a visible checkbox for 'ready for demo' so the demo lead can close the loop quickly.
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 started a whiteboard but Diego says it's cluttered and reviewers won't engage. I have ten minutes…
Decide — diagnose the stuck moment
+Design wants the whiteboard organised.
I started a whiteboard but Diego says it's cluttered and reviewers won't engage. I have ten minutes before the session. What single reorganization will get designers and product to focus and the exact two labels I should add now so people know where to click first?
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 projects our whiteboards fill with stray notes and nobody can find the final decisions. I…
Become — change the pattern
+Whiteboards become messy and unused after a few edits
Across projects our whiteboards fill with stray notes and nobody can find the final decisions. I want one standard that keeps a board readable from day one through demo. What simple structure and a single naming convention should we use so anyone can locate outcomes and the demo lead can close a board cleanly?
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 collaboration work people do in Microsoft Teams.
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.