Introduction

A key tenet of Reimagining Collaboration is lifelong learning: As I write here, it’s essential to push yourself and pick up new tips and techniques. Sometimes this is simply a matter of playing with a new feature in an existing internal collaboration hub. Other times, however, it means learning a new hub altogether.

Case in point: I’m doing a bit of promotional work for Zoom For Dummies with the folks at Wiley.¹ Sure, the marketing peeps and I could bounce a bunch of email back and forth. Anyone who spends more than four minutes with me in a professional setting, though, knows that that’s not how I roll. On projects, all communication and collaboration should take place inside the hub. #PracticeWhatIPreach

Bifurcating communications into multiple apps, hubs, or formats is a recipe for disaster.

Period.

At the same time, though, I can’t insist that everyone uses my hub of choice. To this end, I’m happy to use the hub that my collaborators primarily use. In this case, it’s Microsoft Teams. Make no mistake: the Hub-Spoke Model of Collaboration applies to Microsoft Teams as well.

Lamentably, the move from e-mail to an internal collaboration hub isn’t natural for many folks. As a result, I often have to nudge people to post everything in there. A snarky message or two reminding people that it’s not 1995 usually does the trick.

Simon Says: When it comes to internal collaboration hubs, consistency is key.

Bifurcating communications into multiple apps, hubs, or formats is a recipe for disaster. Pick a lane and stay in it.

Feedback

What say you?