The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Enable two-factor authentication for my account and require it for all team members by Friday, July…
Execute — do the immediate task
+Enable two-factor authentication for my account and require it for all team members by Friday, July 25. Use SMS plus an authenticator app option. After enabling, send setup instructions to each team member and confirm who has completed setup.
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 roll out mandatory two-factor authentication to the team, make compliance easy: show which…
Improve — make it easier to accept
+Before I roll out mandatory two-factor authentication to the team, make compliance easy: show which 2FA methods are available, highlight the least friction option for mobile-first contractors, list steps for recovery if someone loses access, and flag any admin accounts that will be locked out so I can schedule a window to enforce it.
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 enabled two-factor authentication and set my phone up, but I can’t find the recovery codes and…
Decide — diagnose the stuck moment
+I turned on two-factor for myself but can’t access my recovery codes
I enabled two-factor authentication and set my phone up, but I can’t find the recovery codes and I’m worried if I lose my phone I’ll lock the company out. I can’t pause enforcement because the finance director wants it on. What immediate steps should I take to secure fallback access and communicate the change without creating helpdesk chaos?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Each time I require two-factor, a third of the team files help requests about lost codes or phones,…
Become — change the pattern
+Every enforcement push causes helpdesk tickets and lost time
Each time I require two-factor, a third of the team files help requests about lost codes or phones, which drains me and delays payments. What rollout habit, communication template, or recovery policy will cut helpdesk volume and make mandatory 2FA sustainable?
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 payments work people do in PayPal.
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.