Four Lenses of Productivity: From Individuals to the Market
Zooming In: How Productivity Shapes Success at Every Level
In the previous article about developer productivity, we saw how measuring productivity has been a quest akin to finding the Holy Grail in the world of software companies.
We've seen it all: Lines of Code (LoCs), commit frequency, and the infamous ticket-closing rate. And what did we learn? "You get what you measure!" – sometimes, quite literally.
Before we dive into how to measure productivity, let's first understand what it means. This article explores productivity through four distinct lenses, catering to everyone from solo software developers to entire organizations.
Individual Productivity:
Understanding Individual Productivity
When we think of productivity, we often picture a lone 10X developer – the individual – conquering tasks. But being busy isn't the same as being productive. True productivity is about crossing the finish line, not just running the race.
Take a developer, for example. They may be coding up a storm, but if that code never makes it to the codebase, it's like Thanksgiving dinner with nobody to eat it.
What Impacts Individual Productivity
A recent paper on Developer Productivity1 talks about individual productivity in detail. Here is the very high-level highlight.
Achieving the Flow State: It's about creating a distraction-free zone where productivity can bloom.
Feedback Loops: Quick feedback is like GPS for productivity – it helps you stay on course and fine-tune.
Cognitive load: Amount of mental processing a developer would need to understand or work on a task.
Team Productivity:
Understanding Team Productivity
Beyond the individual lies the team's productivity. It's the collective effort to push the boulder up the hill, like releasing a feature or software update.
Imagine a team of five developers coding like there's no tomorrow. But if there's a bottleneck in code reviews, it's like having an F1 car stuck at a pitstop – you're not getting anywhere fast.
What Impacts Team Productivity
Cross-Functional Teams: Teams that handle everything from A to Z tend to skip the relay race and passing of the baton. They collaborate until they get to the finish line together!
Reducing Work in Progress (WIP): Sometimes, reducing the work in hand increases the overall speed. Think of traffic lights, how some cars may have to stop or slow down to avoid jams and maintain a healthy flow of cars
Knowledge Sharing and Collaboration: In a team, team members can get stuck where they require specialized knowledge. Collaboration and knowledge sharing can help such work items get “unstuck.”
Organizational Productivity:
Understanding Organizational Productivity
Zooming out, we see the big picture: organizational productivity. It's about fine-tuning the entire machine, from development pipelines to seamless deployment, to ensure your lead time to change remains low or improves over time.
What Impacts Organizational Productivity
Automation: Most development items spend time sitting in some queue waiting for attention from human beings. Automate most of it. It's like having a productivity robot that does the boring stuff for you.
Software Development Practices: Practices like trunk-based development ensure everything is always dressed for the production party.
Software Architecture: Modular monoliths or breaking down monoliths into microservices may help. Any architecture that decouples multiple teams’ release schedules works the best here.
Reduced Gatekeeping: Traditional companies often react to fear of failure by adding more gates. It's like putting more locks on a door that's already jammed.
Market Productivity:
Understanding Market Productivity
Finally, there's market productivity – the impact of your products or services on the grand stage of the market.
What Impacts Market Productivity
Innovation: It's about creating things that make the market go, "Wow, why didn't I think of that?" Or something game changing like the recent tools based on LLMs, we see the entire markets changing because of revolutionary innovations like those.
The rise of tools like ChatGPT and LLMs has revolutionized content creation, prompting giants like Microsoft Word and Google Docs to jump on the co-pilot bandwagon.
Conclusion
From personal strategies to market-focused innovation, enhancing productivity is a multifaceted journey. It's about making an impact, not just staying busy. Remember, activity doesn't always equal productivity – it's like using an escalator that goes down when you want to go up!
So, whether you're a manager or an individual contributor, focus on impact. After all, in the world of productivity, it's the results that sing the loudest.
The last article in the series is going to be about what productivity looks like in the real world.
Before I publish the next blog on the case studies, help me answer this question.
Subscribe to stay updated about it.
Noda, A., Storey, M.-A., & Forsgren, N. (2023). DevEx: What Actually Drives Productivity: The developer-centric approach to measuring and improving productivity. Queue, 21(2). https://doi.org/10.1145/359587
Love your take on this! Was a really good read.