Commentary

George Dearing
 

Content Management Blunders From Down Under

The hits keep coming in from our "Top 5 Reasons A Content Management Company Will Go Out Of Business" post. This time, the experiences come from a university from the land down under, proving content management blunders serve us all on a truly global scale.

The hits keep coming in from our "Top 5 Reasons A Content Management Company Will Go Out Of Business" post. This time, the experiences come from a university from the land down under, proving content management blunders serve us all on a truly global scale.And just for the record, we're painfully aware that most of the reasons apply to any technology company, certainly one that builds software.

No. 1 -- You fail to thoroughly test your new releases, then delete any problem posts from your tech forum.


More Business Intelligence Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

No. 2 -- There's not enough interaction between front-line technical staff and the engineers, so a problem goes for 3 months of "we haven't changed that" and then ends with a message from engineers with "oh, yes, we did."

No. 3 -- Your documentation hasn't been properly reviewed for a new release, so it contains suggestions that haven't worked for two major releases

No. 4 -- You have 'modular' products where you don't have to include all the pieces, but things are a bit strange if you don't. They're also problematic if you do, because you have to provide for customers that haven't bought them all.

No. 5 -- 'Upgrading' turns a functional testing machine into a nonfunctioning lump of silicon that needs to have its OS reinstalled because it is so far beyond being repaired.

Nos. 1 and 4 are my favorites. The fourth one, describing the modular product pitch, really hit home. The challenge with "marketing modular" is the modules become moving targets, updated in collateral and client pitches as frequently as new functionality can be dreamed up by management. Do everyone a favor and first make sure you have the architecture in place to support your wild-eyed quest for more market share.

OK, I'm done.


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