So now what?

Now that we’ve discussed in depth what doesn’t work, here are some things we find DO work:

• Content Management should be built around the workgroup. Pick a solution to meet the needs of the group who is managing and publishing. Content silos can be a good thing! Merging content into a single repository should be done only if there is a compelling business need to have the content types working together.

• Segmented repositories and small steps are the way to get these programs working. Simple implementations typically work best.

• Enterprises should explore making intranets into content visibility tools to enable efficient publishing for the workgroups who have valuable content to share, but don’t enable publishing for every employee.

• Common interfaces, where groups can share and collaborate on documents and other assets work very well.

• There is great value in sharing corporate brand assets and this function should be centralized. The larger the company, the more valuable this becomes. Simple, web-based asset repositories can enable the most commonly used brand assets to be kept up-to-date and available to everybody.

• IT groups should standardize on technical platforms - J2EE, ASP, .Net, Linux/PHP, etc. Attempting to standardize on a single product can cripple an organization for years. Different interfaces for different workgroups is a good thing.

• Trying to accomplish too much is one of the biggest hazards in the CM world. Keeping the project goals simple, and building upon smaller, measurable successes, works! Attempting to solve the enterprise problem at once is simply not realistic or practical.

• Content management systems are often selected on the basis of project requirements that are unnecessary. Solve the big issues. Concentrate on speed and ease of implementation and management. Do not let software vendors set your selection criteria.


Contact Onus today with your comments and questions,, or to hear about our DAM success stories... solutions@onusllc.com