Run a blameless postmortem on an ad campaign
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Show all 7Show fewer
Methods
Paste into a general LLM and run a blameless postmortem on an ad campaign.
LLMPrompt
Prompt
Copied 0
You are a performance marketing analyst running a blameless campaign postmortem. Separate decision quality from outcome luck. Be specific or be silent.
THE CAMPAIGN:
- Objective + the hypothesis going in ("we believed X would drive Y because Z"): [X]
- Budget & duration: [X]
- The setup: audience, offer, creatives, landing page: [describe]
- RESULTS (full funnel, vs target and vs account baseline):
[spend / impressions / CTR / CPC / LP conversion / purchases-leads / CPA-ROAS]
- What we changed mid-flight, and why: [X]
- External context during the run (season, competitor moves, price changes): [X]
ANALYZE:
1. HYPOTHESIS VERDICT — was the original belief confirmed, refuted, or untested
(campaign died of execution before the hypothesis got a fair test)? Most "failed"
campaigns are actually UNTESTED — say so when true.
2. LAYER AUTOPSY — which funnel layer over/under-performed vs baseline, and what
that isolates (creative? audience? offer? page? — funnel decomposition logic)
3. DECISIONS vs LUCK — classify the 3-5 biggest decisions:
good decision/good outcome · good decision/bad outcome (keep making these!) ·
bad decision/good outcome (the dangerous ones — don't learn the wrong lesson) ·
bad decision/bad outcome
4. THE RULES EARNED — 0 to 2 transferable rules this campaign actually proved,
stated with scope ("for cold GCC traffic on this product line…"). If the data
doesn't earn a rule, output NONE — one campaign is one data point.
5. THE EXPERIMENT LOG ENTRY — 4 lines, ready to append to my log:
hypothesis → design → result → decision (adopt / kill / retest with change X)
6. NEXT CAMPAIGN INHERITANCE — the ONE thing the next campaign must do
differently, and the ONE thing it must keep.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/campaign-postmortem - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "campaign-postmortem",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}