The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Mark the three new customer confirmations as read and archive them, but leave the two flagged…
Execute — do the immediate task
+Mark the three new customer confirmations as read and archive them, but leave the two flagged vendor invoices as unread so I can process them tomorrow morning.
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 mark these messages as read, make the inbox easier to act on: show me which messages can…
Improve — make it easier to accept
+Before I mark these messages as read, make the inbox easier to act on: show me which messages can be safely archived, which need a queued reply, and which require immediate action. For ones to be marked read, recommend a one-line archive note so someone later can find why it was closed, and flag any items that would make a reviewer hesitate.
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 opened many emails and marked them all read to clear notifications, but now my team can’t tell…
Decide — diagnose the stuck moment
+I just opened a stack of emails and marked them all read to clear the notification badge
I opened many emails and marked them all read to clear notifications, but now my team can’t tell which invoices still need processing and I don’t know which approvals are pending. I’m worried procurement will miss payment deadlines. What is the fastest triage to restore order and how should I explain the mistake to my finance lead?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I habitually mark messages read to make my inbox feel under control, then downstream teams miss…
Become — change the pattern
+I habitually mark messages read to feel caught up but create confusion downstream
I habitually mark messages read to make my inbox feel under control, then downstream teams miss items and I get pulled into firefights. Where am I losing time and trust, what single habit change will stop this, and how to get the team to accept a new shared inbox protocol?
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 work people do in Gmail.
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.