Commentary

Jonathan Feldman
 

Meet Your New Enterprise App, Information Intake Management

Some enterprise teams that I work with, when confronted with the question, "what do we do with this new social networking thingy" immediately shoot back, "we're getting killed with emails -- we can't deal with the information we have." It's not that new social information isn't useful. It's that when you're already drinking martinis from a firehose, somebody offering you a cosmo is ironically tragic.

Some enterprise teams that I work with, when confronted with the question, "what do we do with this new social networking thingy" immediately shoot back, "we're getting killed with emails -- we can't deal with the information we have." It's not that new social information isn't useful. It's that when you're already drinking martinis from a firehose, somebody offering you a cosmo is ironically tragic.Paul Hemp at Harvard Business Review goes a step further this month, citing that individuals, as well as organizations, pay a high price for unmanaged information overload, with one researcher citing a $1B productivity problem.

Hemp mentions some solutions to the problem like filtering, and his practical list of "10 Ways To Reduce Email Overload" is not to be missed. You should, er, immediately email all your colleagues about it. SEND THIS TO EVERYONE YOU KNOW OR SOMETHING BAD WILL HAPPEN. Ok, maybe post it in the break room.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

He also offers Zen-like advice from expert Jerry Michalski: "You have to let go of the need to know everything completely... Trust your community to filter and flow the right things to you when you need them."

But an enterprise problem is rarely solved by individual applications of technology and techniques. It may be time for your organization to consider that combating information overload is, as Hemp suggests, an organizational problem. In the same ways that CRM or ERP are enterprise applications, maybe "information intake management" is an enterprise application as well.

Now, I'm not suggesting that applications to filter information aren't available. What I'm suggesting is that they're not perfect, that results vary greatly with the approach to use, and that a systematic approach may be needed for the organization to successfully protect its individuals from the type of burnout that information overload can create (Hemp's article suggests that it may be more profound that marijuana use. Stick that in your pipe and smoke it).

Successful enterprise applications are about more than IT providing technology solutions. They require a concerted effort between business unit managers, IT, and employees; and they require significant change management to ensure that individuals adopt new ways of doing things.

And that is perhaps most irritating part about new media, smart phones, and "always on" employee issues: they are outside the direct span of control of the organization. Managers might wonder if they can do anything about that 15% of employees who are checking their email in church.

But organizations have tackled work-life balance issues for years. Indeed, they've invaded our personal lives about tobacco cessation and other wellness issues. For managers to think that information overload is an issue outside their purview is a cop-out. IT can be part of the solution by treating the portfolio of practices and software that surround information intake management as something of an enterprise application.

Jonathan Feldman is an InformationWeek Analytics contributor who works with IT governance in North Carolina. Comment here, or contribute to his information overload at jf@feldman.org or _jfeldman on Twitter.

Read more about IT governance at governance.informationweek.com


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links