Send a quick message

Send a quick message in Slack — 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 to tell the engineering team that the deploy window is pushed from 6pm to 8pm because we…
I need to tell the engineering team that the deploy window is pushed from 6pm to 8pm because we found a hot memory leak. Send a short message to #eng-ops saying: we’re moving tonight’s deploy from 6:00 PM to 8:00 PM due to a memory leak discovered in staging. Postmortem to follow by end of day tomorrow. Ping @Ravi and @Marta for immediate questions.

Improve — make it easier to accept

+
Before I post the deploy delay to #eng-ops, make it easy for people to see what matters: lead with…
Before I post the deploy delay to #eng-ops, make it easy for people to see what matters: lead with the new time and why, include the risk level, and add who to ping. Message should read: Deploy moved to 8:00 PM — memory leak in staging. Risk: can cause OOM on prod. Please don’t push hotfixes without coordinating. Contact @Ravi for triage, @Marta for rollback plan.

Decide — diagnose the stuck moment

+
We found a memory leak in staging that could cause OOM in prod. I’m about to tell #eng-ops but I’m…

I just detected a memory leak in staging and found it might impact tonight’s deploy.

We found a memory leak in staging that could cause OOM in prod. I’m about to tell #eng-ops but I’m not sure how blunt to be. People will panic and block other work if I overstate it; if I understate it they’ll miss the rollback window. What phrasing gets attention without triggering chaos and who should I @ for fastest triage?

Become — change the pattern

+
We keep getting last-minute deploy issues and my short messages to #eng-ops spark frantic…

I repeatedly send terse deploy updates that prompt frantic threads and follow-ups.

We keep getting last-minute deploy issues and my short messages to #eng-ops spark frantic multi-threaded replies and accidental overrides. Where am I wasting time and credibility, and what habit should I change so notifications are clear, actionable, and reduce reactive firefighting?

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.