Module 1.1: Engineering Productivity Metrics
Master the metrics that define engineering as an economic activity: DORA, APER, Feature Velocity, and Lead Time. Learn to speak the language of finance.
🎯 What You'll Learn
- ✓ How to measure engineering productivity using the four DORA metrics
- ✓ How to calculate Revenue per Engineer (APER) with industry benchmarks
- ✓ How to identify and quantify your Innovation Tax
- ✓ How to package engineering metrics for board presentations
Lesson 1: The Four DORA Metrics
DORA (DevOps Research and Assessment) identified four key metrics that predict software delivery performance. These are the industry standard for measuring engineering organizations.
How often code deploys to production. Elite: on-demand (multiple times/day). Low: less than once per month.
Time from code commit to production deployment. Measures the speed of your delivery pipeline.
Percentage of deployments that cause a production failure requiring rollback or hotfix.
Time to restore service after a production incident.
Calculate each DORA metric for your team over the last quarter. Compare against the benchmarks above. Where does your team fall?
Lesson 2: Revenue Per Engineer (APER)
APER (Annual Productivity to Engineering Ratio) measures how much revenue each engineer generates. This is the bridge between engineering metrics and financial language.
Annual Revenue / Number of Engineers = Revenue per Engineer
Pre-revenue companies need modified APER using ARR trajectory. Post-PMF companies should target quarter-over-quarter improvement.
SaaS companies average $500K-$700K. Infrastructure companies: $800K+. Consumer apps: $300K-$500K. Enterprise: $600K-$1M.
Use the free APER calculator at /tools/aper to calculate your organization's Revenue per Engineer. Compare against stage and industry benchmarks.
Lesson 3: Feature Velocity & Innovation Tax
Feature Velocity measures how much of your engineering capacity goes to new features vs. maintenance. The Innovation Tax is the percentage consumed by non-feature work.
Percentage of engineering time spent on maintenance, bug fixes, support, and infrastructure. Healthy: < 30%. Dangerous: > 60%.
100% minus Innovation Tax = the percentage of engineering capacity available for new features and revenue-generating work.
More important than absolute velocity is the trend. Declining velocity = accumulating debt. Improving velocity = debt is being managed.
Survey your team leads: what percentage of sprint capacity goes to new features vs. maintenance/bugs/tech debt? Calculate your Innovation Tax.
Lesson 4: Board-Ready Metric Packaging
Raw engineering metrics mean nothing to boards and investors. This lesson teaches you how to translate engineering data into the financial language that drives decisions.
Instead of "we need to reduce tech debt," say "maintenance costs consume 45% of our engineering budget — $3.2M annually. Reducing to 30% frees $1.1M for feature development."
Boards care about trends, not snapshots. Show trajectory: "APER improved from $450K to $580K in 3 quarters, tracking toward our $700K target."
Numbers without context are meaningless. "Our MTTR of 2 hours puts us in the top 25% for our industry. We target top 10%."
Create a one-slide executive summary of your engineering organization using the metrics from Lessons 1-3. Include dollar amounts, trends, and benchmark comparisons.
📊 Module Assessment
Complete the following to demonstrate mastery of Module 1.1: