Share a draft

Share a draft in Gmail — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

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 need you to send a draft of the support handover email I wrote to Priya in product and to Marcus…
I need you to send a draft of the support handover email I wrote to Priya in product and to Marcus in onboarding for review, in that order, with a Friday 5pm deadline for comments. Before you send, check the subject line reads: Support handover — Acme Corp, summarize the three open tickets in the first paragraph, and attach the latest incident report. Send as a normal email so their replies thread to me.

Improve — make it easier to accept

+
Before I share this draft with Priya in product and Marcus in onboarding, make it trivially…
Before I share this draft with Priya in product and Marcus in onboarding, make it trivially scannable for a reviewer: put a two-sentence summary of the ask and the risk at the top, bold the three action items and who owns each, pull the proposed timeline into a single line, and flag anything that would make Priya hesitate (missing logs, unclear SLA, or unresolved customer contact).

Decide — diagnose the stuck moment

+
I sent the draft to Marcus and Priya at once instead of Priya first; Marcus handles onboarding and…

I just hit send on a draft that should have gone to Priya first but I’m not sure Marcus needs to see the whole ticket list

I sent the draft to Marcus and Priya at once instead of Priya first; Marcus handles onboarding and the ticket details might confuse him. I’m afraid Priya will miss the prioritized fixes and blame me for not escalating properly. I can’t tell whether Marcus already read it. What’s the likely damage and the best next step to correct recipients and preserve trust?

Become — change the pattern

+
I keep losing control of review order: I blast drafts to everyone and then chase conflicting…

I keep sending drafts to the whole group instead of sequencing reviewers

I keep losing control of review order: I blast drafts to everyone and then chase conflicting comments. Across projects this costs a day and damages my credibility with product owners. What habit should I change to get predictable review sequencing, how to enforce it without sounding passive-aggressive, and one checklist item to use before hitting send?

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.