The name of an initiative is an oft-overlooked aspect of communications. You’ll get a decent name if you work with an experienced OCM crew. However, the most effective names I’ve seen weren’t focus-group tested so to speak. Here they are:
- Everest: Used for a SAP project that was challenging with a tight time line; however, the customer expected good returns from the initiative. This name conveyed these attributes well: Everest is dangerous, has a short climbing window, and signifies the ultimate achievement.
- OASIS: This was an acronym used to describe a SAP upgrade for a customer that had had a troubled initial implementation. The name conveyed danger and privation. More importantly, it reflected the key goal of the project: to provide a stable and modern ERP platform (the customer had waited years to upgrade).
Finally, I have a soft spot in my heart for Project BOHICA, a name we used on a project simulation team. I’ve always wanted to use that one “for real”.
Any other best or worst names?
Filed under: Paul Ritchie, PMO | Tagged: Communications, Organizational Change Management, project names |
[…] get a decent name if you work with an experienced OCM crew. Paul Ritchie in his post writes about good and bad projects names and how them effect on the project […]
[…] My post on best and worst project names remains one of my most popular. As a follow up, here’s a few more good and not-so-good names: […]
[…] posts on Best and Worst Project Names here and […]