Internal Comms & Meetings

How to run a team retrospective as Chief of Staff and Founder's Office

Internal Comms & MeetingsFor Chief of Staff and Founder's Office3 apps12 steps~24 min to set up

You run retrospectives for a 150-person company where the inputs live in six different places. Action items from last quarter's retro are in a Notion doc nobody updated. Decisions made in the meeting get buried in a Slack thread by Thursday. Engineers reference a different set of OKR results than the sales team because each function pulled their own numbers. You spend 90 minutes before every retro manually hunting down what was agreed last time, whether it shipped, and which metrics actually moved — then another 30 minutes after writing up a summary that half the attendees won't read. The retro itself lasts 45 minutes. The logistics surrounding it cost you three hours.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Chief of Staff and Founder's Office3 apps12 steps~24 min to set up

Outcome

What you'll set up

A living retro tracker that pulls last cycle's action items from Notion and Slack, shows completion status before the meeting starts, and never makes you manually hunt for 'what did we actually agree to last time'

An AI-generated meeting summary that captures decisions, owners, and next-period commitments in a structured format — distributed to Slack automatically when the call ends

A searchable retro archive so when someone asks 'didn't we try this in Q3?' you can find the exact meeting, the exact decision, and who was in the room

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

Starch syncs your Notion workspace and Slack channels on a schedule, so retro action items and past decisions are always current. Google Calendar connects directly so Starch knows which meetings are retros and can trigger post-meeting summaries automatically. Connect project management tools like Asana, Linear, or Jira from Starch's integration catalog — the agent queries them live to check whether retro action items that became tickets actually closed.

Prompts to copy

Build me a retrospective tracker that shows open action items from our last three retros, who owns each one, whether it's complete, and the original due date. Pull from our Notion workspace and flag anything overdue.

After each retro meeting, generate a summary with: decisions made, action items with owners and due dates, and one 'what we'll do differently' commitment. Archive it to our retro history and post a digest to our #leadership Slack channel.

Create a project management board for retro action items with priority levels and due dates. Every time a new retro summary is created, auto-populate the board with the action items extracted from that meeting.

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

Walkthrough

Step-by-step

1 Connect Notion and Slack as scheduled-sync sources. Starch pulls your existing retro docs, decision logs, and any #retro or #leadership threads where action items were discussed.

2 Open the Knowledge Management app and tell Starch: 'Find all action items from our last four quarterly retros in Notion, list them with owner and status, and flag any that have no update in 30+ days.' This becomes your pre-retro briefing doc.

3 Connect Google Calendar. Starch identifies your recurring retrospective meetings and knows when the next one is scheduled — you don't have to trigger anything manually.

4 Before the retro, Starch generates a pre-read: open items from last cycle, completion rate, and the two or three things that slipped without explanation. You share it to Slack 24 hours before the meeting.

5 Run the retro. Meeting Notes transcribes in real time. You focus on the conversation; Starch handles the record.

6 When the call ends, Meeting Notes generates a structured summary: what was discussed, decisions made, action items with named owners, and any explicit commitments for next period. Review takes under five minutes.

7 The summary is archived automatically in Knowledge Management under your retro history. Every past retro becomes searchable — decisions, owners, dates, and outcomes in one place.

8 New action items from the retro are pushed into your Project Management board. Each item gets a priority level, an owner, and a due date pulled from what was said in the meeting.

9 Starch posts a digest of the retro summary to your designated Slack channel — three to five bullets, decisions made, and who owns what next. No manual write-up required.

10 Two weeks before the next retro, Starch runs an automatic check: which action items are complete, which are in progress, which have gone quiet. It surfaces this as a short status report in Slack so you're not scrambling the morning of.

11 Over time, the Knowledge Management app builds a retro corpus. When a functional lead asks 'have we discussed this before?' you search the archive and return the exact meeting, the decision, and whether it was ever followed through.

12 Customize the summary template and Slack digest format by telling Starch what to change: 'Add a 'what we won't do' section to the retro summary template and remove the sentiment section — we don't use it.'

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

Q1 2026 Company Retrospective — March 28, 2026

Sample numbers from a real run

Open action items entering the retro	14
Items completed or closed	9
Items with no update in 30+ days (flagged)	3
New action items created in the retro	7
Time to distribute post-retro summary	4

Going into the Q1 retro, Starch pulled 14 open action items from the previous three retro docs in Notion and cross-referenced them against the #leadership Slack channel and the project management board. Nine had closed — three of those were confirmed from Jira tickets queried live from Starch's integration catalog. Three items had no update in over 30 days: a pricing page audit owned by marketing, a hiring calibration doc that was supposed to go to the exec team, and a vendor contract review. Starch flagged all three in the pre-read, which was posted to Slack the night before. The meeting ran 50 minutes. Meeting Notes transcribed it, and the post-meeting summary — 6 decisions, 7 new action items with named owners and due dates — was in Slack within four minutes of the call ending. The 7 new items were on the project board before the next morning's standup. The chief of staff spent 20 minutes total on retro logistics, down from the usual three hours.

Measurement

How you'll know it's working

Action item completion rate: percentage of retro commitments closed before the next retro

Time-to-distribute: minutes from retro end to summary in Slack

Decision retrieval: whether a past decision can be found in under 60 seconds when someone asks about it

Retro prep time: hours spent manually assembling context before the meeting

Owner accountability rate: percentage of action items that have a named, single owner (not 'the team')

Comparison

What this replaces

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

Notion retro docs + manual Slack summary

You already do this — the problem is the Notion doc goes stale by week two and the Slack summary is the one thing you cut when the day gets long.

Confluence + Jira

Solid if you have an ops person who keeps both up to date; at a 150-person company without a dedicated program manager, it becomes shelfware within one quarter.

Loom async retros

Good for distributed teams that want to skip the synchronous meeting entirely, but doesn't solve the action item tracking or pre-read problem — you still have to do that manually.

Dedicated retro tools (Parabol, EasyRetro, TeamRetro)

Purpose-built for the retro ceremony itself, but completely isolated from your Notion docs, Slack history, and project management board — you're back to copying action items by hand.

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

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

Starch works alongside Notion, not instead of it. Starch syncs your Notion workspace on a schedule, reads your existing retro pages, and surfaces action items, decisions, and stale content through its own apps. Your team keeps editing in Notion. Starch just makes the content actually useful before the next meeting.

What happens if the retro is informal — no agenda, just a Zoom call with the leadership team?

Meeting Notes transcribes any call. It doesn't need a formal agenda. After the call, you review the AI-generated summary, edit anything that's wrong, and publish. The structure comes from Starch's extraction, not from you pre-formatting an agenda.

Can Starch check whether a retro action item that became a Jira or Linear ticket actually got done?

Yes. Connect Jira or Linear from Starch's integration catalog; the agent queries either live when it runs a status check. You can tell Starch: 'Check which retro action items from Q1 have a matching closed ticket in Jira' and it will cross-reference and report back.

Does Starch store all our retro content? What are the data limits?

Starch stores what you build in the Knowledge Management and Meeting Notes apps. The Notion sync is a scheduled pull — it reads your Notion data and makes it queryable inside Starch, but Starch is not a long-horizon data warehouse. If you need archived Notion content going back several years, keep Notion as the system of record; Starch surfaces and connects it, it doesn't replace it.

Is this useful if retros happen at the team level, not just the company level?

Yes. You can build separate retro trackers for engineering, sales, and exec-level retros, each pulling from the relevant Slack channels and Notion sections. The Meeting Notes app isn't tied to a single meeting type — it captures any recurring meeting and archives it searchably.

We're not SOC 2 certified internally. Is Starch?

Starch is not SOC 2 Type II certified today. If your company requires SOC 2 Type II from every vendor that handles internal meeting data, that's worth noting before you set this up for sensitive leadership conversations.