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 Mark from Sales removed from the Customer Success team. Deactivate his access so he can’t…
Execute — do the immediate task
+I need Mark from Sales removed from the Customer Success team. Deactivate his access so he can’t view channels or files, then remove him from the team membership list and notify me when it’s complete. Do the removal during off-peak hours between 7:00 p.m. and 9:00 p.m. on Thursday so there’s minimal disruption.
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 remove Mark from the Customer Success team, make it safe for audit — list the channels he…
Improve — make it easier to accept
+Before I remove Mark from the Customer Success team, make it safe for audit — list the channels he currently has access to, flag any files he owns or recently edited in the last 90 days, and surface any active tasks assigned to him. Highlight anything that would break if he’s removed so I can decide whether to reassign first.
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
+Mark told me he’s resigning effective today and HR asked me to remove him immediately from the…
Decide — diagnose the stuck moment
+I just learned Mark is leaving today and is still in the Customer Success team.
Mark told me he’s resigning effective today and HR asked me to remove him immediately from the Customer Success team. I’m worried about losing ownership of open deliverables and exposing sensitive customer documents if I act too fast, but I also can’t leave him with access. Who should I notify first, what’s the fastest safe removal sequence, and what checks do I run now to avoid lost work or security gaps?
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 last six departures we’ve lost time hunting who owned key files and several approvals blew…
Become — change the pattern
+We keep scrambling to remove departing people without clean handoffs.
Over the last six departures we’ve lost time hunting who owned key files and several approvals blew past deadlines after removals. I want a repeatable habit that prevents these last-minute sprints. What simple pre-exit checklist and one-line naming convention for file ownership and tasks should we enforce so removing someone is routine, quick, and safe?
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.