[australia] Why home grown CMS?

[Paul Took]

this is an opportunity for us all as vendors/managers to lead.

our most important role is as cultural change managers. we're the  
ones who do this stuff every day, not our 'clients'.

where a client doesn't value their information, the vendor/manager  
needs to step in and provide a plan that is going to give the client  
a structured approach, ensure client staff enthusiasm is maintained  
and lead them down the path to success.

easier said than done, I know, but it's all about seizing the  
opportunity!

paul





On 11/10/2006, at 10:02 AM, Melanie Kendell wrote:

On 10/10/06, Frank Warwick <frank.warwick at sitemaster.com.au> wrote:
> All this comes down to bad planing and miss management
> of staff and not getting involved because 'thats not what I do'  
> attatude

I think this largely comes back to the fact that organisations do not
value their information or the means of disseminating that
information.

Most CMS "projects" are not fully sanctioned projects at all. At
first, generally only one aspect of information management is
identified which is too small to justify proper funding, and then the
next issue comes up - so we get the piecemeal introduction of bits of
the jigsaw.

For example, they may start out just implementing some sort of version
control, then someone gets concerned about access control, then
someone says it would be nice to have workflow, etc...

Once someone has tacked all these pieces together you have a homegrown
CMS - it works well enough, and the organisation hasn't had to change
its lack of interest in its information - so it just carries on.

-Melanie
_______________________________________________
australia mailing list
australia at lists.cmprofessionals.org
http://lists.cmsml.org/mailman/listinfo/australia