#480 – Turning Transcripts into Action
Friday Ship #480 | February 27th, 2026

This week we held our Cycle 12 User Feedback Retro. It’s our time to look at how the product is actually surviving in the wild.
First, What’s Working
It’s always a boost to see where we’re hitting the mark.
UX & Anonymity
Users continue to praise the clean UI and the safety of our anonymity features, which remain the “secret sauce” for honest team reflections.
Insights for Knowledge Sharing
One user highlighted how our Insights feature can be used to help team leads share learnings, encouraging transfer of knowledge across the org.
Second, What’s Missing or Getting Users Stuck
Meeting Transcripts
We’ve been talking about transcripts for a while, but this time instead of thinking we need to build our own tool, users want a way to integrate what they already use. They want Parabol to just “grab” the minutes from Zoom or Google Meet and put them in the right place. We’re moving toward an integration that augments meeting summaries after the call for a more complete summary.
API vs MCP
As part of our “Agent Epoch”, we’ve been debating the best way to let AI agents interact with Parabol. Our takeaway? A solid, secure GraphQL API is actually what power users and bots need most. We’re doubling down on refactoring our permissions to make our API the easiest way for users to point their own AI agents at their Parabol data.
Metrics

Usage is holding steady as we head into Spring. We are still digging into why the spike in Web Sessions but a decrease in New Web Users.
This week we…
…caught a bug during our own retro that we quickly fixed. Always good to be eating our own dogfood drinking our own champagne.
…added the ability to search by Linear issue number.
Next week we’ll
…kick off Cycle 13 shaping.