How little bits of information are costing Intel a billion dollars a year

Intel recently had their analysis of Infomania (“the mental state of continuous stress and distraction caused by the combination of queued messaging overload and incessant interruptions”) published at The paper, Infomania: Why we can’t afford to ignore it any longer, is aptly titled; it shows that Intel stands to save almost a billion dollars annually by overcoming the inefficiencies due to information overload: 

The bottom line: Infomania causes a damage of about US$1 billion per annum for a knowledge–intensive company of 50,000 employees. As usual with such calculations, this value is conservative, representing only more direct aspects of the problem. Additional, harder to measure damages exist but are not included.”

The paper hints that the calculation above, based almost solely on measurable employee efficiency losses, may only be the tip of the iceberg. The group also found that information overload had a very tangible, negative impact on intellectual property generation, work quality and employee satisfaction. For example: 

“It is critical to understand this huge impact: because of Infomania, employees are not creating new ideas to the extent they could. New, significant inventions remain un–invented. Better solutions to major problems that may be hobbling an organization’s performance toward its goals are left undiscovered. The engineer who could have the “Aha!” insight leading to the next major product innovation is trying to find 30 minutes to think about it, and failing. The supervisor who could double a fabrication line’s efficiency can’t because they are nearly brain dead from staying up until one AM working on e–mail. Across the industry, knowledge workers and managers are thinking less, inventing less, producing less, succeeding less.”

If you think that your organization suffers from these same issues, please forward this paper to a technology buyer at your company and let them know how IMS Pro has helped you get on top of email and become more efficient. Send them my email address (brad at clearcontext dot com) and let them know that we would be happy to help them understand the scope of this issue and the solutions out there to help combat it. Thanks! 

A final note – I found this via the IT@Intel blog. If you’re interested in the solutions they are implementing to solve the problem outlined in this paper, see