The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Reply to this email from Maya Grant about the project update with a clear next step. Acknowledge…
Execute — do the immediate task
+Reply to this email from Maya Grant about the project update with a clear next step. Acknowledge receipt, confirm the revised timeline to June 8, list the two deliverables I will provide, and ask Maya to confirm if the stakeholder review remains on June 10. Keep it short and professional, use plain language, and send before 5pm today.
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 hit send, make this reply easier for Maya to approve: put the new June 8 timeline in the…
Improve — make it easier to accept
+Before I hit send, make this reply easier for Maya to approve: put the new June 8 timeline in the first line, bold the two deliverables, call out any open questions as bullet points, and add a suggested one-sentence calendar invite for the June 10 review. Flag any language that sounds tentative or could trigger scope pushback.
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
+Maya emailed asking for a revised timeline. I can likely hit June 8 but I’m not sure about resource…
Decide — diagnose the stuck moment
+Maya asked for an updated timeline; I don’t know whether to promise June 8
Maya emailed asking for a revised timeline. I can likely hit June 8 but I’m not sure about resource availability and I don’t want to over-commit. My fear is underdelivering or upsetting the client if I hedge too much. Should I commit to June 8 conditionally, offer a firm partial delivery, or propose a buffer? What language reduces risk and keeps the client confident?
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 I delay decisions in replies, using caveats that invite back-and-forth and push…
Become — change the pattern
+I keep writing long, cautious replies that stall decisions
Across projects I delay decisions in replies, using caveats that invite back-and-forth and push timelines out. I lose credibility and my inbox fills with follow-ups. What single habit and a short template can I adopt so my replies state a clear next step, set a deadline, and ask for a binary confirmation?
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 email and calendar work people do in Microsoft Outlook.
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.