A naukri.com initiative
The Beautiful Mess
3M
287
Image Credit: The Beautiful Mess
TBM 304: Losing a Day a Week to Inefficiencies?
- According to a recent Atlassian and DX study, developers lose at least one full day per week due to inefficiencies, and 2 out of 3 developers are still losing 8+ hours a week to inefficiencies in their roles.
- For the roofers and performers, the waste is extremely tangible. In knowledge work, we typically pivot to another task and take a less tangible context-switching hit. Workarounds and task switching become habitual.
- As scary as it sounds, losing a day of a week might be a blip in the grand scheme of things. Getting eight more hours of "quality work" might not make any difference whatsoever.
- The real question is how much revenue those developers could generate with 4,000 hours. I guess that with a sufficiently informed strategy and customer insights, it would be more than $6.9 million.
- Most teams address local issues within their immediate influence. When it comes to anything more global, they typically face a lot of pushback and second-guessing.
- The path forward requires a deep cultural shift in many companies—not just running retros, incrementally better measurement, and better voice of developer efforts, etc.
- The problem (and opportunity) has been out in the open for a long time—it is the talking about it that has been hard.
- These days, people in companies wants to be "efficient" and wants developers to be "productive", but few are willing to make the sacrifices required to achieve operational excellence and foster a culture of continuous improvement.
- Estimates of time losses are important. However, for companies to truly address the challenge, they must figure out how to remove the layers of fear, blame, and apathy.
- The study recommends 'Feedback loops that allow for continuous improvement through learning and adjustments.'
Read Full Article
14 Likes
For uninterrupted reading, download the app