3 posts tagged with "focus-time"

Gloria Mark's research at UC Irvine found that it takes an average of 23 minutes and 15 seconds to refocus after a single interruption. Now consider a typical developer morning: 9:07 Slack pings, 9:15 standup reminder, 9:45 a "quick question" from a PM. By 10:30, they've been "working" for 90 minutes but written exactly 11 lines of code. Three interruptions consumed roughly 70 minutes of cognitive recovery time.

This isn't a productivity problem. It's a focus time problem. And the data shows it's costing your team far more than you think.

Your senior developer is assigned to three projects. You assume they're giving each project a third of their time. Gerald Weinberg calculated the real math in Quality Software Management (1992): with three concurrent projects, each project gets about 20% of a developer's time — and the remaining 40% evaporates into context switching overhead.

This isn't speculation. It's a well-documented cognitive phenomenon, confirmed by our platform data across B2B engineering teams and consistent with Gloria Mark's research at UC Irvine showing 23 minutes of recovery time per interruption. Context switching is one of the most expensive invisible costs in software engineering.

Crunch is the game industry's open secret. Despite decades of discussion, studio closures, and developer burnout, most studios still can't answer a basic question: is our team crunching right now?

They find out when people start quitting. By then, the damage is done — to the team, the project, and the studio's reputation. The IGDA Developer Satisfaction Survey consistently reports that ~50-60% of game developers experience crunch, with many working 50+ hour weeks during peak periods.

Engineering metrics make crunch visible before it becomes a crisis. Here's how.