Internal Comms & Meetings

How to run a team retrospective as Foundation and Nonprofit Ops Teams

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams3 apps10 steps~20 min to set up

Your four-person ops team runs two retrospectives a year — one after each grant cycle closes — and every time it's the same scramble. Someone digs through Slack to reconstruct what actually happened. Someone else finds the notes doc from the last retro, which lives in a Google Drive folder nobody bookmarked. You end up spending 90 minutes in a room surfacing the same three process breakdowns you surfaced six months ago, because nothing was tracked between sessions. Action items from the last retro lived in one person's notebook. Half your team has changed. The institutional memory needed to run a useful retro is scattered across Slack, Notion, email threads, and people's heads.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A searchable archive of every retrospective your team has run, with decisions, action items, and owners — so the next retro starts from what you actually resolved last time, not from scratch

A meeting-notes workflow that automatically extracts action items from your retro call, assigns them by name, and tracks completion so nothing disappears into a doc nobody opens again

A living knowledge base that connects your retro outputs to your actual operating context — grant-cycle timelines, board commitments, program-spend patterns — so process improvements are grounded in what's really happening

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

Data sources & config

Meeting Notes runs on your retro calls directly. Knowledge Management connects to Notion (Starch syncs your Notion data on a schedule) so retro outputs can be stored alongside your existing ops documentation. Slack is connected from Starch's integration catalog — the agent queries it live to pull relevant threads from the grant cycle being reviewed. Task Manager handles action-item tracking standalone; no external sync required for basic task capture.

Prompts to copy

Transcribe today's Q2 grant-cycle retrospective and generate a summary with: (1) what went well, (2) what broke down, (3) action items with owners and due dates, and (4) any decisions we made about changing our process going forward

Create a retrospective knowledge base for our foundation ops team. Each entry should include the grant cycle it covers, what worked, what we're changing, open action items, and a link to the full meeting notes. Surface past entries when I'm preparing for a new retro.

Add a task: [Name] to update our grant-agreement signature workflow by [date], flagged as P1, tagged 'retro-Q2-2026'

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

Walkthrough

Step-by-step

1 Two weeks before your retro, open Starch and prompt Knowledge Management to pull the previous retro's action items and flag which ones are still open. This replaces the 30-minute Slack archaeology session at the start of every retrospective.

2 Ask Starch to query your Slack channels from the grant cycle period — connect Slack from Starch's integration catalog — and surface recurring themes: process complaints, delays, anything that came up more than twice. Give this to your facilitator as pre-read.

3 If your team tracks program spend in QuickBooks, Starch syncs your QuickBooks data on a schedule. Ask it to pull any invoices or payments that were delayed or flagged during the grant cycle so you're looking at real data, not recollections.

4 Run your retro call with Meeting Notes active. It transcribes in real time so no one is assigned note-taker, and everyone can stay in the conversation.

5 After the call ends, Meeting Notes generates a summary with key decisions, what-went-well / what-broke-down sections, and extracted action items with the names of people who said they'd own each one.

6 Review the auto-extracted action items. Add them to Task Manager with priority levels (P1 for anything blocking the next grant cycle, P2-P3 for process improvements) and due dates tied to your program calendar.

7 Save the full retrospective — summary, decisions, action items — into Knowledge Management. Tag it with the grant cycle name and program area so it's findable next time.

8 Ask Knowledge Management to update any standing process documentation that was changed by decisions made in this retro. For example, if you decided to change your grant-agreement routing workflow, the doc describing that workflow should reflect the new process.

9 One week after the retro, prompt Task Manager to report on which action items are overdue or unassigned. Send that list to your team via Slack — connect Slack from Starch's integration catalog and the agent queries it live to post the update.

10 Before your next grant-cycle retro, prompt Knowledge Management to generate a one-page brief: what we decided last time, what we said we'd change, and how many of those action items were actually completed. This becomes your opening frame for the next session instead of starting from memory.

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 Grant Cycle Retrospective — July 2026

Sample numbers from a real run

Action items extracted from meeting	14
Action items still open from Q4 2025 retro	6
Slack threads surfaced as recurring pain points	23
Process docs updated post-retro	3
Days from retro to first overdue-action-item alert	7

Your Q2 grant cycle closed in June. Seven grants moved through the pipeline, two were declined at the board stage, and one agreement sat unsigned for 19 days because the routing sequence in DocuSign wasn't set up correctly. Before the July retro, you prompt Starch to pull the Q4 2025 retrospective from Knowledge Management — it surfaces 6 action items that were never closed, including 'fix DocuSign routing for multi-signatory agreements.' That item was assigned to your grants manager, who left in February. The retro now has a concrete opening: this is a recurring problem, not a one-time miss. During the call, Meeting Notes runs in the background. Afterward it generates 14 action items, including 3 flagged as P1 because they touch the Q3 cycle that starts in September. You add all 14 to Task Manager with owners and due dates. The DocuSign routing fix — now clearly a P1 — is assigned with a two-week deadline. One week later, Starch surfaces that 4 of the 14 items have no progress logged. You send the overdue list to your team Slack channel. By the time your Q4 retro rolls around, the Knowledge Management brief for that session will show that 11 of 14 Q2 action items were completed — a number your team can actually be accountable to.

Measurement

How you'll know it's working

Percentage of retro action items completed before the next grant cycle opens

Number of recurring process failures (same issue surfacing across two or more consecutive retros)

Days between retro call and action items fully assigned with owners and due dates

Board and funder commitments that were affected by process gaps identified in retros

Reduction in time spent on retro prep (reconstructing what happened vs. reviewing what was documented)

Comparison

What this replaces

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

Google Docs + Slack search

Zero cost but no structured action-item tracking, no automatic surfacing of past decisions, and retro prep still requires manual archaeology through message history

Notion standalone

Good for storing retro notes if someone actually formats and files them — but no transcription, no auto-extraction of action items, and nothing connects it to your QuickBooks spend or Slack threads from the grant cycle

Confluence + Jira

Solid for a 40-person program team with an admin to configure it; expensive and over-built for a four-person ops team that doesn't have time to maintain two enterprise tools

Dedicated retro tools (Parabol, EasyRetro)

Purpose-built for the retro ceremony itself but siloed — outputs don't connect to your grants data, your task list, or your team's operating docs, so action items still fall through the same cracks

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 use Notion for our ops documentation already. Will Starch duplicate everything or work alongside it?

Starch syncs your Notion data on a schedule — it reads what's there and can surface it inside Knowledge Management. You don't have to migrate anything. Your existing Notion pages stay where they are; Starch makes them queryable alongside your retro outputs and action items.

We only run two retrospectives a year. Is this overkill for that cadence?

The value isn't in the ceremony — it's in the 90 days between retros. Task Manager tracks whether the action items from your last retro are actually getting done. Knowledge Management surfaces the context you need when the next retro rolls around. Two retros a year with no follow-through is worse than one retro with documented accountability.

Can Starch pull in data from our grants-management system to inform the retro?

If your grants database is Salesforce, you can connect it from Starch's integration catalog — the agent queries it live. If you're using a browser-based system like Fluxx or Foundant that doesn't have an API connector in the catalog, Starch can automate it through your browser — no API needed. Either way, you can pull real cycle data into your retro prep instead of relying on memory.

What happens if someone on my team doesn't attend the retro? Can they get caught up?

Meeting Notes produces a full transcript plus a structured summary with decisions and action items. Anyone who missed the call can read it in five minutes and see exactly what was decided and what they're responsible for. It's also archived in Knowledge Management so it's findable three grant cycles from now.

Is Starch SOC 2 certified? We handle donor data and need to think about where it lives.

Starch is not SOC 2 Type II certified today. That's worth knowing if your foundation has strict data-handling requirements. The retrospective workflow itself — meeting notes, action items, process documentation — typically doesn't involve donor PII, but you should evaluate this against your own data governance policies before connecting systems that do.

We already have someone who takes notes in our retros. Why would we change that?

Keep them in the room. The issue isn't whether notes exist — it's that notes in a doc don't automatically become tracked action items, don't connect to your last retro's unresolved items, and don't feed a searchable knowledge base. Meeting Notes handles the transcription so your note-taker can focus on facilitation instead of typing.