The success of many implementations lies in the ability to flexibly adapt the plan with the many challenges and changes we face every day. A successful Implementation cannot be undertaken without at least some planning to ensure that all involved understand  what is it that we are doing (Scope), why we are doing it(Requirements), how we are going to get it done(Resource Planning), how it will fit(systems Integrations & customisation), what will users do with it(User Policies, Access, Training & Change Management), that it will actually work(Testing) and how to put it all together without disruption to the business(Delivery). Many people ignore the basic principles of project management because of an association with either cost or time, but the simple fact is that even a project that lasts one day, when not project managed correctly, can easily escalate to a week.

Even if an implementation is just the installation of some seemingly benign software onto your production system, there is still a large amount of work to be done, usually much more than the shelf value of the software itself. It is not about that piece of software, it is about what it can do to your existing systems and functionality. Hoping for the best or doing something just because a competitor is might not be the best IT policy.  Leaving it in the wrong hands can have dire consequences, not only affecting one but possibly all of your production systems.

All of this applies to implementing a content management system but more so as usually a company's most important information is stored in unstructured data, which are in turn stored inside a content repository. It is said that information is the lifeblood of a business, and of that there is no doubt, but the key of course is presenting this information to your knowledge workers in a manner they can understand, and also use. This means as much implementing the solution correctly, as it does implementing the right solutions.