The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We need a quick sync with the platform owner. Start a huddle with Marco, Lina, and me now, invite…
Execute — do the immediate task
+We need a quick sync with the platform owner. Start a huddle with Marco, Lina, and me now, invite only those four, and share my screen so I can show the failing logs. Keep it to ten minutes and tell me when they join.
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 start the huddle, make it easier to get the right attention: recommend a one-line huddle…
Improve — make it easier to accept
+Before I start the huddle, make it easier to get the right attention: recommend a one-line huddle invite that explains why it’s urgent, flag which two artifacts (logs, runbook page) should be ready to share, and suggest the brief agenda so the huddle ends within ten minutes and someone owns next steps.
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 started a huddle to get the platform team on the line but only Marco joined and Lina didn’t. I’m…
Decide — diagnose the stuck moment
+I started a huddle and only one person joined; the outage is still unresolved.
I started a huddle to get the platform team on the line but only Marco joined and Lina didn’t. I’m worried we lost the vendor’s attention and the incident will drag on. I don’t know whether Lina missed the invite, was blocked from joining, or was pulled into another priority. What’s the most likely cause and the fastest way to get Lina into the huddle now or escalate appropriately?
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 frequently start voice huddles for urgent problems and often key people miss them, causing…
Become — change the pattern
+Our ad-hoc huddles often fail to gather the right people quickly.
We frequently start voice huddles for urgent problems and often key people miss them, causing delays and duplicated work. This makes our incident handling slow and messy. Which practice—invitation language, pre-selected artifacts to attach, or a change to who can start huddles—would most reduce no-shows and speed resolution?
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 team chat work people do in Slack.
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.