Insights
Insights show how work moves across the workspace and inside each team: what moved, where time went, how review is going, and whether work still matches the plan. Open Insights in the sidebar.
Team insights require a paid plan. Workspace insights stay available without it.
Choose a scope
- Workspace: activity mix, initiative allocation, pull request flow, code change trends, token usage, and work distribution.
- Team: the same charts filtered to one team, plus standup duration and attendance when the team runs standups.
- Individual: a person's work type distribution.
Set the period and time zone before comparing charts, so time-based charts match how the team works.
Initiative and bug detail pages show the same metrics scoped to that item. See Initiatives for the card list.
Chart types
A chart only appears once there is enough data for the selected scope, period, and time zone. The examples below use sample data; your charts use your workspace's data.
Planned vs Unplanned Work
Distribution of planned and unplanned completed work
Activity Distribution
% of all completed tasks related to each activity
Start from a question
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.
Get trustworthy charts
Charts are only as good as the work behind them. Connect your tools, keep initiative statuses and owners current, link pull requests to work, and apply taxonomy consistently.
Use metrics to decide where to look next, not to score individuals. Read the initiatives, bugs, comments, and pull requests behind a number before acting on it.