Commentary
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
- How To Regain IT Control In An Increasingly Mobile World - by BlackBerry
- New Visual and Wizard-Driven Paradigms for Exploring Data and Developing Analytic Workflows
Reports
More >>Webcasts
- Maximize ROI with Database Consolidation onto Private Clouds
- The ABC's of Cloud Computing in the Midmarket
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
| 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: 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 RSSResource Links
This Week's Issue
Technology Whitepapers
- Mobile BI: Actionable Intelligence for the Agile Enterprise
- Creating the Enterprise-Class Tablet Environment - by Yankee Group
- The BlackBerry PlayBook tablet's Good Bones - by BlackBerry
- Red Alert: Why Tablet Security Matters - by BlackBerry
- New Visual and Wizard-Driven Paradigms for Exploring Data and Developing Analytic Workflows
Featured Broadcast
This white paper explains how to create a manageable, scalable environment suited to answer real-time business needs by building out a data center on a standards-based, virtualization-aware, energy-efficient and affordable platform. Plus, learn how virtualization is making the jump from the server realm into the application, mobile and database worlds in the additional resources section.
Learn More












