The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create a private channel for the Product Pricing working group named Pricing-Confidential, add…
Execute — do the immediate task
+Create a private channel for the Product Pricing working group named Pricing-Confidential, add Priya from Product, James from Finance, and Noor from Legal as members, and restrict visibility to only them. Set channel moderation off and confirm membership with me by end of day Friday.
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 create the Pricing-Confidential private channel, make it easy for reviewers — explain why…
Improve — make it easier to accept
+Before I create the Pricing-Confidential private channel, make it easy for reviewers — explain why it needs to be private, show which documents will live there and who truly needs access, and flag any stakeholders who will be excluded but require periodic updates. Recommend a single owner and a 90-day review date to avoid stale private silos.
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
+Product wants a private channel for pricing discussions and named three people. I’m worried…
Decide — diagnose the stuck moment
+Stakeholders asked for a private channel for pricing but I’m not sure who actually needs access.
Product wants a private channel for pricing discussions and named three people. I’m worried Procurement and Sales will claim late they needed read access and that Legal should be consulted on disclosure. Who should I add now to avoid rework while keeping the channel tight, and what’s the fastest way to give others temporary view-only access later if needed?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+In the past year our org has spun up many private channels and information is fragmented; people…
Become — change the pattern
+We create private channels each quarter that become forgotten silos.
In the past year our org has spun up many private channels and information is fragmented; people miss updates and duplicate work because access wasn’t revalidated. I need one habit change to stop private-channel proliferation and keep necessary secrecy. What governance check and naming rule should we apply so private channels stay purposeful and discoverable to admins later?
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 collaboration work people do in Microsoft Teams.
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.