Focus Summary
See how your team's engineering capacity was distributed across work categories — features, bugs, maintenance, incidents, and reviews — over any time period.
The Focus Summary (/focus) answers the question every engineering leader asks after a sprint: where did the time actually go?
It breaks down your team's engineering effort across work categories, shows trends over time, and compares your distribution against industry benchmarks — so you can have an informed conversation about whether your team's attention is aligned with your priorities.
Work categories
Koalr classifies all engineering activity into six categories:
| Category | What counts |
|---|---|
| Feature | PRs and issues linked to feature epics or labeled feature, enhancement |
| Bug Fix | PRs or issues labeled bug, defect, or mapped to a bug-type issue in Jira/Linear |
| Tech Debt | Refactors, deprecations, and deliberate debt-paydown work |
| Maintenance | Dependency updates, chores, infrastructure work |
| Unplanned | Reactive work not committed to at sprint start (bugs, incidents, urgent requests) |
| Uncategorized | Activity that doesn't match any category — unlinked commits or unclassified PRs |
The Uncategorized percentage is a useful proxy for how well your team tracks work to issues.
The donut chart
The main view shows a donut chart of effort distribution over the selected date range. Hover any segment to see:
- Absolute count (commits, PRs, reviews)
- Percentage of total activity
- How this compares to your team's prior period
Trend chart
Below the donut, a stacked area chart shows how the distribution has shifted over the last 12 weeks. Look for:
- Bug % trending up — reactive work is increasing; consider a bug bash or root cause review
- Incident response spiking — on-call burden is unusually high; check PagerDuty for alert noise
- Maintenance crowding out features — tech debt is consuming capacity; may indicate accumulation of deferred work
Industry benchmarks
Koalr surfaces allocation benchmarks from industry research:
| Category | Healthy range |
|---|---|
| Feature | 60–75% |
| Bug Fix | 10–20% |
| Tech Debt | 10–15% |
| Maintenance | 5–10% |
These benchmarks come from Google DORA research and industry data. Your org's ideal allocation depends on your product maturity and team composition — use these as reference points, not hard targets.
Filters
- Date range: 7 days / 14 days / 30 days / 90 days
- Team: Scope to a specific team or view org-wide
Connection to Work Log
Focus Summary is the aggregate view; Work Log is the per-developer daily view. Use them together:
- Focus Summary to spot category imbalances at the team level
- Work Log to understand which specific developers are driving the pattern (and whether it's a structural issue or individual situation)
Data quality note
Category accuracy depends on your team's issue hygiene:
- PRs linked to issues → more accurate categorization
- Issues with correct type/labels in Jira or Linear → more accurate category mapping
- Unlinked commits → show up in "Uncategorized" and reduce signal quality
The Uncategorized percentage in your donut is a useful proxy for how well your team tracks work to issues.