The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Rename the file Proposal_Draft_v3.docx in the Sales > Pending folder to…
Execute — do the immediate task
+Rename the file Proposal_Draft_v3.docx in the Sales > Pending folder to Proposal_AlphaCorp_Signed_v1.pdf, and rename the Pending folder to Pending — Under Review. Confirm any links or shortcuts still point to the renamed file and tell me if any shared links break.
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 rename items for handoff to the legal team, surface the risk points: move the current…
Improve — make it easier to accept
+Before I rename items for handoff to the legal team, surface the risk points: move the current draft to a folder called For Legal Review, place the filename Proposal_AlphaCorp_For_Legal_20260721.docx so it's obvious, and highlight where previous versions exist. Flag if any external collaborators will lose access because of the rename.
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 changed Pending to Pending — Under Review and a client says their shared link to…
Decide — diagnose the stuck moment
+I renamed a folder and some team members report broken links
I changed Pending to Pending — Under Review and a client says their shared link to Proposal_Draft_v3 no longer works. I’m worried I broke published links and I don’t know which ones. What immediate steps find and restore any broken shared links, and what’s the minimal rollback or notification I should do to avoid confusion?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every handoff someone renames files differently and we lose track of the approved version. Version…
Become — change the pattern
+We keep changing filenames and auditing versions costs time
Every handoff someone renames files differently and we lose track of the approved version. Version control slows approvals and forces duplicate storage. What simple naming rule and one team habit will stop the churn, make the approved file discoverable, and reduce version-checking conversations by at least half?
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 file storage work people do in Google Drive.
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.