Use Cases
Conduct a postmortem
Features
Categories
Overview
Product, engineering and other teams need to conduct meaningful retrospectives that synthesize insights across project management tools, communication channels, and documentation. Perplexity's integrations with tools like Jira, Microsoft Teams, and Notion/OneDrive let you analyze an entire year of work to identify patterns, assess goal alignment, and extract strategic insights from a single query, eliminating hours of manual data gathering across disconnected platforms.
Your search
Connect your Jira, Microsoft Teams, and document storage (Notion/OneDrive) to Perplexity, then ask comprehensive retrospective questions using natural language. The search intelligently queries all connected tools to give you a complete strategic picture.
Review Jira tickets, Microsoft Teams channels and meeting notes for a retrospective on last year. Identify major wins and misses organized by strategic theme, and show how they align with our annual goals.
Perplexity automatically:
Analyzes Jira tickets across all projects, filtering by completion dates, priority, labels, and custom fields
Searches Microsoft Teams channels for strategic discussions, decisions, and retrospective comments
Reviews meeting notes and documents for goal definitions, quarterly reviews, and outcome assessments
Organizes findings by your company's strategic themes (e.g., "Customer Growth," "Platform Stability," "Developer Experience")
Maps achievements and gaps against documented annual objectives
Perplexity's answer
You get a comprehensive retrospective synthesizing data from all three platforms:
From Jira: Completed initiatives, feature releases, velocity metrics, blocked or abandoned projects, and bug resolution trends organized by strategic theme
From Microsoft Teams: Key decisions documented in channels, team sentiment from retrospectives, escalations and incident post-mortems, and leadership commentary on outcomes
From meeting notes: Quarterly goal definitions, OKR progress updates, strategic pivots, and lessons learned from planning sessions
The answer identifies patterns like "Customer Growth initiatives achieved 85% completion rate with strong user adoption metrics" or "Platform Stability goals missed due to infrastructure migration delays," connecting specific Jira tickets and Teams discussions to each insight. You'll see which strategic themes over-performed, which underperformed, and the root causes behind both—complete with citations to specific tickets, conversations, and documents.
Tips
Reference your strategic framework: Mention your specific themes like "ask about our Q1-Q4 OKRs" or "organize by our three pillar strategy"
Specify timeframes precisely: Use "calendar year 2025," "Q4 2024 through Q3 2025," or "since our annual planning in January"
Request actionable outputs: Ask "recommend engineering tickets to address gaps" or "suggest strategic initiatives for next year based on misses"
Compare periods: Try "how did H2 compare to H1 on customer-facing features?" to spot trends
Deep-dive on themes: Follow up with "show me all Teams discussions about why Platform Stability goals were missed" to understand context
Generate artifacts: Request "create a summary suitable for board presentation" or "draft Jira tickets to fix identified issues"