30-45% of engineering time produces zero customer value. Here's a 4-week audit process that identifies exactly where time goes and the AUDIT cadence for continuous productivity improvement.
Last year, our CEO asked why it took 6 engineers 4 months to build a feature our competitor shipped in 6 weeks with 3 people. I didn't have a good answer. I had excuses: our codebase was more complex, our requirements were different, we had more edge cases. All true. None satisfying.
That question drove me to build a structured approach for auditing engineering productivity. Not the fluffy "are your developers happy?" kind of audit. A systematic examination of where engineering time actually goes, what's blocking throughput, and what specific changes would have the highest impact.
I've now run this audit at three organizations. Every single time, it revealed that 30-45% of engineering time was being consumed by activities that produced zero customer value. Not because engineers were slacking. Because the systems, processes, and tooling around them were broken in ways nobody had quantified.
# The Contrarian Take: Productivity Isn't About Working Faster
Most productivity initiatives focus on making engineers work faster: better tools, fewer meetings, more "focus time." That's optimizing the wrong variable. The biggest productivity gains come from eliminating work that shouldn't exist.[1]
In every audit I've run, I find that engineers spend more time on non-value work than actual feature development:
Activity
% of Engineering Time
Value Category
Writing and reviewing code
32%
Direct value
Debugging and incident response
18%
Necessary but reactive
Waiting (CI, reviews, environments)
17%
Pure waste
Meetings and communication
15%
Mixed value
Tooling and environment issues
10%
Pure waste
Rework (bugs, scope changes)
8%
Avoidable waste
That's 35% of engineering time in the "waste" categories. For a team of 20 engineers at $200K average fully loaded cost, that's $1.4M per year spent on waiting, fighting tools, and redoing work.
Treat the workflow timestamp interval above as an approximation. For execution duration, inspect workflow jobs and their completion times.
From your incident tracker:
Count incidents per month, mean time to resolution, and which components caused them. This data usually lives in PagerDuty, Opsgenie, or a spreadsheet.
Observe 3-5 engineers for a working day each, with their agreement, and log the workflow interruptions you are trying to understand. Keep the observation focused on system constraints and discuss what the record misses with the participant.[5]
I've never done a shadow session that didn't reveal something the automated data missed. In one session, I watched an engineer spend 45 minutes trying to reproduce a bug locally because the staging environment didn't match production. That doesn't show up in any dashboard.
The review-wait item scores highest in this weekly comparison. Onboarding still needs attention, but its quarterly frequency must be converted to the same period before ranking it against recurring weekly waits.
Deliver findings as a prioritized list with expected ROI for each fix. I limit recommendations to 5 items. More than that and nothing gets done.
markdown
## Engineering Productivity Audit - Recommendations### 1. Containerize development environment- **Impact:** Save 32 engineer-days per year on setup- **Cost:** 2 weeks of platform engineering time- **Capacity return:** 3.2x in the first year, assuming one engineer spends 10 working days on the two-week implementation- **Metric to track:** Time from "laptop received" to "first PR merged"### 2. Implement review SLA with automated assignment- **Impact:** Reduce cycle time by 40%- **Cost:** 3 days to set up, ongoing process change- **ROI:** 4.5 hours/week/engineer recovered- **Metric to track:** P50 and P90 time to first review### 3. Parallelize CI pipeline- **Impact:** Reduce CI time from 28 to 9 minutes- **Cost:** 1 week of DevOps engineering- **ROI:** 57 engineer-hours/month recovered- **Metric to track:** P50 CI duration
A - Assess quarterly. Full data collection from git, CI, and incident systems. 1 day of effort once you've built the scripts.
U - Understand through surveys. Same 10 questions every quarter. Track trends. A question that drops from 3.5 to 2.8 is an early warning.
D - Deep-dive semi-annually. Full shadow sessions and cross-referencing. This is the expensive part. Do it twice a year.
I - Implement the top 3. Not top 5. Not top 10. Three items per quarter. Finish them completely before taking on more.
T - Track relentlessly. Every recommendation gets a metric. Review metrics monthly. If a fix didn't move the metric, understand why.
The hardest part of the audit isn't collecting data or making recommendations. It's getting leadership to prioritize productivity improvements over feature work. Frame it in dollars: "This audit identified $1.4M in annual waste. Each recommendation includes its expected capacity return, implementation cost and assumptions. We will track whether the proposed savings are realised."
I've never seen a leadership team say no to those numbers. The key is having the data to back them up, and that's exactly what this audit gives you.
Figure 2. A recommendation becomes useful when its effect can be checked.
Frequently asked questions
What data belongs in an engineering productivity audit?
Combine delivery records, CI results and incident information with developer feedback and observed work. Each source answers different questions. Investigate an explanation across sources before treating a dashboard signal as the cause of a delay.
Why use surveys alongside delivery data?
System data can show waiting or failure patterns while a survey can reveal missing access, unreliable environments and unclear expectations. Use questions that the team can answer consistently, and compare responses with workflow evidence.
How should I compare audit recommendations?
Use a common period and clear denominators when estimating time lost and recoverable capacity. Separate recurring weekly waits from occasional onboarding work. State implementation and maintenance effort before comparing the proposed returns.
What should happen after an audit?
Give each chosen improvement an owner and a measure of the expected change. Review the result after implementation, and investigate cases where the measure fails to move. The post proposes a recurring cadence for keeping the work visible.
Most code quality dashboards fail because they track too many metrics and live outside the team's workflow. Here are exactly 7 metrics and a 3-week adoption plan that actually works.
A 3-tier succession planning framework for engineering orgs, with a 90-day sprint for accelerating candidates from potential to ready. Based on succession plans built at 4 companies.
The CTO's real job in product development isn't attending every meeting or making every technical call. It's connecting feasibility, viability, and capacity while letting EMs handle the day-to-day.
Four years of data from a fully remote engineering team across 4 time zones. Specific metrics on productivity, retention, and onboarding with the frameworks that actually worked.
Small frictions cost more than big blockers. 47 micro-frictions consume 96 minutes per engineer per day. Here's the TAX Return framework for finding and eliminating the developer productivity tax.
Compare cyclomatic and cognitive code complexity with change risk. Check corrected examples, understand each measure’s limits and target refactoring effort.