The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Add a checkbox grid question to the departmental feedback form for Operations. Title it Which…
Execute — do the immediate task
+Add a checkbox grid question to the departmental feedback form for Operations. Title it Which features do you use for each product? Rows: Time tracking, Reporting, Alerts. Columns: Desktop app, Mobile app, Web portal, API. Allow responders to check multiple columns per row and make the question optional.
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
+Make the checkbox grid easier for the procurement reviewers: surface the most-used features by…
Improve — make it easier to accept
+Make the checkbox grid easier for the procurement reviewers: surface the most-used features by ordering rows with Time tracking first, group columns logically (apps then API), include a short instruction above: You may select all that apply for each feature, and flag any row/column that might be misread (for example 'API' could be unclear). Ensure it renders well on phones where checkboxes stack.
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 added a checkbox grid to the feedback form for the product team but procurement didn't tell me if…
Decide — diagnose the stuck moment
+Procurement asked for one checkbox grid but didn't define columns clearly.
I added a checkbox grid to the feedback form for the product team but procurement didn't tell me if 'API' means 'public API' or 'partner API'. I can ask them but the deadline is tomorrow. What's the likely interpretation reviewers will use, and should I proceed with a clarifying parenthesis now or send it as-is and follow up?
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 quarter the checkbox grid responses from operations are messy — people check inconsistent…
Become — change the pattern
+Checkbox grids repeatedly generate ambiguous responses.
Every quarter the checkbox grid responses from operations are messy — people check inconsistent combinations and comments say the columns are unclear. Where am I losing clarity — industry jargon, column order, or missing instructions — and what single change to my template would reduce ambiguous checks across all teams?
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.