Commentary

Chris Murphy
Editor, InformationWeek  

Content Management Problem? That May Be A Good Sign

Collaboration has such a lovely "let 1,000 flowers bloom" ring to it. IT teams know it means pulling a lot of weeds, too, but it sure beats the alternative.

Collaboration has such a lovely "let 1,000 flowers bloom" ring to it. IT teams know it means pulling a lot of weeds, too, but it sure beats the alternative.At Pfizer, it means tending the 6,000 Microsoft SharePoint sites used by 63,000 employees -- all of which have sprouted in just over a year. It's one of several examples in the current InformationWeek cover story that argues that the explosive growth of unstructured content requires a rethinking of enterprise content management strategies. The article describes how Pfizer's thinking about the challenge:

[Dave Biersach, associate director at Pfizer] takes the enterprise content management part of ECM seriously. Pfizer has about 1.5 TBs of SharePoint content in its SANs, and he expects to have about 6 TBs in two years. But he's determined not to let SharePoint become an information landfill. "If three years from now we see 15 TBs, that would indicate a loss of governance."

More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Having this problem should be a point of pride for IT teams. SharePoint is growing like kudzu in Georgia for a reason -- given the chance, people crave the collaboration and control SharePoint and other tools like it allow. IT teams need to answer that kind of demand.

Yes, it's creating a runaway bloom of unstructured content that IT teams need to figure out how to manage. Better that than a company where there's no place for this kind of collaboration to even take root.


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