Re: More users = simpler CMS

At 07:14 PM 7/08/2005, Rickard Öberg wrote:

>The need for in-depth knowledge of the CMS that 
>the implementing customer team must have can be 
>radically reduced by utilizing the vendor 
>itself, or by asking how other similar customers 
>have approached similar problems. While many 
>tend to believe they are "unique" or "special", 
>that is rarely the case, at least not with 
>regard to the issues raised in this article.
>
>The CMS itself can also be created in a way that 
>explicitly deals with the issues outlined in the 
>article. I happen to be the architect of one, 
>hence my own bias and perspective :-)
>
>It is indeed important that users can start off 
>in an expedient and "simple" fashion, and then 
>leverage more and more as the experience and 
>needs increase. The single most devastating 
>error that can be done is to do an all-at-once 
>implementation that simply does not reach escape 
>velocity and hence comes tumbling back to earth 
>making a spectacular crash. There are endless 
>stories of traumas relating to such projects, 
>both on the CMS and "portal" side of things. But these can be avoided.

Hi Rickard,

I agree 100% with your points, so clearly my article didn't convey
the argument very well.

To therefore paraphrase:

If you have a lot of users, then you should get a CMS that is suited
to being used by large numbers of non-technical users.

The inherent usability/simplicity of the CMS should therefore be a
*key selection criteria* when choosing a CMS...

Cheers,
James


-------------------------
James Robertson
Step Two Designs Pty Ltd
Knowledge Management / Content Management / Intranets

http://www.steptwo.com.au/
[email protected]