OKR Tracker
Automatically map your engineering OKRs to real delivery metrics — no manual updates required.
Overview
The OKR Tracker connects your high-level engineering objectives to measurable delivery outcomes computed from your GitHub, Jira, and incident data. Unlike static spreadsheet OKRs, Koalr's OKR Tracker updates in real time as your team ships.
Default OKR objectives
Koalr ships four engineering-focused objectives that map to industry-standard KPIs:
1. Accelerate delivery velocity
| Key Result | Target | Source |
|---|---|---|
| Deploy frequency | ≥ 5 deploys/day | Deployment events |
| Cycle time (PR merge time) | ≤ 2 days | PR data |
| Throughput (merged PRs) | ≥ 40 PRs/month | PR data |
2. Improve deployment reliability
| Key Result | Target | Source |
|---|---|---|
| Change failure rate | ≤ 5% | Deployments + incidents |
| MTTR | ≤ 60 minutes | Incident data |
| DORA tier | Elite | Composite |
3. Strengthen code quality
| Key Result | Target | Source |
|---|---|---|
| PR review coverage | ≥ 90% | PR review data |
| Mean time to first review | ≤ 4 hours | PR review timing |
| Code churn rate | ≤ 15% | Commit data |
4. Reduce technical debt
| Key Result | Target | Source |
|---|---|---|
| Test coverage | ≥ 75% | Codecov / SonarCloud |
| PR size (median lines changed) | ≤ 300 lines | PR data |
| Deploy risk score (mean) | ≤ 30 | Risk scoring engine |
Reading the dashboard
Overall progress gauge
The top-of-page gauge shows aggregate progress across all objectives. 100% = all key results at target; 0% = all at zero. This is an average of objective-level progress, not a weighted sum.
Objective cards
Each objective card shows:
- Progress bar — what % of the key results are at target
- Key results table — current value, target, trend indicator (↑↓ or →)
- Trend — "improving", "stable", or "declining" based on week-over-week change
Trend indicators
- Improving (green) — metric moved ≥ 5% toward target vs. prior period
- Stable (grey) — metric within ±5% of prior period
- Declining (red) — metric moved ≥ 5% away from target
Time range
Select 7, 14, 30, or 90 days. Targets are the same regardless of time range; current values are computed for the selected window. The prior period (used for trend comparison) is the same duration immediately before the selected window.
Interpreting OKR progress
What 100% means
A key result reaches 100% when the current value meets or exceeds the target. Values slightly above target still show 100% (the system doesn't penalize overperformance).
What 0% means
A key result at 0% means there is no data for that metric in the selected period (e.g., no deployments, no integrations connected), or the metric is far below target.
Target customization
The default targets are based on DORA Elite tier benchmarks. They are intentionally ambitious. If your team is at the "Medium" tier, you may want to set intermediate targets as stepping stones.
Using OKR data in retrospectives
The OKR Tracker is designed as a conversation starter, not a performance scorecard. Recommended use:
- Sprint planning — use current OKR progress to identify which dimension to focus on
- Retrospectives — review which key results improved or declined over the sprint
- Quarterly reviews — present overall progress to engineering leadership with trend context
- Goal-setting — adjust targets when a key result consistently hits 100% (signal to raise the bar)
Connection to DORA
The OKR Tracker's first two objectives ("Accelerate delivery velocity" and "Improve deployment reliability") directly reflect DORA's four key metrics. Progress here is the same signal you see in DORA Metrics, just expressed as a progress bar rather than a tier label.