Diversity and Inclusion are words that are normally thrown around by people of a certain persuasion. In fact, they were among the key principles espoused by one of my earlier employers as well (to their credit, some of their diversity and inclusion sessions did a lot of help broaden my worldview).
However, as I’ve argued earlier on this blog, in a lot of cases, arguments on diversity and inclusion are (literally) only skin deep – people go big on diversity of sex, sexuality, skin colour, nationality and so on while giving short shrift to things like diversity of thought, which in my opinion plays a larger role in building a more successful team.
I’ve also mentioned earlier on this blog about how some simple acts of inclusion can go a long way – for example, I’d mentioned about how building a pedestrian walkway, or pedestrian crossing with signals, would help make one of the roads in Bangalore more inclusive towards pedestrians (a class of people the usual proponents of diversity and inclusion don’t care about).
I was reminded of diversity and inclusion when the recent hoopla about messaging apps happened. A number of my contacts said they were leaving WhatsApp and moving to Telegram or Signal. Others said they weren’t going anywhere and were sticking to WhatsApp, and that Facebook’s new privacy rules were nothing new.
From my personal point of view, since I didn’t have a view on this messaging apps issue, the best solution turned out to be “inclusion”.
I’m on all apps. I’m on Signal, and Telegram, and WhatsApp, and iMessage, and good old SMS. However you choose to reach me, I’m there to receive your message and respond to you. In that sense, when you don’t have a strong opinion, the best thing to do is to be inclusive.
Of late I’ve realised it’s the same with language. Since I now work for a company that is headquartered in Gurgaon, a number of colleagues instinctively speak in Hindi. Initially I used to be a bit snobbish, and tell them that my Hindi sucked, and when they spoke Hindi, I would reply in English.
Over time, however, I’ve realised that I’m only being an asshole by refusing to be inclusive. Since I know Hindi (I got more marks in Hindi in Class 10 board exams than I did in English – not that that says anything), I should let the people decide whether I’m worth talking to in Hindi at all. I’ll talk to them in my broken Hindi, and if they think it’s too broken they can choose to switch to a language I’m more comfortable in.
And a week ago, Pranay and Saurabh of the Puliyabaazi podcast asked me if I’m willing to go on their (Hindi) podcast to talk about logical fallacies and “how not to use data”. I immediately accepted, not only because it’s a great podcast to be on (they’re fun to talk to), but it also gives me an opportunity to show off my broken Hindi.
The episode dropped on Thursday. You can listen to it here:
I realised while I was recording that my Hindi has become really rusty, and I found myself struggling for words many times. I also realised after the episode dropped that I don’t even understand what the title means, yet I’ve been happily sharing it around in my office! (a colleague kept asking me if I knew this word and that word, and I realised the answer to all that was no. Yet I had made assumptions and gone on with the podcast – another example of my own “inclusiveness”!)
Henceforth I’m never telling a colleague that I don’t know Hindi. However, if I find that someone overestimates my level of Hindi I might inflict this podcast on them. Even then, if they choose to speak to me in Hindi, so be it! I’m going to make an attempt to be more inclusive, after all.