This week we’ve been focused on shipping an all-new version of an old feature, our meeting summaries. Although we’ve made some improvements over the years, this has been overdue for a fresh take. While meeting summaries sound super exciting 😏, what I’m keen on sharing is how our bets—the features we’re investing in—are stacking up. Let’s dig in.

Product roadmap bets

The meeting summaries will be built on two new features: Pages and Insights.

The bet behind Pages is that we can reduce friction in how folks get information and knowledge in and out of meetings and collaborative activities. We think there’s a market for a tool that drives meetings and workflows with embedded knowledge management.

The bet behind Insights is that leaders and teams will make use of trends and insights from data across meetings and teams to make better decisions and plans. We want to help folks understand what they already know and help them answer the question: what now?

Meeting summaries as pages

The new meeting summary pages will allow folks to customize their insights by asking questions of their meeting data. They’ll be able to shape the notes and outputs of the meeting directly, and organize them alongside other team knowledge. Soon, we plan to enrich this with video call transcriptions. In the future, we may offer summary templates that users can customize.

While we hope these summary pages are a big improvement, we’re eager to learn a few things:

• How might users discover and use insights across meetings and teams, not just for a single meeting?
• Will folks reach for this feature, or are we expecting too much behavior change?
• Do the insights across meetings and teams actually help leaders and teams understand their data, build knowledge, and answer the question: what now?

The big picture

Perhaps the biggest bet is on the platform as a whole. We think there’s a virtuous cycle between getting information and knowledge into a collaborative activity (via embedded knowledge management, integrations, and imports), enabling workflows that help teams make sense of that data and decide what to do next, and then building those learnings back into the organization’s knowledge and insights.

To support this, we’re building a tool that powers customizable workflows for many meeting formats (e.g. retros and estimation), collaborative activities (e.g. brainstorming and prioritization), and team processes (e.g. collecting feedback or team health surveys). The bet here is that by enabling more processes across an organization, the knowledge, trends, and insights gained will inform cross-functional decisions and planning. Teams can get started with Parabol by reaching for templated solutions to the problem they’re trying to solve, and the platform will adapt to them from there.

This is the product roadmap we’re focused on; we’re iterating toward this vision. So we make bets upon bets upon bets, learn, and ask ourselves: what now?

---

Originally published as Parabol Friday Ship #451