cloudthinker-ai Engineering Metrics Dashboard
Phase 1: DORA Metrics
Track the four key metrics from the DORA research program.
| Metric | Current | Target | Elite Benchmark |
|---|---|---|---|
| Deployment Frequency | ___ / week | Multiple per day | |
| Lead Time for Changes | ___ hours | Less than 1 hour | |
| Change Failure Rate | ___% | 0-15% | |
| Mean Time to Recovery | ___ hours | Less than 1 hour |
Data Sources:
- Deployment frequency: source = ___
- Lead time: measured from ___ to ___
- Change failure rate: definition of failure = ___
- MTTR: measured from ___ to ___
Phase 2: Quality Metrics
| Metric | Current | Target | Trend |
|---|---|---|---|
| Bug escape rate (bugs found in prod) | |||
| Test coverage (%) | |||
| P1/P2 incidents per month | |||
| Tech debt ratio (% of sprint on debt) | |||
| Code review turnaround time | |||
| Build success rate (%) |
Phase 3: Operational Health
| Metric | Current | Target | Trend |
|---|---|---|---|
| Service availability (%) | |||
| P50 / P99 latency | |||
| Error rate (%) | |||
| On-call pages per week | |||
| Toil percentage (%) | |||
| Infrastructure cost per request |
Phase 4: Team Productivity
| Metric | Current | Target | Trend |
|---|---|---|---|
| Cycle time (commit to production) | |||
| PR merge time (avg) | |||
| Sprint velocity (rolling avg) | |||
| Work in progress (avg items) | |||
| Planned vs unplanned work ratio | |||
| Developer experience score (survey) |
Phase 5: Dashboard Design
- Select visualization tool: ___
- Define refresh frequency: ___
- Set up automated data collection pipelines
- Configure alerting for metrics that breach thresholds
- Ensure metrics are visible to the entire engineering org
- Add context annotations (deploys, incidents, re-orgs)
Anti-Gaming Guidelines:
- Use metrics for learning, not punishment
- Always pair efficiency metrics with quality metrics
- Review metric definitions quarterly
- Include qualitative feedback alongside quantitative data
Counter-Rationalizations
| Shortcut | Counter | Why |
|---|---|---|
| "We can skip some steps for this case" | Adapt the workflow steps, don't skip them | Skipped steps are where incidents and oversights originate |
| "The user seems to already know what to do" | Complete all workflow phases with the user | The workflow catches blind spots that experience alone misses |
| "This is a minor case, full process is overkill" | Scale the process down, don't turn it off | Minor cases become major when unstructured; the process scales, not disappears |
| "I'll fill in the details later" | Complete each section before moving on | Deferred details are forgotten; real-time capture is more accurate |
| "The template output isn't necessary" | Always produce the structured output format | Structured output enables comparison, audit trails, and handoff to other teams |
Output Format
Summary
- Organization: ___
- Reporting cadence: ___
- DORA performance level: Elite / High / Medium / Low
- Top improving metric: ___
- Metric needing attention: ___
Action Items
- Set up automated data collection for all metrics
- Build dashboard in selected visualization tool
- Establish baseline measurements for first reporting period
- Schedule recurring review meetings
- Communicate metric goals and anti-gaming guidelines to teams
- Review and refine metrics after first quarter