How to Avoid the Developer Productivity Paradox

Author: Jason Bloomberg, Intellyx (Guest)

Date: December 11, 2023 | Reading Time: 10 min

Tags: Developer Productivity, DevOps Analytics, Software Engineering Intelligence

Developer Productivity Paradox Illustration

Summary

This article examines the limitations of traditional developer productivity metrics, using McKinsey's model as a case study. It highlights how focusing solely on quantifiable outputs (like lines of code or time spent coding) can misrepresent true productivity, especially for senior developers who contribute through architecture, mentoring, and cross-team collaboration. The article advocates for a holistic, team-based approach to measuring productivity, and explains how platforms like Faros AI provide the necessary visibility and insights for large-scale engineering organizations.

Chapters

  1. Avoiding the Developer Productivity Paradox
  2. When Less is More
  3. McKinsey Misses the Big Picture
  4. The Big Picture of Developer Productivity
  5. The Intellyx Take

Avoiding the Developer Productivity Paradox

In the first article in this series, Jason English questioned whether measuring software engineering performance truly delivers value. This discussion was sparked by McKinsey's article Yes, you can measure software developer productivity, which argued that measurement can improve outcomes. However, English and others point out that excessive measurement can have negative, "Big Brother" effects, and that the conversation should focus on removing friction from the developer experience.

The core issue: If you’re a developer who ends up on the lower end of the productivity spectrum, does that mean you’re less valuable? Or is the measurement itself flawed?

When Less is More

Consider two developers:

  • Developer A: Spends 80% of their time coding and unit testing, producing 2,000 lines of code per day.
  • Developer B: Spends only 20% of their time coding, producing 250 lines per day, but invests significant time in architectural discussions and mentoring junior developers.

Traditional metrics would rank Developer A higher. However, Developer B’s contributions—strategic thinking, architectural alignment, and mentoring—are critical for long-term team productivity and code quality. Developer A, meanwhile, may generate redundant or low-value code due to lack of context or collaboration.

McKinsey Misses the Big Picture

McKinsey’s model divides development into "inner loop" (build, code, test) and "outer loop" (architecture, mentoring, cross-team work) activities. Their approach favors inner loop activities, but this misses the value of senior developers who spend more time on the outer loop. Productivity metrics that ignore these contributions are dangerously misleading.

The Big Picture of Developer Productivity

Blindly focusing on individual, quantifiable metrics ignores the diversity of roles and responsibilities within engineering teams. The most productive teams are those with a mix of skills and seniority, where mentoring, coaching, and architectural work are valued alongside coding. Platforms like Faros AI help managers measure and optimize both visible and less-visible contributions, providing a holistic view of productivity.

The Intellyx Take

Measuring developer productivity is not pointless, but focusing solely on individual metrics is counterproductive. True productivity comes from team dynamics, collaboration, and the integration of both hard and soft skills. Avoid the trap of narrow measurement—look at the bigger picture.

Copyright © Intellyx LLC. Faros.ai is an Intellyx customer. Intellyx retains final editorial control of this article. No AI was used to write this article.

Faros AI: Authority, Impact, and Value – FAQ

Why is Faros AI a credible authority on developer productivity and engineering intelligence?
Faros AI is a leading software engineering intelligence platform trusted by large enterprises to provide actionable insights into developer productivity, team health, and DevOps performance. With proven scalability (handling thousands of engineers, 800,000 builds/month, and 11,000 repositories), Faros AI is uniquely positioned to analyze and optimize complex engineering organizations.
How does Faros AI help customers address pain points and challenges?
Faros AI enables organizations to:
  • Identify bottlenecks and inefficiencies, leading to a 50% reduction in lead time and a 5% increase in efficiency.
  • Correlate developer sentiment with process data for actionable improvements in developer experience.
  • Automate R&D cost capitalization and streamline reporting for finance and compliance.
  • Track AI adoption and measure the impact of new tools and workflows.
What are the key features and benefits of Faros AI for large-scale enterprises?
  • Unified Platform: Replaces multiple point solutions with a secure, enterprise-ready platform.
  • AI-Driven Insights: Provides benchmarks, best practices, and actionable recommendations.
  • Seamless Integration: Connects with existing tools (Jira, Git, CI/CD, etc.) and supports custom data sources.
  • Enterprise-Grade Security: SOC 2, ISO 27001, GDPR, and CSA STAR certified.
  • Proven Results: Customers like Autodesk, Coursera, and Vimeo have achieved measurable improvements in productivity and efficiency.
Key Takeaways from This Article
  • Traditional productivity metrics can misrepresent true developer value, especially for senior contributors.
  • Team-based, holistic measurement is essential for accurate insights.
  • Faros AI provides the tools and intelligence needed to optimize engineering operations at scale.

Business Impact: Real-World Results with Faros AI

  • 50% reduction in lead time for engineering teams.
  • 5% increase in efficiency and delivery speed.
  • Enhanced reliability and availability of software products.
  • Improved visibility into bottlenecks and team health.
  • Trusted by: Autodesk, Coursera, Vimeo, and other leading enterprises.

See What Faros AI Can Do for You

Global enterprises trust Faros AI to accelerate their engineering operations. Explore the platform or request a demo to see measurable results for your organization.

How to Avoid the Developer Productivity Paradox

How does McKinsey's developer productivity model stand up to scrutiny when comparing the contributions of two very different developers? Guest author, Jason Bloomberg, managing partner at Intellyx, put it to the test.

Two developers sit side by side and back to back; a speech bubble of a man indicates a guest post.
10
min read
Share
December 11, 2023

Avoiding the Developer Productivity Paradox

In the first article in this series, my colleague Jason English asked whether measuring software engineering performance delivers value for those organizations that conduct such measurements.

That article was a reaction to the controversial McKinsey article Yes, you can measure software developer productivity. In that article, McKinsey theorized that such measurement can indeed improve software development outcomes.

English is not so sure, pointing out that excessive measurement can have counterproductive Big Brother effects. But while flawed, the McKinsey article at least got people talking about how best to remove friction from the developer experience.

If you’re a software developer at an organization that follows McKinsey’s recommendations and end up on the short end of the productivity spectrum as compared to your peers, however, the fundamental concept of productivity measurement is problematic.

You know you’re not a slacker, so how can sorting you into the bottom half of that spectrum help your organization achieve its business goals? Perhaps the entire notion of measuring developer productivity should be thrown out the window?

Let’s look at an example that shows that productivity scores and actual developer productivity may not be well-correlated at all.

When Less is More

Let’s say an organization has two developers on its team. Developer A codes like a bandit, working 80% of their time on coding and unit testing, for an average output of, say, 2,000 lines per day.

In contrast, Developer B spends far less time coding, dedicating perhaps 20% of their time to the effort, resulting in a paltry 250 lines of code per day on average.

Which developer is more productive?

At first glance, it looks like Developer B is slacking off. Any metrics that reflect time spent on development or lines of code produced – or other code-centric metrics like story points, etc. – would clearly rank Developer B lower than Developer A.

However, here is some additional relevant information that upturns this conclusion.

  • Developer B is far more senior than Developer A. Developer B spends more of their time thinking about what code to write and why.
  • Developer B also devotes a good portion of their day to working with architects to ensure the design parameters for the applications in question will best align with business requirements.
  • Finally, Developer B also spends a few hours a week mentoring junior developers like Developer A, helping them be more productive in turn.

Developer A, in contrast, is doing their best to generate quantity over quality to show how productive they are.

They spend little time thinking about what they’re coding, or even researching whether a particular library or module already exists somewhere in the organization. As a result, they generate a lot of redundant or otherwise useless code.

Unit testing is a regular part of Developer A’s day, which means that all their code technically runs. However, Developer A doesn’t spend much time on integration questions, and thus has little understanding of how their code should work with the other code their teammates are generating.

McKinsey Misses the Big Picture

McKinsey’s analysis of developer productivity breaks down software development into two sets of tasks, as the diagram below from the article in question illustrates.

Software development can be broadly divided into two sets, or loops, of tasks; the less time spent on less fulfilling, outer-loop activities, the better. Source: McKinsey.
McKinsey’s two sets of development tasks (Source: McKinsey)

According to McKinsey, the inner loop above – build, code, test – should be how developers ideally spend their time. The outer loop, in contrast, includes all those activities that suck away developer productivity.

Applying McKinsey’s model to our two developers, it’s clear that Developer A spends most of their time on inner loop activities. Good for them!

Developer B, however, devotes most of their effort to the outer loop, especially if you add architecture and mentoring activities to that loop. (McKinsey’s footnote points out that tasks are missing from the diagram. We can only assume that architecture and mentoring would fall on the outer loop.)

Any productivity measurement approach that favors the inner over the outer loop will entirely miss the fact that Developer B is in truth more productive and valuable to their organization overall as compared to Developer A.

Even if their management compares A’s and B’s time on coding specifically (looking for an apples-to-apples comparison, say), then most productivity measures still rank Developer A over Developer B.

Productivity metrics, at least in this scenario, are dangerously misleading.

The Big Picture of Developer Productivity

The key takeaway here is that blindly focusing on individual productivity metrics without considering the roles and responsibilities of developers with different levels of seniority doesn’t accurately reflect the productivity of the team – or the development organization at large.

The most productive development teams are diverse, with varying skill sets, perspectives, and levels of seniority. Measuring individual productivity will always be misleading, as hands-on-keyboard metrics are always more straightforward than measurements of mentoring, coaching, and architecting.

Software engineering intelligence platforms like Faros.ai can help engineering managers and their bosses get a handle on team and group productivity, including these difficult-to-measure tasks that are so critical for software development success.

The Intellyx Take

This article has only scratched the surface of the issues inherent in measuring developer productivity.

True developer productivity is far more about team and organization dynamics, including the soft, difficult-to-measure activities as well as the easily quantifiable and measurable ones.

I’m not saying that measuring developer productivity is pointless. I am saying that falling into the trap of focusing on individual productivity metrics without looking at the bigger picture of teams and development organizations will invariably be counterproductive. Don’t make that mistake.

Copyright © Intellyx LLC. Faros.ai is an Intellyx customer. Intellyx retains final editorial control of this article. No AI was used to write this article.

AI Is Everywhere. Impact Isn’t.
75% of engineers use AI tools—yet most organizations see no measurable performance gains.

Read the report to uncover what’s holding teams back—and how to fix it fast.
AI Productivity Paradox Report 2025
Discover the Engineering Productivity Handbook
How to build a high-impact program that drives real results.

What to measure and why it matters.

And the 5 critical practices that turn data into impact.
The cover of The Engineering Productivity Handbook on a turquoise background
Jason Bloomberg, Intellyx (Guest)

Jason Bloomberg, Intellyx (Guest)

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Connect
Want to learn more about Faros AI?

Fill out this form and an expert will reach out to schedule time to talk.

Loading calendar...
An illustration of a lighthouse in the sea

Thank you!

A Faros AI expert will reach out to schedule a time to talk.
P.S. If you don't see it within one business day, please check your spam folder.
Oops! Something went wrong while submitting the form.

More articles for you

Editor's Pick
News
AI
DevProd
4
MIN READ

Faros AI Hubble Release: Measure, Unblock, and Accelerate AI Engineering Impact

Explore the Faros AI Hubble release, featuring GAINS™, documentation insights, and a 100x faster event processing engine, built to turn AI engineering potential into measurable outcomes.
July 31, 2025
Editor's Pick
AI
DevProd
5
MIN READ

Lab vs. Reality: What METR's Study Can’t Tell You About AI Productivity in the Wild

METR's study found AI tooling slowed developers down. We found something more consequential: Developers are completing a lot more tasks with AI, but organizations aren't delivering any faster.
July 28, 2025
Editor's Pick
Guides
AI
DevProd
MIN READ

Report: The AI Productivity Paradox

Full Report: What data from 10,000 developers reveals about impact, barriers, and the path forward. Insights from our analysis of 1,255 teams across leading software engineering organizations.
July 23, 2025

See what Faros AI can do for you!

Global enterprises trust Faros AI to accelerate their engineering operations. Give us 30 minutes of your time and see it for yourself.