What top CTOs measure weekly that average CTOs measure quarterly.
Engineering metrics decay. A quarterly read of deploy frequency, change failure rate, or PR cycle time is a fossil — useful for governance, useless for management. The CTOs whose orgs ship fastest read the same four numbers every Monday morning, in under 10 minutes.
The DORA metrics — deploy frequency, lead time for changes, change failure rate, MTTR — are the closest thing engineering has to GAAP. But they were designed for benchmarking, not for management. Read quarterly, they tell you what already happened. Read weekly, they tell you what's about to happen. Across the 15 highest-performing engineering orgs in my coaching cohort, the CTO opens a single dashboard every Monday morning and reads four numbers in under 10 minutes. That weekly cadence — not the metrics themselves — is what compounds.
- Numbers presented in the board deck.
- Trends spotted 8–12 weeks after they started.
- Interventions discussed, rarely shipped.
- Engineers don't see the dashboard.
- Numbers read Monday 9am, 10 minutes, no slides.
- Trends spotted within 2 weeks of starting.
- Interventions shipped in the same week as the read.
- Dashboard is public to all engineers — and they look at it.
The two things never to put on the weekly dashboard
- Lines of code, PRs opened, or any per-person productivity metric. The minute it's on the dashboard, it's gamed. DORA's own research confirms this — individual metrics correlate negatively with team performance.
- Vanity uptime numbers (99.9% across all services). Aggregate uptime hides the one service that's at 97% and is the actual problem.
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.