Content Management Blunders From Down Under - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Software // Social
Commentary
4/30/2008
09:51 AM
George Dearing
George Dearing
Commentary
50%
50%

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.

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.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Commentary
Enterprise Guide to Edge Computing
Cathleen Gagne, Managing Editor, InformationWeek,  10/15/2019
News
Rethinking IT: Tech Investments that Drive Business Growth
Jessica Davis, Senior Editor, Enterprise Apps,  10/3/2019
Slideshows
IT Careers: 12 Job Skills in Demand for 2020
Cynthia Harvey, Freelance Journalist, InformationWeek,  10/1/2019
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Getting Started With Emerging Technologies
Looking to help your enterprise IT team ease the stress of putting new/emerging technologies such as AI, machine learning and IoT to work for their organizations? There are a few ways to get off on the right foot. In this report we share some expert advice on how to approach some of these seemingly daunting tech challenges.
Slideshows
Flash Poll