Internal Comms & Meetings

How to run a team retrospective as DTC Brand Founders

Internal Comms & MeetingsFor DTC Brand Founders3 apps10 steps~20 min to set up

Your team retrospective happens in a Google Doc that nobody can find two weeks later, or in a Slack huddle where the action items live in someone's short-term memory. As a DTC founder you're running retros on top of a chaotic week — maybe CAC spiked on Meta, a Shopify fulfillment partner dropped the ball, or Klaviyo flows fired on the wrong segment. You need a 45-minute session that produces real decisions, not a feelings circle. Instead you get: no pre-read, three people repeating what happened on the Q4 promo, and a list of 'action items' that nobody owns. The doc from last retro is in a Notion page you forgot existed.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor DTC Brand Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A structured retro process where Meeting Notes captures every decision and action item automatically — so the founder isn't playing secretary while also facilitating

A living team wiki in Knowledge Management where retro outputs accumulate sprint over sprint, so 'didn't we already try that?' becomes a searchable answer instead of a debate

A closed loop between retro action items and your Project Management board, so tasks assigned in the meeting show up where the team actually works

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 Project Management

Data sources & config

Meeting Notes connects to your Google Calendar — Starch syncs your calendar data on a schedule — to identify retro events and auto-join. Knowledge Management connects to your Notion workspace — Starch syncs your Notion pages on a schedule — so existing docs are searchable context. Project Management runs natively inside Starch with no additional integration needed. For teams using Slack, connect Slack from Starch's integration catalog; the agent queries it live to pull in threads that are relevant context before the meeting.

Prompts to copy

Transcribe this retro call and generate a summary with: (1) what went well, (2) what went wrong, (3) every action item with the owner's name and due date. Flag any item that was also raised in our last three retros.

Create a Knowledge Management page titled 'Q2 Sprint 3 Retro — June 2026' and save the summary under our Retros database. Tag it with: fulfillment, paid-social, and Klaviyo.

For each action item in today's retro summary, create a Project Management task: assign it to the right person, set priority based on business impact, and due date as discussed. Group all of them under the 'Retro Actions' project.

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

Walkthrough

Step-by-step

1 Before the retro, tell Starch: 'Pull the last sprint's open action items from Project Management and any Slack threads tagged #retro, and generate a one-page pre-read.' Everyone walks in knowing the agenda.

2 Start your retro call — Google Meet, Zoom, or a plain phone call. Meeting Notes joins and transcribes in real time. You facilitate; you don't type.

3 Run your standard retro format (Start / Stop / Continue, or whatever your team uses). Meeting Notes captures attributions — it knows who said what — so you're not reconstructing later.

4 When the call ends, Meeting Notes generates a structured summary: what went well, what went wrong, decisions made, and a clean action-item list with owner names extracted from the conversation.

5 Review the summary — takes two minutes. Edit any misattributed names or garbled SKU numbers. This is the only manual step.

6 Tell Starch: 'Save this retro summary to Knowledge Management under our Retros database, tagged with the relevant topics.' The AI auto-categorizes and links it to prior retros on the same themes.

7 Tell Starch: 'For each action item, create a Project Management task with the assigned owner, due date, and link back to this retro page.' Tasks appear on the board before anyone has closed their laptop.

8 At the start of next week's standup, tell Starch: 'Show me all retro action items that are overdue or not yet started.' You get a two-line briefing, not a dig through Notion.

9 When a new team member joins, tell Starch: 'Build an onboarding path from our Knowledge Management retro history — summarize the five most recurring issues and how we resolved them.' They get institutional memory on day one.

10 Before the next retro, Starch flags: 'Three of this week's proposed action items have appeared in retros before without resolution.' You address the pattern, not just the symptom.

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

June 2026 Sprint 4 Retro — Post-Summer-Sale debrief

Sample numbers from a real run

Meta CAC spike — sunscreen SKU	0
Klaviyo welcome flow fired on existing customers	0
3PL picked wrong bundle variant on 214 orders	0
Action items created in retro	7
Action items with an owner and due date	7
Action items resolved by next retro (historical average before Starch)	3

Your summer sale ran June 14–16. CAC on the sunscreen bundle hit $38 against a $24 target, the Klaviyo welcome flow triggered on a segment that included 900 existing buyers (you found out from a reply-all complaint), and your 3PL shipped the wrong bundle variant on 214 orders worth roughly $6,800 in returns exposure. The retro on June 18 had six people, ran 50 minutes, and historically would have produced a Notion doc with 11 bullet points that nobody re-read. This time: Meeting Notes transcribed the call, surfaced that the 3PL variant issue was also flagged in the March retro (never resolved), and generated 7 action items — each with an owner. 'Fix Klaviyo suppression logic for existing customers' went to your email operator, due June 21. '3PL variant labeling audit' went to your ops lead, due June 25, and was linked to the March retro entry in Knowledge Management so she could see what was tried last time. By the June 25 check-in, 6 of 7 were closed. The one outstanding item was a Meta creative audit — still in flight, but tracked, not lost.

Measurement

How you'll know it's working

Action item close rate retro-over-retro (how many assigned items are actually done by next session)

Recurring issue rate — how many retro items appeared in a prior retro without resolution

Time from call end to tasks on the board (target: under 10 minutes)

Retro participation rate — did the whole core team show or did someone skip again

Knowledge Management search hit rate on retro content — are people actually using the archive

Comparison

What this replaces

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

Notion + manual notes

Notion is fine for storage but someone still has to type during the call, action items still have to be copy-pasted into Asana or Linear, and nothing flags when you're relitigating a problem from two months ago.

Otter.ai + Linear

Otter transcribes well, but you're manually triaging the transcript into action items and copying them into Linear — two tools, two logins, and the transcript archive and the task board never know about each other.

Loom async retro

Works for distributed teams but loses the live decision-making moment and produces video artifacts that nobody re-watches when a new hire joins six months later.

Google Docs retro template

Zero cost and everyone already has access, but action items live in the doc and not in any task system, and the archive is a folder full of 'Retro June 2025 FINAL v2' files that AI can't search across.

On Starch RECOMMENDED

One platform — meeting notes, knowledge management, project management 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

Does Starch actually join the call automatically, or do I have to paste a transcript?

Meeting Notes connects to your Google Calendar — Starch syncs your calendar data on a schedule — and can identify retro events so you're not setting this up each time. How you get audio into the transcription depends on your call setup; your Starch workspace will show you the options when you configure the app.

We use Slack for async retros sometimes. Can Starch pull in those threads?

Yes. Connect Slack from Starch's integration catalog; the agent queries it live. You can tell Starch to pull threads from a specific channel or date range and include them as pre-read context or append them to the retro summary in Knowledge Management.

What if my team uses Linear or Asana instead of Starch Project Management for tasks?

Linear and Asana are reachable from Starch's integration catalog, so the agent can query them live. You can describe the integration you want — 'when a retro action item is created in Starch, also create a task in Linear with the same owner and due date' — and Starch will build that automation. You don't have to abandon your existing task tool.

Is our retro data — what went wrong, team issues, frank feedback — stored securely?

Starch is not SOC 2 Type II certified today, so if your company has a compliance requirement that mandates certified vendors for internal communications data, that's worth knowing upfront. For most DTC operators running 5–20 person teams, this isn't a blocker, but it's honest to name it.

We've tried retro tools before and nobody used them after the first two sessions. What's different?

The friction that kills retro tools is the manual work after the call — someone has to turn notes into tasks, file them somewhere, and chase people. Starch eliminates that step: tasks go onto the board automatically, the summary is filed in Knowledge Management before the call window closes, and the next retro's pre-read pulls from what was committed last time. There's nothing for you to maintain between sessions.

Can Starch flag when we're repeating the same issue retro after retro?

Yes. Once your retro history is in Knowledge Management, you can prompt Starch before each session: 'Review our last six retro summaries and flag any action items or themes that recurred without resolution.' It returns a short list so you walk into the room knowing which patterns need a structural fix, not just another owner.