4 ms·
> Inclusive By Default > We all tend to operate within explicit and implicit hierarchies within our teams. Explicitly we know we have a manager we should defer
by avgcorrection 4y ago
> Inclusive By Default
> We all tend to operate within explicit and implicit hierarchies within our teams. Explicitly we know we have a manager we should defer to, and that there are executives and other roles that are important to the team. Implicitly we know there are people with more experience in particular topics or simply more social capital within the team. If you see someone above you in either of those hierarchies, you're more likely to pause and listen, and potentially to decide it's not worth the effort to bring your ideas forward.
> Our goal by removing typing indicators is to help teams build environments where anyone can think through an idea and bring it forward without having to wait for those above them to speak up first. We want everyone to feel included in discussions when they have an important idea to bring to the table.
We make a chat app for teams with a clear chain of command (I don’t know just going by context). By removing this one super-modern chat app quirk we will be able to say that we are “inclusive by default”, even though the whole context that your team operates in contradicts our stated aim.
I don’t know I just think that the hierarchy of the group trumps such trivialities.
- deleted 4y ago[deleted]
- commondream 4y agoI can see where that opinion on how I wrote it comes up. My meaning was more that most teams operate with a defined chain of command and another implicit seniority/culture structure. We're trying to find interesting ways to be more inclusive of people lower in those structures by not prompting them to wait for those above them to finish speaking before they go ahead and share their own ideas. Hierarchies definitely trump those trivialities and are a huge hurdle to being more inclusive, but we also see these small tweaks as steps in the right direction.