I’ve read a number of articles from the likes of Github where they decided to go fully distributed over hybrid because it only works really well if everyone is remote. A lot of companies are going to experience the messiness of hybrid when they decide to be “more remote” but not fully remote. How can they employ “more remote” without being fully remote?
We had this challenge at KISSmetrics when we went hybrid after years of being fully remote. The key is to think about everyone on the team's experience.
After some iterations with our processes and lessons learned we realized one simple thing:
People who are remote should not feel like second class team members.
For example, if you're doing an all-hands in a hybrid company I would strongly suggest that you have everyone join via Zoom virtually instead of letting folks in the office view folks who are speaking live. And also potentially encourage chat via Slack at the same time if that's appropriate.
The key is to ensure that the experience people have regardless of how and where they work is consistent across the team. If it isn't you'll see a lot of negative cultural damage as a result. People will not feel part of the "same team" and instead you'll develop an "us vs. them" phenomena that is best to avoid.
This question is part of an AMA with Hiten Shah.View entire AMA with Hiten Shah.
Mixpanel, Amplitude and several others are more for B2C use cases. Coz of this, account level (usage at the company level) grouping is either very tough OR available only at their enterprise-level ...