by Craig Roth | May 25, 2010 | Comments Off on Please Stop Blaming Everything on Information Overload
Has “overload” become the latest meme? The “information overload” label can be slapped on anything related to too little time or too much to sort through. That’s a huge swath of problems and the term contributes neither explanatory power nor solutions. There’s a word for terms that are deeply layered with other meanings: “overloaded”.
A co-worker passed along an article about Google’s App store that manages to twist even that unrelated event into an overload solution. Writes Thomas Claburn in the InformationWeek Google blog:
Expect to see more App Stores because aggregation is a necessary defense against information overload.
Couldn’t he come up with a more spurious meta-reason for launching an app store? Maybe the airing of the last episode of Lost has left people with more free time that needs to be filled with Android apps?
I try to assist organizations address attention management, and “information overload” abuse does not help. When it goes beyond awareness of an issue into easily debunked flag waving then reflexive eye-rolling kicks in and it becomes an uphill battle to reach jaded executives.
I’ve only addressed information overload here, but the “overload” label is also appended to data overload, traffic overload (=traffic), brain overload, fun overload, etc. I’ve had enough. Besides, my toddler is whining about something in the other room and I have to go. I suspect pants overload …
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.