The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Before the full send, email a test version to me and to Priya in content on Thursday by noon. Use…
Execute — do the immediate task
+Before the full send, email a test version to me and to Priya in content on Thursday by noon. Use three test addresses that represent a Gmail inbox, an Outlook desktop, and an iPhone Mail app. Confirm that links, images, personalization and the unsubscribe link all work, and note any rendering issues.
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 test email make approvals fast. Include a screenshot of how the message appears on desktop…
Improve — make it easier to accept
+Make the test email make approvals fast. Include a screenshot of how the message appears on desktop and mobile, report missing alt text and any links that go to staging instead of production, and list any merge tags left unresolved. Highlight one issue that would make a reviewer hold the send.
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
+My test email looked fine on desktop but the mobile preview stacked blocks badly and the CTA was…
Decide — diagnose the stuck moment
+Test email displayed broken layout on mobile
My test email looked fine on desktop but the mobile preview stacked blocks badly and the CTA was off-screen. I’m worried we’ll lose clicks and trigger complaints. I don’t know which content block or CSS is causing it or whether it affects only certain devices. What quick diagnostic pinpoints the offending block, what immediate fix gets the CTA visible, and how do I rerun a focused test before Friday?
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 sending after quick tests and later find rendering problems across clients. That creates…
Become — change the pattern
+We run informal tests that miss key viewports
We keep sending after quick tests and later find rendering problems across clients. That creates rework and small but recurring revenue loss. Suggest a standard testing checklist for desktop, mobile, and major clients, one small automation or workflow to capture screenshots automatically, and a required approval gate so nothing goes live without these checks.
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 email marketing work people do in Mailchimp.
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.