Commentary

Chris Murphy
Editor, InformationWeek  

Search, And Failure Of 'Consumer Effect'

We've written a lot about the consumer effect, how employees fall in love with consumer tech like iPhones and instant messaging, then demand the same experience at work. So why has this effect failed to drive enterprise search?

We've written a lot about the consumer effect, how employees fall in love with consumer tech like iPhones and instant messaging, then demand the same experience at work. So why has this effect failed to drive enterprise search?Our cover story this week asks "What's Wrong With Search?" Our research finds that less than 2% of respondents have enterprise search that combs multiple data silos in our companies. The article blames policies and privacy fears, not technology, which InformationWeek contributor Michael Healey says is up to the job. It also prices out a scenario of Google or Microsoft enterprise systems. Healey argues strongly for enterprise search improving productivity, especially as companies cut staff and ask employees to do more:

Getting search technology implemented--and used--is a great way to improve productivity. If your organization has endured layoffs, remaining staffers are as eager as they'll ever be to adopt search. Chances are, they've already felt the pain of looking for information that was in the head-or the e-mail store-of a colleague who was let go. Time to throw them a lifeline.

More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Why aren't employees screaming for this? Perhaps consumer versions of tools like desktop search aren't that great, so people can't picture how effective in-house search could help them. Let us know what you think.


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