« Creating & maintaining a web style guide | Main | IT and intranet ownership »

Why defining requirements is not good enough

Patrick Cormier has written a blog entry on the importance of having an integrated information management plan. To quote:

It is not good enough to adopt, as a starting point, "we need a content management system", or "we need a document and records management system". Other starting points are equally not valid: "we need a new records management policy", "we need a new training program". The optimum starting point should be: "we need a sound information architecture promoting integrated information management".

I definitely agree on the importance of not starting with just a single system, but instead taking a more global view of information needs in an organisation. I remain concerned, however, that the desire to create an integrated plan can lead to either over-simplification or "analysis paralysis"...

Posted by jamesr on May 31, 2006 11:24 AM
Categories: Information management