The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Ben is talking over the presenter and refusing to mute during the 14:00 product demo. Mute him for…
Execute — do the immediate task
+Ben is talking over the presenter and refusing to mute during the 14:00 product demo. Mute him for now, then message him that he can rejoin when he stops interrupting and outline the rule: one speaker at a time. Do it quietly so the demo can continue.
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 mute Ben in the 14:00 product demo, surface how often he has interrupted today, show…
Improve — make it easier to accept
+Before I mute Ben in the 14:00 product demo, surface how often he has interrupted today, show whether his mic is picking up background noise, and highlight polite script options to inform him after muting so the host doesn't sound confrontational.
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
+Ben has already been asked twice to stop interrupting and is still talking. I'm worried muting him…
Decide — diagnose the stuck moment
+Ben keeps interrupting the presenter despite two polite asks.
Ben has already been asked twice to stop interrupting and is still talking. I'm worried muting him will make him defensive and derail future collaboration. I can't tell if he's doing it deliberately or has technical feedback issues. What's the likely cause and the least escalatory next move that preserves the demo pace?
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 the last five demos we've spent 10–15 minutes managing audio disruptions by muting attendees,…
Become — change the pattern
+Hosts keep muting participants one by one in every demo.
Over the last five demos we've spent 10–15 minutes managing audio disruptions by muting attendees, which shrinks productive time and annoys people. What operational habit should we change in invites, pre-demo instructions, or host prep to prevent routine muting and keep demos on schedule?
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 video calls work people do in Google Meet.
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.