I’m a sucker for a good code name. I watch my fair share of CIA-FBI-MI6 content and code names abound.

Sometimes it’s the characters and their call signs (Goose, Maverick). Sometimes it’s an operating procedure (Ghost protocol). Sometimes it’s a secret organization (Night Action) or network of evil villains (SPECTRE). Sometimes it’s the core mystery at the centre of the drama (Treadstone). If you understood all those references, we can probably be friends.

In real life you hear code names too. Some are infamous (Manhattan Project) some are aspirational (Apollo Program) some are playful nods (Apple OS updates are named after California landmarks). I bet your local police force has a code name for their campaign to reduce speeding and impaired driving during the holidays (Operation Fuzzy Bear).

I’m helping coach a client through a six-month project with their team. As we were creating the roadmap, we discussed using a code name for the project. Unlike the spy movies, this project is not top-secret. But there are a few advantages of going with a code name:

Separate the project from the operation. In this case, the work will redesign some standard operating procedures. The team will have to lift themselves out of their daily operational tasks to view the entire system.
Create a shared shorthand. We’re leveraging the team’s existing meeting schedule so using a code name signals when we’re switching to project-related discussions.
Build collective ownership. With a shared code name the team recognizes their role in co-creating the changes required.
Introduce a playful element. When you pick the right code name you can use it as a metaphor and make the work more playful. For example, “Project Road Trip” needs a road map and some milestones along the way. See? Easy.

Next time you’re running a project, bring everyone together and name the project. You won’t be sorry… and don’t worry, this message won’t self-destruct.

Inspiration

Every spy movie ever made.

In Praise of Code Names

Ship At 80%