The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Share the meeting notes with the product squad and the engineering director for visibility, give…
Execute — do the immediate task
+Share the meeting notes with the product squad and the engineering director for visibility, give the squad edit rights and the director view-only access, and include a short note asking for additions by Thursday. Make sure the link reaches both teams and they get an email notification.
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 share this document, make it frictionless for collaborators: put the action items in a top…
Improve — make it easier to accept
+Before I share this document, make it frictionless for collaborators: put the action items in a top summary, add an @-mention to each responsible person, and set the sharing so team members can edit but execs can only comment or view. Flag anything that will make an exec reply instead of just reading.
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 just shared the meeting notes with the product squad and the engineering director; Claire on the…
Decide — diagnose the stuck moment
+I hit share but Claire says she didn’t get an email and can’t open the file.
I just shared the meeting notes with the product squad and the engineering director; Claire on the squad says she didn’t receive the email and can’t open the link. I’m worried I used the wrong address or wrong access level, and I don’t know whether to resend individually or change the document link. What is the most likely cause and the fastest way to ensure everyone actually receives and can open the document now?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over several projects, we spend time policing who can edit and who can’t, leading to accidental…
Become — change the pattern
+We keep getting questions about who can edit our shared files.
Over several projects, we spend time policing who can edit and who can’t, leading to accidental overwrites and missing input. Where are we breaking down — naming conventions, sharing habits, or review workflow — and what two changes to our routine will stop accidental edits and make permission setup predictable for every new document?
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 word processor work people do in Google Docs.
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.