I was the first house in the new subdivision, so I was given the keys for mailbox #1. Only after other homes had been built did the Post Office consider that I was the second house on the block. Consequently, we had to switch keys and labeling so I could have box #2, allowing the mail to be kept in the order of house number instead of when they were first occupied.
In a similar vein, while working on campus, we planned to build five new student apartment buildings. We assigned them names of trees, and planned to label them in alphabetical order. What would end up being the third building in the row was built first, and we had to insist that it be named Cedar (instead of Aspen) so they would be in alphabetical order when the complex was finished.
And another example: when we renamed the generic Conference Rooms A, B, and C, we intentionally identified the smallest as the Dubuque Room, the mid-size one as the Iowa Room (bigger than Dubuque), and the largest as the Mississippi Room (bigger than Iowa). This naming convention allowed people to easily associate the name with size and reserve the proper facility.
Your naming conventions can serve a purpose beyond simply giving something a label. Put some forethought into what you call things and how those names can facilitate memory or efficiency as they are used in the future.
