Naming Distributed Teams

I try to remind everyone as often as possible that the most complex part of solving problems is people.  So many little things impact people every day.

Today I came across this tip from Johanna Rothman for distributed teams:

Call the teams by their feature names, not by their geographic location. It’s too easy to call the teams by "Headquarters" or "Cincinnati" or "Paris" or "Bangalore", and any name other than "Headquarters" implies a hierarchy among the teams.

Recognizing and breaking these subtle habits is hard, but the sign of an organization more concerned with results and teamwork than title and seniority.

image

Are these teams distributed or co-located?  Each has the skills needed to deliver a feature for our project/product that meets the definition of done.  Does this scale more or less than resource pools?