Skip to main content
AI Features

Theme Insights

What Theme Insights Are

Theme insights is an AI feature that analyzes patterns across multiple retrospectives to identify recurring themes, persistent challenges, and improvement trends over time. While individual retrospectives capture a snapshot of a single sprint, theme insights connect the dots across weeks and months to reveal the bigger picture.

Teams often discuss the same issues sprint after sprint without realizing the pattern. Deployment problems might surface in slightly different forms across five retros. Communication gaps might appear under different labels. Theme insights brings these patterns to the surface so your team can address root causes rather than symptoms.

Theme insights analyzes completed retrospectives only. It does not access retrospectives that are still in progress. You need at least three completed retrospectives for meaningful insights to be generated.

How to Generate Theme Insights

To generate a theme insights report for your team:

  1. Navigate to the team dashboard for the team whose retrospectives you want to analyze.
  2. Click the "Theme Insights" tab in the dashboard navigation, or find it in the analytics section.
  3. Select the time range you want to analyze. Options include the last 4 weeks, last 8 weeks, last quarter, or a custom date range.
  4. Click "Generate insights" to start the AI analysis. This may take 10 to 20 seconds depending on the number of retrospectives in the selected range.
  5. Review the insights report that appears on the page.

Theme insights can also be generated at the organization level by administrators who want to see patterns across multiple teams. Organization-level insights aggregate themes while keeping team-specific details appropriately separated.

Understanding the Insights Report

A theme insights report is organized into several sections that build a comprehensive picture of your team's retrospective patterns.

Recurring themes

The report identifies themes that have appeared in multiple retrospectives within the selected time range. Each recurring theme includes:

  • Theme name — A descriptive label for the recurring topic, such as "Code review bottlenecks" or "Sprint planning estimation accuracy."
  • Frequency — How many retrospectives featured cards related to this theme.
  • Trend direction — Whether the theme is appearing more often, less often, or at a stable rate. An upward trend may indicate a growing problem; a downward trend suggests improvement.
  • Representative cards — A selection of anonymized card excerpts from different retros that illustrate the theme.

Sentiment analysis

For each recurring theme, the AI assesses the overall sentiment of related cards. This helps distinguish between themes that are purely pain points, themes that are improving, and themes that are already working well but at risk of regression. Sentiment is displayed as a simple scale:

  • Positive — Cards related to this theme are predominantly celebratory or appreciative.
  • Mixed — The theme has both positive and negative cards, suggesting an area in transition.
  • Negative — Cards are predominantly frustrated or critical, indicating an unresolved problem.

Action item effectiveness

The report cross-references recurring themes with action items created in past retrospectives to assess whether previous commitments had an impact. For each theme, you can see:

  • How many action items were created to address this theme.
  • How many of those action items were completed.
  • Whether the theme's frequency or sentiment changed after the action items were implemented.

The action item effectiveness section is one of the most valuable parts of the report. It helps your team see whether the changes you committed to actually made a difference, creating a feedback loop that improves the quality of future action items.

Emerging themes

In addition to recurring patterns, the AI identifies themes that appeared for the first time in recent retrospectives. These are flagged as emerging themes because they may represent new challenges or opportunities that are worth monitoring. Catching these early can prevent a small issue from becoming a persistent problem.

Summary and recommendations

The report concludes with a narrative summary of the team's retrospective patterns and two to four high-level recommendations. These recommendations synthesize the data into suggested focus areas for the team's next few sprints.

Using Insights to Drive Improvement

Generating the report is only the first step. Here is how to use theme insights to create real change on your team:

  1. Share with the team — Present the insights report at the start of a sprint planning session or a dedicated improvement meeting. Make the data visible so the whole team can discuss what they see.
  2. Prioritize persistent themes — Themes with high frequency and negative sentiment that have not improved despite past action items deserve focused attention. Consider dedicating a specific improvement initiative to these areas.
  3. Celebrate positive trends — When the report shows a theme trending downward in frequency or shifting from negative to positive sentiment, acknowledge the team's progress. This reinforces the value of the retrospective process.
  4. Monitor emerging themes — Keep an eye on new themes flagged in the report. Discuss them briefly in the next retro to determine whether they need immediate attention or can be observed for another sprint.
  5. Revisit action item quality — If the action item effectiveness section shows that completed action items did not change the underlying theme, the problem may be with action item specificity rather than follow-through. Consider using AI drafting to write more targeted action items.

Theme insights works best with honest, detailed retrospective data. If your team's cards are consistently vague or if participation is low, the AI will have less material to work with and the insights may be superficial. Investing in card quality through card coaching pays dividends in the quality of theme insights over time.

Regenerating and Comparing Reports

You can generate theme insights as often as you like. Each report is saved and timestamped, so you can compare insights from different time periods to see how your team's patterns evolve. This longitudinal view is especially valuable for managers and agile coaches who want to track team health over quarters or longer.

To compare reports, open the theme insights tab and select two saved reports from the report history dropdown. The comparison view highlights themes that have appeared, disappeared, or shifted in sentiment between the two report periods.

Organization-Level Insights

Organization administrators on the Enterprise plan can generate theme insights across all teams in the organization. This cross-team view surfaces patterns that no single team might notice, such as company-wide tooling frustrations, shared infrastructure bottlenecks, or cultural themes that cut across team boundaries. Organization-level insights aggregate data while respecting card anonymity and team boundaries.