Let me explain why……. by naming the project from the technology, it has just become an IT project (in the literal sense of the phrase) and therefore the responsibility of IT. The business teams involved now feel they can take a back seat and leave it to IT. Without the business taking ownership the project has just been doomed to failure.
Its amazing how important a small thing like the project name can be. My recommendation is to get the business to name the project and look for a catchy word or phrase that relates to the processes involved.
To find out more about change management and particularly how to be successful with IT related change see the related articles below.
Change Management (Part 1) – Cracking the Code of Change
Change Management (Part 2) – Step Models of Change
Change Management (Part 3a) – Change Capability
Change Management (Part 3b) – Success with IT Change