campaign-postmortem

Files (6)

• ONBOARDING-PROMPT.md
• README.md
• SCHEMA-MAP.md
• SETUP.md
• SKILL.md
• metadata.yaml

SKILL.md (first lines)

# Campaign Postmortem

## Use When

A marketing team needs to understand what happened in a campaign and turn the learning into better next-cycle decisions.

## Workflow

1. Confirm campaign name, date range, goals, channels, and audience.
2. Gather approved source material: brief, launch plan, project notes, performance data, meeting notes, and team feedback.
3. Build a timeline of major decisions, launch events, results, and follow-up actions.
4. Compare goals to actual results with source references.
5. Separate observations from interpretations.
6. Identify what worked, what did not work, root causes, and open questions.
7. Recommend what to repeat, change, or stop.
8. Add an action register with owners, dates, and unresolved decisions when available.

## Zapier MCP And SDK Role

- Use Zapier MCP to gather approved campaign docs, conversations, dashboards, CRM context, meeting notes, and tracker state.
- Use Zapier SDK for retro intake, scheduled reminders, reviewer routing, action logging, and follow-up tracking.
- Keep metrics, claims, and broad sharing review-gated.

## Output Format

- Executive summary
- Source list
- Campaign timeline
- Goal vs. actuals
- What worked
- What did not work
- Root causes and caveats
- Repeat / change / stop
- Action register

## Guardrails

- Never invent metrics, attribution, causes, or owner commitments.
- Label missing data and conflicting evidence.
- Keep the retro focused on systems, decisions, and process, not personal blame.
- Require human review before sharing broadly or updating source-of-truth records.

From zapier/gtm-cheat-codes, MIT.

More from zapier/gtm-cheat-codes