Internal Comms & Meetings

How to run a team retrospective as Small Marketing Teams

Internal Comms & MeetingsFor Small Marketing Teams4 apps10 steps~20 min to set up

Your three-person marketing team runs retrospectives in a Notion doc that someone half-fills in the day before, a Zoom call where half the action items get lost in chat, and a follow-up Slack message nobody threads correctly. Two weeks later, when the demand gen lead asks 'didn't we already try that campaign structure in Q3?' nobody can find the answer. Retro notes live in four different places — Notion, Zoom recordings, Gmail threads, someone's personal to-do list. Action items from last sprint's retro are still open and nobody noticed. You're too small to have a chief of staff and too busy to run a tight retro process from scratch every two weeks.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Marketing Teams4 apps10 steps~20 min to set up

Outcome

What you'll set up

A structured retro app in Starch that captures what worked, what didn't, and what to change — then auto-extracts action items and assigns them to the right person on the team

A searchable archive of every retro your marketing team has ever run, so you can actually answer 'did we try this before?' with a real answer instead of a shrug

A standing automation that surfaces open action items from the previous retro at the start of each new one, so nothing carries forward silently for six sprints

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Meeting Notes Knowledge Management Task Manager Project Management

Data sources & config

Starch connects directly to Notion (scheduled-sync provider) so your existing campaign briefs, previous retro docs, and project notes are searchable inside the Knowledge Management app. Gmail is synced on a schedule so the retro app can surface relevant email threads — like the campaign recap you sent the CEO — as context during the session. For Slack, connect it from Starch's integration catalog and the agent queries your #marketing channel live to pull any retro-relevant threads when the app runs. No new tool stack required — Starch sits on top of what you already have.

Prompts to copy

Build me a marketing team retrospective app. Each retro should have four sections: what we shipped this sprint, what worked (with specific campaigns or tactics), what didn't work (with root causes where we know them), and action items with owner and due date. Pull in any open action items from the previous retro automatically so we review them first.

Create a knowledge base for our marketing retro archive. Every time we complete a retro, save the summary here and tag it by quarter, campaign theme, and channel (paid, content, lifecycle, events). Make it searchable so I can ask 'when did we last test a webinar-to-trial sequence?' and get the answer.

Add a task to remind me every other Thursday at 9am to prep the retro agenda — pull the three most recent open action items from our retro archive and include them in the reminder.

Create a project called 'Marketing Retro Actions' and auto-populate it with action items from today's retro. Assign each item to the right person, set priority based on impact to pipeline, and flag anything that's been open more than two sprints.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Start the Meeting Notes app in Starch before your retro call. It transcribes in real time so your demand gen lead can run the conversation instead of typing notes, and the lifecycle person isn't half-listening while they try to keep up.

2 At the end of the call, Meeting Notes generates a structured summary with key decisions highlighted and action items extracted — including who said they'd own each one, based on the transcript.

3 Open the retro app you built in Starch. Review the auto-populated 'open from last sprint' section first. Any action item that's still open gets a status update — closed, in progress, or explicitly deprioritized — before you move to new items.

4 Work through the four sections: what shipped, what worked, what didn't, and what changes next sprint. For 'what worked,' pull in real numbers — Starch can query your HubSpot deals live from the integration catalog to show which campaign source drove the most MQLs this sprint.

5 For 'what didn't work,' reference the Growth Analyst app if you've set it up — it pulls PostHog and Gmail data together to show where qualified traffic dropped off or where nurture sequences underperformed.

6 Finalize action items inside the retro app. Each item gets an owner (one of your three names), a due date, and a priority level. Starch creates corresponding tasks in the Task Manager or Project Management app automatically — no copy-paste.

7 The retro summary is saved to the Knowledge Management app and tagged by quarter, sprint number, and campaign theme. Next time someone asks 'when did we test gated content as a lead gen channel?' the answer is a search query, not a conversation.

8 Starch posts a retro summary to your Slack channel — connect Slack from Starch's integration catalog — so the rest of the company (including the CEO) sees what the marketing team shipped, learned, and committed to next, without you writing a separate update.

9 The following sprint, when you open the retro app, it surfaces all action items from this retro with their current status. Anything still open gets flagged. You spend the first five minutes of the next retro on accountability, not archaeology.

10 Quarterly, use the Knowledge Management app to pull every retro from the past three months and ask Starch to summarize recurring themes — which channels keep underperforming, which tactics keep getting deprioritized, which action items keep reopening. Use that as input for your quarterly marketing review with the CEO.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 Sprint 6 Marketing Retro

Sample numbers from a real run

Open action items carried from Sprint 5	4
Items closed before Sprint 6 retro	2
New action items created in Sprint 6 retro	6
Sprint 6 MQLs attributed to content (HubSpot live query)	38
Sprint 6 MQLs attributed to paid (HubSpot live query)	21
Retros archived in Knowledge Management (Q1 + Q2 so far)	11

Sprint 6 retro opens with four items still open from Sprint 5 — two closed, two still in progress. The demand gen lead ran the retro on camera while Starch transcribed. Key finding: the April webinar-to-trial sequence drove 38 MQLs against a target of 30, but the LinkedIn Ads campaign that was supposed to amplify it underdelivered by 40% because the creative brief was delayed. That delay traced back to a Sprint 4 action item — 'establish a 10-day lead time for paid creative' — that was marked done but never enforced in practice. Because every retro is archived in the Knowledge Management app, the team could search 'creative lead time' and pull up exactly when they flagged this the first time, three sprints ago. Six new action items were created: one each for the demand gen lead (rebuild the LinkedIn Ads brief template), the content lead (move webinar promotion to a 14-day runway), and the lifecycle lead (A/B test subject lines in the webinar confirmation sequence). Starch posted a three-paragraph summary to #marketing-updates in Slack within two minutes of the retro ending. The CEO replied within the hour. No separate write-up required.

Measurement

How you'll know it's working

Action item close rate sprint-over-sprint (what percentage of last retro's action items are done before the next one starts)

Average age of open action items in the marketing retro backlog

MQL volume by channel cited in retro 'what worked' sections, tracked over rolling quarters

Number of recurring retro themes (tactics that appear in 'what didn't work' more than twice in a quarter — signal of a structural problem vs. one-off)

Time from retro end to summary posted to Slack (proxy for how much manual overhead the process still has)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Notion retro template + Zoom recording

You still own all the synthesis work — someone has to watch the recording, extract action items, update the Notion doc, and post the summary to Slack; Starch handles those steps.

Miro or FigJam async retro boards

Good for design-heavy or distributed teams doing sticky-note retrospectives, but the output is a board, not a structured document with assigned tasks and a searchable archive.

Fellow.app

Purpose-built for meeting notes and action items, but it doesn't connect to your HubSpot deals, Notion docs, or Slack channel to give the retro actual campaign context — Starch does.

Linear or Asana for retro action tracking

Solid task trackers, but they require someone to manually move retro action items into the tool after every session; Starch creates the tasks directly from the retro output.

On Starch RECOMMENDED

One platform — meeting notes, knowledge management, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We already use Notion for retro docs. Does Starch replace that or work with it?

Starch syncs your Notion data on a schedule, so your existing retro docs, campaign briefs, and project notes are searchable inside Starch without you migrating anything. You can keep writing in Notion if you want — Starch surfaces and connects that content. Over time, most teams move the structured retro itself into Starch because the action item extraction and task creation happen automatically.

Can Starch pull in HubSpot deal data to give the retro real campaign context?

Yes. Connect HubSpot from Starch's integration catalog and the agent queries your deals live when the retro app runs. You can ask it to show MQLs by source for the sprint, which campaigns are in 'proposal' stage, or which deals moved backward — giving the retro actual numbers instead of vibes about what worked.

What if our retro action items live in Slack threads right now and we want to import them?

Connect Slack from Starch's integration catalog and the agent can query your #marketing channel live to pull threads that look like action items. You'd describe what you want — 'find all messages in #marketing from the last two weeks that have a checkbox or say someone will do something by a date' — and Starch extracts them. It won't be perfect on the first pass, but it's faster than reading 200 messages yourself.

Is Starch SOC 2 certified? We'd be putting retro notes with campaign strategy in here.

Not yet — Starch is not SOC 2 Type II certified today. If that's a hard requirement for your company's vendor approval process, it's an honest blocker right now. It's on the roadmap. For a three-person marketing team at a 120-person company, most teams make the call based on what data they're actually putting in — retro notes and action items are lower-risk than customer PII.

We run retros async, not on a call. Does the Meeting Notes app still help?

The Meeting Notes app is built around transcription of live calls. For fully async retros — where people fill in a doc over 48 hours — you'd skip Meeting Notes and go straight to the custom retro app you build in Starch. The action item extraction, Knowledge Management archiving, and Slack posting all still work; you just don't get real-time transcription.

What about Customer.io or Klaviyo data? Can we pull campaign performance into the retro?

Connect Customer.io or Klaviyo from Starch's integration catalog and the agent queries them live. You can ask Starch to pull open rates, click rates, and conversion rates for the sequences you ran this sprint and surface them in the 'what worked / what didn't' section of the retro. No BI tool required — just describe what you want to see.