Keith -
Here's an article I'd written a few years ago on this subject:
"Juliet might have said “That which we call a rose by any other name would smell as sweet” but I beg to differ when we are coming up with project names.
Here are a few of the ways in which good project names can make a difference:
– Motivating and unifying a cross-functional project team that hasn’t worked together in the past and is not 100% dedicated to your project. Ensuring that your project name is uplifting and somehow captures the essence of what benefits the organization and the team members will reap can help focus team efforts.
– Engaging stakeholders and sponsors. It might be easy as a stakeholder to ignore pleas from the project manager of the “implement ABC system version 1.2” but you’d think twice of doing this if the name was “reduce patient mortality due to transcription errors”…
– Supporting that “outside in”, business-focused view of projects – this is especially true for technology projects. IT is forever blamed as being disconnected from the business and purely technology-focused and picking technology-centric project names does not help your CIO foster credibility with his or her peers at the executive level.
So what are the hallmarks of a good project name? Here are a few suggestions:
1. It should reflect the expected benefits or business outcomes of the project.
2. It should be short – short enough that you could give the project name & a brief description in the stereotypical 30 second elevator pitch.
3. It should be positive (e.g. reduce operating costs is not as positive as increase profitability)
The acid test is to visualize yourself at a conference presenting a case study about the success of your project upon its completion – would you be proud to state its name, or would you cringe and mutter it under your breath?"
