Hands-up, which of you has named their project based on the technology being implemented? That simple act may have just sealed the failure of the project.
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.
____________________
Related articles:
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
Martin Davis' Blog 
Hi Martin,
I didn’t notice this before, you are quite right! When a project is named after a technology (for example, the XML desktop reader), then the business people will no longer feel that they own the project, and slowly, but surely, their support to the project diminishes…
I would like to republish your series on project management on PM Hut, please either email me or contact me through the contact us form on the PM Hut website in case you’re OK with this…
LikeLike
Posted by PM Hut | April 18, 2012, 8:18 amReblogged this on Martin Davis' Blog.
LikeLike
Posted by Martin | July 22, 2016, 12:01 pm