Delivery insights
See the flow.
Find the friction.
Follow the work that shipped, the work still waiting and the scope that changed. Use observed delivery to choose a useful next conversation.
Start with a question
Something feels stuck.
Take a closer look.
Choose an example to see how the measures can guide a discussion. The next step is to inspect the work and test your explanation with the team.
Illustrative investigation · no measured results shown
Where is work waiting?
Look at current work by stage alongside observed time in review. Open the waiting work to check dependencies, review capacity and the clarity of its acceptance criteria.
Useful next discussion · what would help reviews move?The work, from several angles
Know what moved.
And what’s waiting.
Choose a date range and work type. Narrow the view with the project, workflow, milestone or other available filters.
- First shipping and rework
- Separate work completed for the first time from later completion cycles after reopening.
- Changes in scope
- See work entering scope alongside completed, removed and reopened items in the selected period.
- Current work in progress
- See today’s open work grouped by workflow category, including the queues that deserve attention.
- Delivery timings
- Compare time from creation to first completion, current open-work age and observed blocked duration.
- Time in stage
- Explore how long work has spent in common workflow categories, using observed history.
- Workload distribution
- Where permitted, inspect assigned work, complexity and blocked items to discuss how work is distributed.
Project Insights follows the accessible project work. Administrators can use a broader workspace view. Workload counts describe allocation and support team decisions; they do not rank colleagues.
Understand the evidence
The explanation
comes with the number.
Switch a chart to its data table for exact values, full labels and sample counts. Check definitions and measurement coverage before comparing periods.
Read the delivery insights guideTypical and longer durations.
Timing views show the median, p50, and a longer-duration percentile, p85. The sample count helps you judge how much recorded history supports them.
Current and historical views.
Delivery events follow the selected date range. Work in progress, open-work age and workload describe what is open now.
Gaps stay visible.
Insufficient samples are withheld. Coverage explains when measurement began, keeping unrecorded history out of the result.
A shared outcome on the horizon
Connect the work.
Revisit the forecast.
Milestones link work across projects and teams around a shared outcome. Follow the remaining scope while the items stay in their original workflows.
When forecasting is enabled and enough history exists, inspect likely and conservative dates and an on-time probability. Changes in scope, estimates, delivery and blockers can change the outlook.
Explore outcome planningA date worth
discussing.
Customers can manage their reports without a support request.
What do the remaining scope and observed completions suggest about the target?
Check the blocked dependency and agree whether the scope or target needs to change.
Agent usage in context
See the usage
behind the work.
Explore known token usage attributed to visible work from reported agent runs. Shared runs can be allocated across work items, with approximate allocations and missing counters shown.
Use this alongside the work and its outcome. These client-reported figures describe recorded usage; provider billing remains separate.
Explore connected agentsRead the view with care
Better questions.
Better decisions.
Does a forecast commit the team to a date?
A forecast estimates future delivery from observed history and remaining work. Keep the agreed target and the predicted dates distinct, and revisit both when circumstances change.
What if there is too little recorded history?
Insights explains coverage and withholds timing percentiles when samples are insufficient. Milestone forecasts show Insufficient data until they have enough observed delivery to support an estimate.
How do insights connect to reviews?
Insights helps you investigate the flow. Reviews and retrospectives give the team a place to interpret the evidence, agree changes and turn those decisions into owned work. Explore learning practices.
COME TAKE A LOOK
A little less busy.
A lot more together.
Curious? Leave your email. We’ll keep you posted on early access and what’s new.