The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+List the top 10 exit pages for the last 30 days with exit rate, sessions ending there, and whether…
Execute — do the immediate task
+List the top 10 exit pages for the last 30 days with exit rate, sessions ending there, and whether those exits followed a specific landing page. Highlight any commerce pages (cart, checkout) that appear in the exits list so product can triage immediately.
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 send the exit-page report to product, make it review-ready: surface the top three exit…
Improve — make it easier to accept
+Before I send the exit-page report to product, make it review-ready: surface the top three exit pages with exit counts, annotate if exits coincide with error pages or slow load events, and flag any checkout step with exit rate above 30% so the engineers prioritize fixes.
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
+Step two of checkout now shows a surge in exits and revenue trended down. I’m worried a payment…
Decide — diagnose the stuck moment
+Checkout step 2 is suddenly high on the exit list and revenue dipped.
Step two of checkout now shows a surge in exits and revenue trended down. I’m worried a payment widget or validation change broke flow, but I don’t know if it’s a frontend error, a payment provider outage, or a wording change that confused users. What is most likely and what immediate checks will identify the root cause?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+After almost every release we see exits spike on checkout pages. We keep passing blame between…
Become — change the pattern
+Repeat spikes in exits on checkout pages after deployments
After almost every release we see exits spike on checkout pages. We keep passing blame between product, engineering, and payments. What habitual change — a release checklist that includes monitoring exits, a post-deploy smoke test for checkout, or a rollback trigger — will stop these recurring post-deploy failures?
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 web analytics work people do in Google Analytics.
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.