The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Download the Q2 Sales deck from the Shared Files channel, save a local copy to my laptop as…
Execute — do the immediate task
+Download the Q2 Sales deck from the Shared Files channel, save a local copy to my laptop as Sales-Q2-Deck-v2.pdf, and verify the file checksum or modification timestamp matches the version the team approved. Do it during the 15-minute window after this stand-up so everyone’s edits are settled.
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 download the Q2 Sales deck, make sure the reviewers can trust the file — surface the…
Improve — make it easier to accept
+Before I download the Q2 Sales deck, make sure the reviewers can trust the file — surface the latest approver, the approval timestamp, and any comments or pending edits. If the deck isn’t final, show which slides changed since the last approved version so I only download the true release copy.
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 attempted to download the Q2 Sales deck from the Shared Files channel and found v1, v2, and a…
Decide — diagnose the stuck moment
+I tried to download the Sales deck but multiple versions exist and I don’t know which is final.
I attempted to download the Q2 Sales deck from the Shared Files channel and found v1, v2, and a 'final' file; no one marked which is approved. I’m afraid I’ll send the wrong slide set to executives. Who do I ask right now to confirm finality, and what quick check will prove the file is the approved release before I distribute it?
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 repeatedly hand out the wrong slide decks because approvals aren’t visible in the file system…
Become — change the pattern
+We keep downloading outdated or unapproved files and embarrassing leadership.
We repeatedly hand out the wrong slide decks because approvals aren’t visible in the file system and people name files inconsistently. I want one habit that prevents this across projects. What naming convention, approval tag, and one-minute verification step should we require before anyone downloads and shares a presentation?
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.