Last week, I asked a colleague how her recent transition to remote working was going on. Was her internet and VPN working ok? Did she get access to the docking station, screen, and mouse from the office? Was she proactively taking breaks?
Her answers reassured me: Yes, yes, and yes.
She also told me that after finishing her work at 6.00 pm she rushed to the supermarket to only find broccoli and Brussels sprouts. We made fun about how some people rather starve than eat certain food. It also made me realize that I’ve failed as a leader.
The scarcity trap
The picture that accompanies this post it’s how the supermarkets looked like where I live a week ago. It’s how they looked all this week too. And this weekend as well. Me too, I’ve felt the pain and stress of visiting 3, 4, 5 supermarkets to gather the basic food and toiletries I needed.
Interacting with tech products that reject me as a user or provide a subpar experience elicits two very different responses in me.
As a Head of Customer Service with 25+ years’ experience in scientific and engineering software, I’m well aware of the constraints imposed by a finite R&D team and an ever-growing list of customer enhancement requests and bugs to fix. It’s teams like mine that build those lists and provide feedback to the product team on their prioritization. Which features and fixes make it into code depends on a multitude of factors: the difficulty to implement them, their alignment with the vision for the product, and their potential impact on the user experience and expectations. This last criterion is assessed using fictional user personas created by the product team as a representation of the ideal customer. The closer the requester of the feature is to one of the user personas, the higher the chances of implementation into the product. However, if the issue is considered an edge case – not representative of a substantial customer base – then it will mostly get rejected or postponed indefinitely. Every new feature and fix must demonstrate its ROI.
As a woman that cumulates several out-group identities – e.g. non-native English speaker, poor vision – I’m used to the frustrating feedback that my mediocre user experience is deceptively cataloged as an edge case. Why deceptively? The average tech Continue reading →
Before using the term diversity and inclusion advocacy, I had already identified the need for it. I’m a woman, STEM studies, work in tech, and I’ve been an immigrant all my life. This intersection of out-group identities has often resulted in being seen as the other. It has also prompted me to consciously endeavour to listen and empower members of other out-groups.
However, a little more than a year ago, I realized that, unconsciously, I was silencing those other voices.