The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The analytics integration is spamming the product channel with daily metrics that confuse PMs.…
Execute — do the immediate task
+The analytics integration is spamming the product channel with daily metrics that confuse PMs. Disable the analytics integration for the product channel today and tell Ana in PM and Marco the engineering lead that it’s off and why, so they don’t expect those messages anymore.
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 disabling the integration, make it easy for product and engineering to keep the useful…
Improve — make it easier to accept
+Before disabling the integration, make it easy for product and engineering to keep the useful parts: list which messages the integration posts, mark the three that product actually uses, show how to send those three as a daily brief instead of live posts, and warn about any dashboards or alerts that will stop updating if we turn it off.
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 disabled the analytics integration to stop the noise, but Priya in Product says the morning…
Decide — diagnose the stuck moment
+I flipped off the analytics bot and now the PMs are asking where the daily numbers went.
I disabled the analytics integration to stop the noise, but Priya in Product says the morning conversion numbers are missing and Marco says he relies on one of those posts for an alert. I don’t know which posts are essential and I can’t tell if disabling the integration broke dashboards. What’s the likeliest cause and the quickest way to restore the essential feeds while keeping everything else dark?
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 past six months we toggle integrations on and off when channels get noisy, and each time…
Become — change the pattern
+We oscillate between full integrations and no integrations, confusing stakeholders.
Over the past six months we toggle integrations on and off when channels get noisy, and each time someone in Product or Ops complains about lost data or missed alerts. This erodes trust and wastes time. What concrete rule or gating process should we adopt for enabling/disabling integrations so we keep the useful signals and avoid reactive flips?
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.