The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I have an urgent customer escalation from Daniel Chen and need the team to act. Open the thread…
Execute — do the immediate task
+I have an urgent customer escalation from Daniel Chen and need the team to act. Open the thread from Daniel Chen, set the email priority to High, mark it Follow-up, and forward it to the escalation group with a one-line note: Urgent customer outage — please respond within one hour. Add me on the To line. Confirm changes and report when forwarded.
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 label this message urgent, make priority clear without causing alarm fatigue. Add High…
Improve — make it easier to accept
+Before I label this message urgent, make priority clear without causing alarm fatigue. Add High importance to the message, but in the subject prefix URGENT only if the customer named Daniel Chen reports service-down. Otherwise mark as Medium and add a due-by time in the body. Ensure the escalation group sees priority and the expected response SLA.
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
+Daniel Chen just emailed saying the service is down. I am afraid over-using High priority will…
Decide — diagnose the stuck moment
+A customer wrote 'service down' and I hesitate to mark everything urgent.
Daniel Chen just emailed saying the service is down. I am afraid over-using High priority will train the team to ignore flags, but waiting could delay a real outage fix. I cannot tell if this is a real system outage or a local issue. What's the best immediate step to set priority and route the message so we act fast without creating noise?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We have a culture where most emails are tagged High and the engineering on-call stops trusting…
Become — change the pattern
+Our team ignores priority flags because almost everything is marked high.
We have a culture where most emails are tagged High and the engineering on-call stops trusting flags, causing real incidents to be missed. I want one habit to fix this: how should we define when to use High importance, who approves escalations, and what email practice will restore trust and fast response?
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.