Internal Comms & Meetings

How to run a team retrospective as Small HR Teams

Internal Comms & MeetingsFor Small HR Teams3 apps11 steps~22 min to set up

Your Q4 retro is in two days and you're already dreading it. Last quarter's notes live in a Google Doc that three people edited, nobody agreed on the action items, and the follow-through was zero — you only know that because you're still chasing the same manager about the same onboarding gap six months later. Running a retro for 150 people across eight managers means you're the one scheduling it, running it, capturing it, and somehow turning 'communication could be better' into a follow-up plan. You don't have a chief of staff. You have Slack, a Notion page nobody reads, and a calendar that's already full.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small HR Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A structured retro session with real-time transcription, auto-generated summaries, and action items assigned to specific managers — so nothing gets lost between the meeting and Monday morning

A searchable archive of every past retro, so when someone asks 'didn't we talk about this last quarter?' you can pull the exact clip, not reconstruct it from memory

A running action-item tracker that links retro outputs to owners and due dates, so you can see at a glance what closed and what's been sitting open for three cycles

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 Task Manager Knowledge Management

Data sources & config

Meeting Notes captures the retro session in real time. Task Manager tracks action items with owners and due dates. Knowledge Management stores the Notion-backed archive — Starch syncs your Notion data on a schedule, so the knowledge base stays current without manual exports. For teams using Slack to share retro summaries, connect Slack from Starch's integration catalog; the agent queries it live to pull relevant threads into context.

Prompts to copy

Transcribe today's Q2 retro and generate a summary with: top three themes, decisions made, and every action item with the name of the person who owns it

Create tasks for each action item from the Q2 retro — assign to the right person, set due dates two weeks out, mark anything flagged as recurring as P1

Save the Q2 retro summary to the HR knowledge base under 'Retros > 2026', tag it with the themes discussed, and flag any action items still open from last quarter's retro as stale

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

Walkthrough

Step-by-step

1 Open Meeting Notes in Starch and start a new session named 'Q2 2026 Team Retrospective' before the call begins — it transcribes in real time so you're not typing while facilitating.

2 Run your retro normally. When the call ends, Meeting Notes auto-generates a summary with key decisions, themes, and raw action items surfaced from the conversation.

3 Review the summary immediately after the session and correct any name or context errors — this takes about four minutes, not forty.

4 Tell Starch: 'Create tasks for each action item from the Q2 retro — assign to the right person, set due dates two weeks out, mark anything flagged as recurring as P1.' Task Manager creates and assigns every item without a form.

5 Open Task Manager and do a 30-second check: does every task have a real owner (a name, not 'HR team'), a due date, and a priority? Reassign anything that landed in the wrong bucket.

6 Tell Starch: 'Save the Q2 retro summary to the HR knowledge base under Retros > 2026 and tag it with the themes discussed.' Knowledge Management files it, categorizes it, and makes it searchable.

7 Tell Starch: 'Flag any action items still open from last quarter's retro as stale and list them.' You'll get the short, uncomfortable list of things that didn't happen — surface it in the next manager sync, not six months from now.

8 Send each manager a Slack message with their specific action items from the retro. You can prompt Starch to draft these: 'Draft a Slack message to each manager with their retro action items, tone is direct and brief.'

9 Set a two-week Task Manager check-in by telling Starch: 'Remind me in two weeks to review retro action item completion and flag anything overdue.' The task appears with a due date so it doesn't slip.

10 At the start of the next retro, open Knowledge Management and search last quarter's summary. Pull the open items into your facilitation notes so the team sees what carried over — no pretending the last cycle didn't happen.

11 After three cycles, tell Starch: 'Summarize recurring themes across the last three retro summaries in the knowledge base.' You'll have a pattern report you can take to the CEO without building a deck.

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

Q2 2026 Retrospective — 22 attendees, 8 managers, June 17 2026

Sample numbers from a real run

Action items generated	14
Action items assigned to named owners	14
Tasks created in Task Manager (auto)	14
Open items carried over from Q1 retro	5
Stale items flagged by Starch	5
Time to file retro to knowledge base	3

The Q2 retro ran 75 minutes across eight managers and 14 ICs. Meeting Notes transcribed the session and surfaced 14 action items: three around onboarding documentation gaps (owner: Priya, People Ops), four around manager communication frequency (owners: Marcus and Dani), two around PTO visibility in Rippling vs. actual behavior (owner: HR team), and five miscellaneous. After the call, Starch created all 14 tasks in Task Manager with two-week due dates. When asked to check for stale items from the Q1 retro, Starch flagged five — including the onboarding documentation gap that Priya had owned since March. That item was escalated to P1 and added to the weekly HR standup. The retro summary was filed to the Notion-backed knowledge base under Retros > 2026 in under three minutes. Two weeks later, a Task Manager reminder surfaced the overdue items; 9 of 14 were closed, 5 were still open, and 2 were reassigned. No spreadsheet. No follow-up email to 8 managers asking for status.

Measurement

How you'll know it's working

Retro action item close rate by manager, tracked across cycles (target: >70% within two weeks)

Number of recurring themes across three or more consecutive retros — a signal of structural issues, not one-off friction

Time from retro end to action items assigned and filed (target: under 30 minutes)

Percentage of retro action items with a named human owner (not 'HR' or 'the team') at time of filing

Stale action items carried forward from the previous cycle — ideally trending to zero

Comparison

What this replaces

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

Google Docs + manual notes

Free and familiar, but action items get buried in prose, nobody checks the doc two weeks later, and there's no searchable archive — you reconstruct history from memory.

Notion retro template

Good for structure, but someone still has to take notes in real time, manually create tasks, and remember to update it — the admin burden stays on the two-person HR team.

Lattice or 15Five retrospective features

If you're already paying for performance management, some retro tooling is included, but it's scoped to structured review cycles and doesn't give you a searchable meeting archive or cross-app action tracking.

Otter.ai or Fireflies for transcription

Good at transcription alone, but you still manually extract action items, create tasks somewhere else, and file notes yourself — three separate tools to do what Starch handles end-to-end.

On Starch RECOMMENDED

One platform — meeting notes, task manager, knowledge 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 integrate with the tools we already use for retros — like Notion or Slack?

Yes. Starch syncs your Notion data on a schedule, so anything filed to the knowledge base is reflected in your existing Notion workspace. For Slack, connect it from Starch's integration catalog and the agent queries it live — useful for sharing retro summaries or pulling relevant Slack threads into context before a session.

We use Rippling and Greenhouse — can Starch pull data from those into retro prep?

Rippling and Greenhouse are reachable from Starch's integration catalog, where the agent queries them live when your app runs. So you can build a retro prep view that pulls headcount changes from Rippling and open roles from Greenhouse alongside your meeting history — describe what you want and Starch assembles it.

What happens if someone misses the live session — can they catch up?

Yes. Meeting Notes archives every retro in a searchable history. Anyone who missed it can search for the session by date or keyword and read the summary, decisions, and action items. They can also search for specific moments — 'what did we decide about the onboarding process' — and get the relevant section, not the full transcript.

Is Starch SOC 2 certified? We're cautious about where meeting data lives.

Starch is not currently SOC 2 Type II certified. If your organization has compliance requirements that make that a hard blocker, that's worth knowing upfront. It's on the roadmap. For a 2-person HR team at a 150-person company that isn't in a regulated industry, most teams find the current security posture acceptable — but we'd rather you know than assume.

Can Starch run the retro itself — like facilitate the session?

No — Starch captures and processes the retro, it doesn't run it. You still facilitate. What changes is what happens after: instead of spending 45 minutes cleaning up notes and chasing action item owners, Starch handles the summary, task creation, and filing so you can be done in under 30 minutes total.

We already have a Notion knowledge base that nobody reads. How is this different?

The problem with most Notion knowledge bases isn't the structure — it's that updates require a human to remember to do them, and search requires knowing what you're looking for. Starch's Knowledge Management app auto-files retro summaries when you tell it to, detects when documentation goes stale, and answers natural-language questions like 'what did we decide about manager check-ins last quarter' without you navigating the doc tree.