[australia] Why home grown CMS?

[Melanie Kendell]

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