That just migrating users by building or department was a mistake. What we ran into every time was "Oh can you also migrate john from accounting today? It’s kind of an emergency he's working with IT on a big project and he needs to collaborate with them. He just called to say he can’t see anyone’s calendar in IT"

 

So trying to keep this from happening led us to develop a methodology (Collaboration Mapping™) that eventually turned into a tool we call, "Collaboration Mapper™". No doubt a mouthful to say, but a very cool way to understand your organizations internal collaboration. A "map" of who works with who. At first this was a great way to migrate systems and end-users because it virtually eliminated the problems of co-existence when migrating. Groups and individuals moved with those they worked with. But soon we realized, or I should say our customers realized, that this was a tool for understanding their organization in a deeper way. How often do you create org charts and use those to put departments together in a building? Truthfully your just guessing. This tool tells you who is working together in no uncertain terms