The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+This document needs tracked-suggestion edits rather than blunt changes. Turn on Suggesting mode,…
Execute — do the immediate task
+This document needs tracked-suggestion edits rather than blunt changes. Turn on Suggesting mode, replace the executive summary paragraph with the tightened version I drafted, leaving the original text visible as a suggestion, and add a short comment explaining why this phrasing reduces ambiguity for procurement. Tag Owen as the reviewer and set a three-day review deadline.
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 submit suggested edits, make them easy to accept: keep each suggestion atomic and explain…
Improve — make it easier to accept
+Before I submit suggested edits, make them easy to accept: keep each suggestion atomic and explain the reason in one line, surface the net word-count change, and flag any sentence where meaning could shift legally. Identify suggestions likely to trigger pushback from Owen and propose an alternative phrasing he can accept without multiple rewrites.
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 turned edits into suggestions and Owen accepted half but rejected a key clause I thought…
Decide — diagnose the stuck moment
+I suggested a rewrite and Owen accepted some but rejected others.
I turned edits into suggestions and Owen accepted half but rejected a key clause I thought clarified liability. I don't know whether he objects to tone, legal exposure, or losing flexibility. Should I add a comment explaining my rationale, propose a compromise sentence, or schedule a quick screen share to walk him through the changes? Which will get agreement fastest?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across many documents our team uses suggesting mode but final authors frequently ignore the…
Become — change the pattern
+Suggested edits keep getting buried or ignored across projects.
Across many documents our team uses suggesting mode but final authors frequently ignore the suggestions, causing rework. Where are suggestions failing — visibility, timing, or trust in the suggester — and what one practice should we adopt to make suggested edits accepted first time?
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.