Campaign Retrospective Report

63 campaign retrospective global

by minhnv0807 · MIT license · ★ 599 on GitHub

63 campaign retrospective global cover

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,…

---
name: 63-campaign-retrospective-global
description: "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`."
metadata:
  version: 1.0.1
  category: operations
license: MIT
triggers:
  - "campaign retrospective"
  - "campaign retro"
  - "post-mortem"
  - "campaign debrief"
  - "what worked what did not"
  - "lessons from the campaign"
  - "campaign wrap-up"
output: "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"
related:
  - 07-marketing-report-global

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add minhnv0807/ai-business-skills --skill 63-campaign-retrospective-global -g -a claude-code
Claude Code (degit)npx degit minhnv0807/ai-business-skills/skills/en/63-campaign-retrospective-global#master ~/.claude/skills/63-campaign-retrospective-global
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md8.4 KB
Read SKILL.md here
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 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 599
Checked
Source
minhnv0807/ai-business-skills ↗
Creator
minhnv0807 · 150 listings
View creator

Similar skills

See all →
SkillExperiment Dashboard Vieweralirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillLinkedIn Analytics Dashboardcharlie947/social-media-skills · by charlie947Turn 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.★ 3.7k GitHub starsSkillEarnings Report Previewhimself65/finance-skills · by himself65Generate 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.★ 3.3k GitHub starsSkillPerformance Measurement Auditormichael-denyer/pstack-claude · by michael-denyerVet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.★ 1k GitHub starsSkillApp Bug Reportermicrosoft/power-platform-skills · by microsoftUse when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.★ 954 GitHub starsSkillAgency Client Dashboardindranilbanerjee/digital-marketing-pro · by indranilbanerjeeBuild the agency dashboard across all client brands: health, pacing, risk. "how are all our clients doing"★ 866 GitHub stars

More from minhnv0807

SkillMarketing Plan Builderminhnv0807/ai-business-skills · by minhnv0807Dung khi can ke hoach marketing tong the cho mot ky — muc tieu, phan khuc, kenh, ngan sach, timeline, KPI va ma tran rui ro. Co ca che do ban day du va che do ke hoach 1 trang cho chu doanh nghiep nho. Kich hoat khi user nhac 'lap ke hoach marketing', 'ke hoach MKT', 'marketing plan', 'chien luoc marketing nam', 'plan quy toi', 'ke hoach 1 trang'. Khong dung cho — tinh nguoc ngan sach tu doanh thu thi dung skill 10-tinh-kpi-nguoc; phan bo ngan sach chi tiet theo kenh thi dung skill 61-budget-planning; brief mot chien dich cu the thi dung skill 02-brief-chien-dich.★ 599 GitHub starsSkillOverall Marketing Strategyminhnv0807/ai-business-skills · by minhnv0807Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.★ 599 GitHub starsSkillContent Calendar Plannerminhnv0807/ai-business-skills · by minhnv0807Use when the user needs a monthly or weekly content calendar — posting schedule per channel, funnel ratio, content pillars, repurposing matrix, and an owner per slot. Trigger on 'content calendar', 'posting schedule', 'what should we post this month', 'editorial calendar', 'social media plan', 'we post randomly with no plan'. Also use when the user only says the team keeps running out of things to post. Not for — the brief for one specific post, see `36-content-brief-global`; the caption text itself, see `37-social-caption-global`; deciding next period content from last period data, see `40-next-content-plan-global`; a paid campaign timeline, see `02-campaign-brief-global`.★ 599 GitHub starsSkillContent Posting Scheduleminhnv0807/ai-business-skills · by minhnv0807Dung khi can lich dang bai cho ca thang — chot content pillar va ti le, xep bai theo ngay va khung gio, ma tran tai su dung noi dung, va gan muc tieu cho tung tru cot. Kich hoat khi user nhac 'lich noi dung', 'content calendar', 'thang nay dang gi', 'len lich dang bai', 'ke hoach content thang', 'phan bo noi dung'. Khong dung cho — brief tung bai truoc khi viet thi dung skill 36-content-brief; viet caption thanh pham thi dung skill 37-caption-social; lap plan ky sau tu data thi dung skill 40-next-content-plan.★ 599 GitHub starsSkillCampaign Execution Briefminhnv0807/ai-business-skills · by minhnv0807Dung khi can brief mot chien dich cu the cho ca team thuc thi — muc tieu, thong diep, deliverable, timeline phan cong theo tuan, gate duyet va ma tran rui ro. Kich hoat khi user nhac 'brief chien dich', 'ke hoach campaign', 'len brief cho team', 'chien dich thang toi', 'phan cong campaign', 'timeline chien dich'. Khong dung cho — ke hoach marketing ca ky thi dung skill 00-ke-hoach-mkt; danh sach asset can thiet ke thi dung skill 41-campaign-asset-list; giao viec cho tung nguoi thi dung skill 64-team-brief.★ 599 GitHub starsSkillCampaign Brief Frameworkminhnv0807/ai-business-skills · by minhnv0807Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.★ 599 GitHub stars