Insights
Insights show how work moves across the workspace and inside each team.
They answer practical operating questions: what moved, where time went, what changed in review, and whether work still matches the plan.
What Insights show
Insights combines completed work, planning, review, and taxonomy signals into workspace and team charts.
At the workspace level, Insights shows the full operating view: activity mix, initiative allocation, pull request flow, code change trends, and work distribution.
At the team level, use the same charts through a team filter. If standups are enabled, team Insights can also show standup duration and attendance cards.
Individual Insights are smaller today: they focus on the person's work type distribution.
Chart types
The dashboard renders chart cards only when enough data exists for the selected scope, period, and timezone. These examples mirror the chart cards and help text used in the dashboard; your values come from the connected workspace.
Planned vs Unplanned Work
Distribution of planned and unplanned completed work
Activity Distribution
% of all completed tasks related to each activity
Read the signal
Start with the question the team is trying to answer.
Is planned work getting interrupted?
Planned vs. Unplanned Work compares completed initiative work with urgent bugs, requests, and other unplanned work.
Are initiatives moving?
Roadmap Progress shows which initiatives are getting completed work and which ones are quiet.
Is review slowing delivery?
Pull Request Flow tracks lead time, review time, merge pace, and PR volume.
Where is work concentrated?
Taxonomy Analytics compares work by product, customer, goal, skill, and coding tool.
What did agents touch?
Agent Analytics shows agent-attributed work without counting agent sessions as separate completed work.
Measurement principle
Insights are only as useful as the work graph behind them. Clear initiatives, honest statuses, linked pull requests, team ownership, and consistent taxonomy make the charts easier to trust.
Metrics point to where to look next. They are not a scorecard for individual performance and they are not a replacement for reading the underlying initiatives, bugs, comments, pull requests, and blockers.
Set the period and timezone before comparing charts. That keeps time-based charts aligned with how the team actually works.
Insights become more useful after you set up integrations, keep initiatives current, and apply taxonomy where it helps planning or reporting.