The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Delete the attendance question labeled Present/Absent that is no longer needed. Remove it from the…
Execute — do the immediate task
+Delete the attendance question labeled Present/Absent that is no longer needed. Remove it from the main quiz form and also remove any validation or branching rules that reference it. Confirm there are no orphaned branches and preview the form once the question is deleted before I publish the updated form for Monday.
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 deleting the Present/Absent attendance question, check what depends on it: branch rules,…
Improve — make it easier to accept
+Before deleting the Present/Absent attendance question, check what depends on it: branch rules, summary calculations, or linked sheets. If anything references it, flag those dependencies and suggest an alternative or update. If safe, delete it and confirm the form layout remains logical and no required follow-ups were removed.
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 removed the attendance question and now some follow-up questions vanished from the student view.…
Decide — diagnose the stuck moment
+I deleted a question and a section disappeared.
I removed the attendance question and now some follow-up questions vanished from the student view. I don’t know which branch used that question. How do I find what branches referenced Present/Absent and restore any essential follow-ups without rebuilding the entire form?
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 year we keep removing outdated questions and each time a hidden dependency breaks later…
Become — change the pattern
+We repeatedly delete questions that break the form.
Over the year we keep removing outdated questions and each time a hidden dependency breaks later questions or reports. What systematic habit or small documentation practice will stop accidental breaks when deleting questions? Give one immediate checklist item and one naming or linking convention to adopt.
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 forms and surveys work people do in Google Forms.
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.