The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We need to track incoming customer feedback on the product experience for the support and product…
Execute — do the immediate task
+We need to track incoming customer feedback on the product experience for the support and product teams. Create a feedback database with fields: date, customer name, account MRR, channel, verbatim comment, product area, severity, and owner for follow-up. Import the last 90 days of Intercom transcripts, tag high-severity items, and assign follow-up to Priya in Customer Success within 48 hours.
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 expose the feedback tracker to stakeholders, make it quick to act on: surface…
Improve — make it easier to accept
+Before I expose the feedback tracker to stakeholders, make it quick to act on: surface high-severity and high-MRR tickets at the top, add a short summary line for each comment, flag duplicates, and highlight unresolved items older than 72 hours so Priya and the product leads can prioritize follow-up immediately.
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 pulled the feedback feed and found five high-MRR accounts with severe issues marked but no owner…
Decide — diagnose the stuck moment
+Several high-MRR tickets are unassigned and aging
I pulled the feedback feed and found five high-MRR accounts with severe issues marked but no owner assigned; two are older than a week. Priya is out on leave and the product lead is in back-to-back meetings. I can’t tell who should own escalation or whether any are already in engineering backlog. Who likely should take immediate ownership, and what is the best next step to ensure customers hear back within 24 hours?
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 time feedback accumulates in the tracker without clear severity tagging or ownership; teams…
Become — change the pattern
+Feedback sits unlabeled and people assume someone else will act
Over time feedback accumulates in the tracker without clear severity tagging or ownership; teams assume others will act, so critical issues slip and customer churn rises. What single change to our tracking and handoff process will stop ownership gaps and ensure a visible SLA from report to response?
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.