The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Share the updated product brief and prototype with the whole design team and the product managers.…
Execute — do the immediate task
+Share the updated product brief and prototype with the whole design team and the product managers. Set the document permissions so anyone in the company can view but only design and product can comment. Send a note to the team and cc Zoe in product with a request to review by Tuesday and to mark any blocker in the comments. Confirm the permissions and delivery before sending.
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 share this with product and the rest of the company, make it easy for them to act. Put a…
Improve — make it easier to accept
+Before I share this with product and the rest of the company, make it easy for them to act. Put a short TL;DR at the top that states what needs review and by when, add a comments section with three specific questions we need answered, and make the prototype link open in view mode. Flag anything confidential so people don’t accidentally forward it.
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 shared the brief and prototype with product and the company and set comments only for product,…
Decide — diagnose the stuck moment
+Shared doc got view-only but no comments
I shared the brief and prototype with product and the company and set comments only for product, but no one left feedback and the review deadline is tomorrow. I’m worried people assume it’s just FYI. What’s the likely diagnosis and the fastest way to get the reviewers to open and comment without mass pings?
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 sharing documents and prototypes but rarely get timely comments, which stalls decisions and…
Become — change the pattern
+Shared documents don’t get timely reviews
We keep sharing documents and prototypes but rarely get timely comments, which stalls decisions and stretches timelines. Are we failing in how we surface ask, in how reviewers are chosen, or in signaling urgency? Recommend two practical changes to our sharing and notification routine that will increase on-time reviews for the next three deliverables.
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 docs and databases work people do in Notion.
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.