The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Rename the #ux-updates channel to #ux-weekly so the team expects a cadence rather than a stream.…
Execute — do the immediate task
+Rename the #ux-updates channel to #ux-weekly so the team expects a cadence rather than a stream. Update the channel purpose to say ‘Weekly UX updates every Friday; questions in threads.’ Notify Karen in design and Sam in ops about the change before you rename it tonight.
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 renaming #ux-updates to #ux-weekly, make it easier for people to find the new cadence. Pull…
Improve — make it easier to accept
+Before renaming #ux-updates to #ux-weekly, make it easier for people to find the new cadence. Pull the last three posts and put a one-line summary at the top showing the typical topics, add the new posting day and format in the purpose, and draft a pinned example post so someone knows what to post each Friday.
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
+We decided to rename #ux-updates to #ux-weekly to reduce noise, but I’m worried people will assume…
Decide — diagnose the stuck moment
+We chose a new name but colleagues might miss that it implies a schedule change.
We decided to rename #ux-updates to #ux-weekly to reduce noise, but I’m worried people will assume anything can be posted anytime and the cadence won’t stick. I can’t tell how attached the team is to ad-hoc updates. What’s the quickest way to announce and enforce the new weekly rule so the channel actually becomes lighter?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across projects I keep renaming channels to control volume—#backend-chat becomes…
Become — change the pattern
+We relabel channels to reduce noise but they keep becoming dumping grounds again.
Across projects I keep renaming channels to control volume—#backend-chat becomes #backend-announcements, then it fills up with random questions. It wastes time and undermines the purpose. What persistent change to naming, channel purpose, and team norms will actually reduce noise long-term?
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.