…we’re the People’s Front of Judea!
How many times has your organization made minor or major organization changes that made the naming of teams or departments less than 100% aligned with their job descriptions? Obviously, the confusion generated by such inconsistencies cannot be allowed.
More importantly, generic department names such as “information technology” won’t because such terms are neither cool nor do they offer enough variety to give every mid-level manager a team with a different name. Worse still, what would happen if the CIO was also in charge of the sales department? Clearly, “information technology” would not be a broad enough term for the department, and you’d have to name your department for some job that loosely resembles your function… You’d become the “Barrista Department”.
Inevitably, no name fits the mission completely, and no mission fits the need completely. Therefore, management and teams must change, and names along with them.
A lovely side effect of this is that the “old” names tend to still be used for some time after the fact. Maybe you gave your team fancy logo wear to pump them up for the last name change. Maybe you prefixed all of your documents with an abbreviation of the department name. Maybe you had 2 million glossy business cards printed up with the new department name and logo. Maybe you even had a special domain name with that department or division represented.
Well, forget them. They’re all useless. Any use of the old names is likely to produce confusion. Using the old names may also suggest that the old way was good enough, and we all know that reorganizations are perfect.
Burn those business cards, shirts, and servers with legacy names and logos on them. Otherwise, you may get a scolding for clinging to the “old ways”.
[If you don’t get the title reference, see the following YouTube clip (warning: language)