Provide Regular Time to Focus

向右看齐 2022-08-09 06:15 120阅读 0赞

## Provide Regular Time to Focus ##

James Leigh  
Toronto, Ontario, Canada  
SoFTWARE DEvEloPERS REgUlARly REPoRT that interruptions such as meetings, demos, and urgent bug fixes keep them from completing their work. Typically, a person takes about 20 minutes to regain his train of thought after one of these interruptions. A 5-minute question actually costs 25 minutes, and a quick 10-minute meeting actually costs 30 minutes of potential work. Inter- ruptions and recovery time consume 28% of a typical knowledge worker’s day and can cause undue frustration and stress.  
To help address this issue, set aside two hours a day (for example, between 10:00 a.m. and noon) that are interruption free. Alternately, you may be able to plan an entire day when no meetings, questions, email, phones, and other distractions are permitted, to allow developers to concentrate and focus on their work. Intel and IBM set aside Fridays, calling them “zero-email Fridays” and “Think Fridays,” respectively.  
It is equally important that developers know what their top two priorities are so they can plan their work for this period effectively. Even the best-intentioned developers could only randomly guess at what these are if they’re not explicitly told what will bring real business value to the project.  
Infomania (a debilitating state of information overload) is widely recognized as a major opponent to a developer’s productivity. Programming requires that developers keep many things in their heads at once—everything from variables, class structures, APIs (application programming interfaces), utility methods, and even directory hierarchies. When a developer is interrupted,  
  
much of this information is “swapped out,” and it requires considerable mental energy to regain it. This has a huge impact on productivity, and studies find that employees are not creating new ideas to the extent they used to because of infomania.  
In addition, different types of distractions have varying degrees of impact on the developer’s train of thought. One might be able to get up, use the restroom, get a cup of coffee and a sandwich, or even move to a whiteboard, while keep- ing all of the program data still actively circulating in the brain. In fact, the movement might help him/her see a new avenue to solve a problem.  
Planned meetings are especially problematic for programmers, as they might waste time when they know there is an upcoming item on their schedule. They think, “why get started only to be interrupted in 30 minutes?” And great ideas that come during meetings may be lost, or stale, by the time the developer gets back to his computer to capture them.  
Developers’ productivity can also degrade by over 50% for each additional simultaneous project. Developers working on three or more projects often spend more time attending meetings to explain why they are not making any progress than getting any actual work done. When developers must contribute to multiple projects, make sure that they are guaranteed at least two full days on each project before switching to another. This will minimize the amount of time they must spend reintroducing themselves to each project.