Breaking the cycle of friction in developer workflows and workplace tech could dramatically boost software delivery, with recent insights pointing to strategic infrastructure and streamlined processes as key solutions.
Engineering productivity is too often treated as a personal failing when it is usually an organisational one. The real bottleneck is rarely talent; it is the accumulation of friction around that talent. A developer can be blocked by slow environments, broken pipelines, admin-heavy workflows and calendars packed with meetings long before a line of code is written. The result is familiar: delivery slows, roadmaps slip and product teams spend more time coordinating work than doing it.
That friction is not abstract. Logitech has said workplace technology problems are now disrupting meetings and draining productivity, with more than 70% of IT leaders reporting frequent issues such as poor audio and dropped connections. Its report also found that only 29% of organisations see workplace experience as a core business strategy, and only a third have a unified function for making those investment decisions. In practice, that means the systems meant to support collaboration often become another layer of delay. For engineering teams, the same pattern appears in local development environments, brittle build processes and tools that require constant human intervention.
The problem is amplified by interruptions. Stack Overflow has written about the importance of flow state in software development, arguing that even short disruptions can break the chain of working memory that engineers need to solve complex problems. Research cited by the publication suggests developers may be interrupted dozens of times a day, and other analysis says it can take around 15 to 25 minutes to regain concentration after a break. That makes the modern ritual of constant Slack messages, status meetings and “quick syncs” especially costly. A packed calendar may suit managers, but it is a poor fit for people who need long, uninterrupted blocks to build anything substantial.
Recent survey data also shows how expensive technical drag has become. According to Lokalise, US developers lose nearly 20 working days a year to inefficiencies, at an estimated cost of about $8,000 per developer. The survey blamed software bugs, service downtime, poor documentation and integration problems, while more than 60% of respondents said they were pulled into unofficial IT support tasks such as troubleshooting networks or configuring tools. Perhaps most strikingly, over 40% said AI tools had not helped and had sometimes made things worse. That suggests productivity gains will not come from adding more software unless the underlying workflow is simplified first.
The more durable answer is to remove avoidable friction. That means treating internal developer platforms, automation and reliable test and deployment systems as strategic infrastructure, not optional overhead. It also means designing for fewer hand-offs, better documentation and more self-service provisioning, so engineers spend less time waiting and more time building. The central lesson is straightforward: when organisations make it easier to ship, productivity improves. When they surround coding with bureaucracy, they should not be surprised when the roadmap stalls.
Disclaimer: This content is intended for informational purposes only. Readers are advised to exercise their own judgement, conduct due diligence, or consult a qualified expert before acting on any information provided.
