The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Restore the client presentation slides to the version saved on March 2 at 09:15 because the March…
Execute — do the immediate task
+Restore the client presentation slides to the version saved on March 2 at 09:15 because the March 10 file was corrupted. Replace the current Presentation_Final.pptx with that March 2 copy and keep a backup of the corrupted March 10 file in a folder named Corrupted Backups before replacing it.
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 revert slides for the sales deck, make it easy for the account lead to accept the change:…
Improve — make it easier to accept
+Before I revert slides for the sales deck, make it easy for the account lead to accept the change: show a timestamped preview of the March 2 version, list any images or linked charts that will be affected, warn if any comments will be lost, and create a backup of the current file in a Corrupted Backups folder so the team can review if needed.
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
+The March 10 sales deck opened as gibberish and Priya insists we must restore March 2. I worry we…
Decide — diagnose the stuck moment
+The latest deck got corrupted and the team wants the March 2 copy back
The March 10 sales deck opened as gibberish and Priya insists we must restore March 2. I worry we might lose Tom’s last-hour edits from March 8. I don’t know whether those edits exist in the corrupted file or a local copy. What’s the most reliable way to restore March 2 while preserving any recoverable March 8 edits and minimizing risk before our Friday call?
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 keep reverting to earlier file versions and then discover we’ve lost important late edits,…
Become — change the pattern
+We repeatedly restore old versions and lose recent edits
We keep reverting to earlier file versions and then discover we’ve lost important late edits, costing credibility with clients. Are we failing because people work offline, because we lack a clear single-edit-owner, or because backups aren’t automated? What one operational habit should we enforce to stop these repeated rollbacks?
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.