63 campaign retrospective global skill

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners.

by minhnv0807·MIT license·★ 599 Stars on the repo·GitHub ↗

Use now

Files of 63 campaign retrospective global

minhnv0807/master1 file shown
SKILL.md
Show the full text166 lines

Campaign Retrospective (Global)

A retrospective is not for assigning blame — it is how the team and the system get better after every campaign. The best insight comes from failure, but only if it is safe to speak honestly. A retro with no action is wasted time: every lesson must become one concrete change in the playbook, the Brand Hub, or the process.

Information gathering

Ask up to 4 questions:

  1. Which campaign, and over what dates? Name, start and end dates, original objective.
  2. Final data: revenue, leads, CPA, ROAS, spend — final numbers versus target. (If a report already exists from 07-marketing-report-global, use it as the input.)
  3. Who attends the retro? Content, performance, design, sales, leader?
  4. How long ago did the campaign end? Run the retro within 5 days of the end, while memory is fresh.

Principles

  1. Mandatory after every major campaign. No skipping because the team is busy. No retro means paying tuition without learning the lesson.
  2. Record only claims backed by data. "Creative A felt strong" is not an insight; "creative A hit $18 CPA against a $28 account average" is.
  3. No individual blame. Talk about systems and process. Everyone has the floor.
  4. Every lesson becomes one concrete change — to the playbook, a template, the Brand Hub, or a process — with an owner and a deadline.
  5. Document so it still makes sense in 6 months — and link the retro into the next campaign's brief.

Workflow

1. Prepare (before the session)
  • Pull final data: revenue, leads, CPA, ROAS, spend, timeline adherence, budget variance.
  • Send the data to the team before the meeting — the meeting is for discussion, not for reading numbers.
  • Book 60 minutes with a named facilitator (usually the leader). For distributed teams, pick a time that works across the relevant timezones and require written pre-reads from anyone who cannot attend live.
2. Campaign scorecard
KPI Target Actual % achieved vs previous campaign
Revenue
Leads
CPA
ROAS
Spend
Timeline (on schedule?)
Budget (within plan?)

Overall verdict: Success (>90% of KPIs) / Mixed (60-90%) / Miss (<60%).

When comparing against category benchmarks, use the right region and industry row in references/benchmarks-global.md — and adjust for seasonality before declaring a CPA increase a failure, since Q4 media costs run materially above Q1.

3. What worked (repeat next time)
# What worked Evidence (numbers) Why it worked How to apply next time
1
2
3

Name the winning patterns explicitly:

  • Content angle: which angle converted best
  • Creative format: video / image / carousel — which performed
  • Audience: which segment responded
  • Timing: which day or hour performed best
  • Channel: best CPA and ROAS
4. What did not work (avoid next time)
# What failed Evidence Root cause Decision: stop / fix / retest
1
2

Root cause must go past the symptom. "The ads were bad" is not a root cause; "audience overlapped with the previous campaign > frequency rose above 4 > CTR fell below 1%" is.

5. Surprises
  • Positive surprises: what beat expectations, by how much, why — what do you take from it?
  • Negative surprises: what came in worse, by how much, why — how do you prevent it?
6. Process and execution review
Item Assessment Problems hit Improvement
Brief quality
Timeline adherence
Team communication
Review and approval process
Launch-day execution
Data and tracking setup

Biggest process bottleneck: the single thing most worth fixing next time.

7. Team callouts

Record specific contributions: [Name] — [the specific contribution and its positive impact on the result]. Recognize publicly, correct privately.

8. Playbook and Brand Hub updates plus action items
Document to update What changes Owner Deadline
Launch playbook (60-launch-playbook-global) Add or amend step: [X] Leader
Campaign brief template Adjust section: [Y] Leader
Brand Hub — customer insight Add new insight from this campaign: [Z]
Brand Hub — KPI framework / internal benchmarks Update the benchmarks you actually achieved (CPA, CVR)
Winning creative library Store the winners plus the reason they won

Every action item needs an owner and a deadline — never "the whole team will handle it."

9. Input for the next campaign
  • 3 things to definitely repeat: 1... 2... 3...
  • 3 things to definitely do differently: 1... 2... 3...
  • Hypothesis to test next campaign: [hypothesis + how it will be measured]

Facilitation guide

  • Timing: within 5 days of campaign end.
  • Format: 60 minutes, full team, facilitator (leader): 10 min scorecard > 15 min what worked > 15 min what did not > 10 min process > 10 min action items and owners.
  • Ground rules: no individual blame, systems and process only; everyone speaks; constructive, not a venting session.
  • After: the leader publishes the document within 24 hours, shares it with the team and leadership, and links it into the next campaign brief.

Output structure

File name: campaign-retro-[campaign-name]-[YYYYMMDD].md — the 9 sections above: scorecard > what worked > what did not > surprises > process review > team callouts > playbook and Brand Hub updates > input for the next campaign > action items with owners.

  • 07-marketing-report-global: the final report supplies the scorecard data.
  • 60-launch-playbook-global: execution lessons are written directly back into the playbook.
  • 02-campaign-brief-global: the "lessons from the previous campaign" section of a new brief comes from this retro.
  • 34-ai-marketing-os-global: new insights and real benchmarks are written into the Brand Hub.
  • 65-team-performance-review-global: team callouts and observations feed individual reviews at period end — keep the two documents separate.

Quality checklist

  • Retro run within 5 days of campaign end
  • Scorecard covers all KPIs against target with a Success/Mixed/Miss verdict
  • Every "what worked" and "what did not" entry has numeric evidence — no impressions
  • Failures trace to a real root cause, not a symptom
  • Benchmark comparisons adjusted for region, industry, and season
  • At least one playbook update and one Brand Hub update
  • Every action item has an owner and a deadline
  • 3 things to repeat, 3 things to change, and a hypothesis for next time
  • No individual blame anywhere in the document
  • Document shared within 24 hours and linked into the next campaign brief
1---
2name: 63-campaign-retrospective-global
3description: "Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`."
4metadata:
5 version: 1.0.1
6 category: operations
7license: MIT
8triggers:
9 - "campaign retrospective"
10 - "campaign retro"
11 - "post-mortem"
12 - "campaign debrief"
13 - "what worked what did not"
14 - "lessons from the campaign"
15 - "campaign wrap-up"
16output: "File .md — full retrospective: scorecard, what worked / did not / surprises, process review, playbook and Brand Hub updates, input for the next campaign, action items with owners"
17related:
18 - 07-marketing-report-global
19 - 60-launch-playbook-global
20 - 02-campaign-brief-global
21 - 34-ai-marketing-os-global
22 - 65-team-performance-review-global
23---
24 
25# Campaign Retrospective (Global)
26 
27> A retrospective is not for assigning blame — it is how the team and the system get better after every campaign. The best insight comes from failure, but only if it is safe to speak honestly. A retro with no action is wasted time: every lesson must become one concrete change in the playbook, the Brand Hub, or the process.
28 
29## Information gathering
30 
31Ask up to 4 questions:
32 
331. **Which campaign, and over what dates?** Name, start and end dates, original objective.
342. **Final data:** revenue, leads, CPA, ROAS, spend — final numbers versus target. (If a report already exists from `07-marketing-report-global`, use it as the input.)
353. **Who attends the retro?** Content, performance, design, sales, leader?
364. **How long ago did the campaign end?** Run the retro within 5 days of the end, while memory is fresh.
37 
38## Principles
39 
401. **Mandatory after every major campaign.** No skipping because the team is busy. No retro means paying tuition without learning the lesson.
412. **Record only claims backed by data.** "Creative A felt strong" is not an insight; "creative A hit $18 CPA against a $28 account average" is.
423. **No individual blame.** Talk about systems and process. Everyone has the floor.
434. **Every lesson becomes one concrete change** — to the playbook, a template, the Brand Hub, or a process — with an owner and a deadline.
445. **Document so it still makes sense in 6 months** — and link the retro into the next campaign's brief.
45 
46## Workflow
47 
48### 1. Prepare (before the session)
49 
50- Pull final data: revenue, leads, CPA, ROAS, spend, timeline adherence, budget variance.
51- Send the data to the team before the meeting — the meeting is for discussion, not for reading numbers.
52- Book 60 minutes with a named facilitator (usually the leader). For distributed teams, pick a time that works across the relevant timezones and require written pre-reads from anyone who cannot attend live.
53 
54### 2. Campaign scorecard
55 
56| KPI | Target | Actual | % achieved | vs previous campaign |
57|-----|--------|--------|------------|----------------------|
58| Revenue | | | | |
59| Leads | | | | |
60| CPA | | | | |
61| ROAS | | | | |
62| Spend | | | | |
63| Timeline (on schedule?) | | | | |
64| Budget (within plan?) | | | | |
65 
66Overall verdict: **Success** (>90% of KPIs) / **Mixed** (60-90%) / **Miss** (<60%).
67 
68When comparing against category benchmarks, use the right region and industry row in `references/benchmarks-global.md` — and adjust for seasonality before declaring a CPA increase a failure, since Q4 media costs run materially above Q1.
69 
70### 3. What worked (repeat next time)
71 
72| # | What worked | Evidence (numbers) | Why it worked | How to apply next time |
73|---|-------------|--------------------|---------------|------------------------|
74| 1 | | | | |
75| 2 | | | | |
76| 3 | | | | |
77 
78Name the winning patterns explicitly:
79 
80- Content angle: which angle converted best
81- Creative format: video / image / carousel — which performed
82- Audience: which segment responded
83- Timing: which day or hour performed best
84- Channel: best CPA and ROAS
85 
86### 4. What did not work (avoid next time)
87 
88| # | What failed | Evidence | Root cause | Decision: stop / fix / retest |
89|---|-------------|----------|------------|-------------------------------|
90| 1 | | | | |
91| 2 | | | | |
92 
93Root cause must go past the symptom. "The ads were bad" is not a root cause; "audience overlapped with the previous campaign > frequency rose above 4 > CTR fell below 1%" is.
94 
95### 5. Surprises
96 
97- **Positive surprises:** what beat expectations, by how much, why — what do you take from it?
98- **Negative surprises:** what came in worse, by how much, why — how do you prevent it?
99 
100### 6. Process and execution review
101 
102| Item | Assessment | Problems hit | Improvement |
103|------|------------|--------------|-------------|
104| Brief quality | | | |
105| Timeline adherence | | | |
106| Team communication | | | |
107| Review and approval process | | | |
108| Launch-day execution | | | |
109| Data and tracking setup | | | |
110 
111Biggest process bottleneck: the single thing most worth fixing next time.
112 
113### 7. Team callouts
114 
115Record specific contributions: [Name] — [the specific contribution and its positive impact on the result]. Recognize publicly, correct privately.
116 
117### 8. Playbook and Brand Hub updates plus action items
118 
119| Document to update | What changes | Owner | Deadline |
120|--------------------|--------------|-------|----------|
121| Launch playbook (`60-launch-playbook-global`) | Add or amend step: [X] | Leader | |
122| Campaign brief template | Adjust section: [Y] | Leader | |
123| Brand Hub — customer insight | Add new insight from this campaign: [Z] | | |
124| Brand Hub — KPI framework / internal benchmarks | Update the benchmarks you actually achieved (CPA, CVR) | | |
125| Winning creative library | Store the winners plus the reason they won | | |
126 
127Every action item needs an owner and a deadline — never "the whole team will handle it."
128 
129### 9. Input for the next campaign
130 
131- 3 things to definitely repeat: 1... 2... 3...
132- 3 things to definitely do differently: 1... 2... 3...
133- Hypothesis to test next campaign: [hypothesis + how it will be measured]
134 
135## Facilitation guide
136 
137- **Timing:** within 5 days of campaign end.
138- **Format:** 60 minutes, full team, facilitator (leader): 10 min scorecard > 15 min what worked > 15 min what did not > 10 min process > 10 min action items and owners.
139- **Ground rules:** no individual blame, systems and process only; everyone speaks; constructive, not a venting session.
140- **After:** the leader publishes the document within 24 hours, shares it with the team and leadership, and links it into the next campaign brief.
141 
142## Output structure
143 
144File name: `campaign-retro-[campaign-name]-[YYYYMMDD].md` — the 9 sections above: scorecard > what worked > what did not > surprises > process review > team callouts > playbook and Brand Hub updates > input for the next campaign > action items with owners.
145 
146## Related skills
147 
148- `07-marketing-report-global`: the final report supplies the scorecard data.
149- `60-launch-playbook-global`: execution lessons are written directly back into the playbook.
150- `02-campaign-brief-global`: the "lessons from the previous campaign" section of a new brief comes from this retro.
151- `34-ai-marketing-os-global`: new insights and real benchmarks are written into the Brand Hub.
152- `65-team-performance-review-global`: team callouts and observations feed individual reviews at period end — keep the two documents separate.
153 
154## Quality checklist
155 
156- [ ] Retro run within 5 days of campaign end
157- [ ] Scorecard covers all KPIs against target with a Success/Mixed/Miss verdict
158- [ ] Every "what worked" and "what did not" entry has numeric evidence — no impressions
159- [ ] Failures trace to a real root cause, not a symptom
160- [ ] Benchmark comparisons adjusted for region, industry, and season
161- [ ] At least one playbook update and one Brand Hub update
162- [ ] Every action item has an owner and a deadline
163- [ ] 3 things to repeat, 3 things to change, and a hypothesis for next time
164- [ ] No individual blame anywhere in the document
165- [ ] Document shared within 24 hours and linked into the next campaign brief
166 

Discussion

Alternatives

/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Data & AI · MITAnalytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Creator · MITEarnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly. · MITPath A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".Creator · MIT