<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Simon Whitaker on Medium]]></title>
        <description><![CDATA[Stories by Simon Whitaker on Medium]]></description>
        <link>https://medium.com/@s1mn?source=rss-53d184125a57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WMuNKB4hM3Y6wfY7KiaXmg.jpeg</url>
            <title>Stories by Simon Whitaker on Medium</title>
            <link>https://medium.com/@s1mn?source=rss-53d184125a57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:15:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@s1mn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What does unconscious bias look like?]]></title>
            <link>https://medium.com/@s1mn/what-does-unconscious-bias-look-like-9e2c9f3da4e2?source=rss-53d184125a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e2c9f3da4e2</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Simon Whitaker]]></dc:creator>
            <pubDate>Fri, 13 Jan 2017 07:19:34 GMT</pubDate>
            <atom:updated>2017-01-13T17:49:31.056Z</atom:updated>
            <content:encoded><![CDATA[<p>In a recent project meeting we were talking about a technical decision the team had made when implementing a particular feature on iOS. There were four of us in the room: me, an iOS engineer and a product manager (all men) and a female technical project manager. I took a few minutes to explain to the PM and TPM a couple of the fundamentals of iOS development, which helped to explain why we’d taken the direction we had.</p><p>After the meeting the TPM asked if she could have a word in private.</p><p>“When you explained the technical stuff, was that for my benefit, or the benefit of me and the PM?” she asked.</p><p>“It was for both of you,” I replied.</p><p>“OK, so is there any reason why you only looked at me while you explained it all?”</p><p>My gut instinct was to protest; I’m sure I would have looked at both of them in turn as I explained. But I took a moment to think back on the meeting, and she was absolutely right. When I explained the technical stuff, I addressed the explanation to her alone.</p><p>About a year ago I took the <a href="https://managingbias.fb.com/">Managing Unconscious Bias</a> training that Facebook offers. It was fascinating, and it highlighted a number of unconscious biases that I have, including: I have a bias for expecting men to be better at technical subjects and women to be better at arts subjects. (With a civil engineer for a father and an English teacher for a mother, it doesn’t take Freud to figure out where this one came from.)</p><p>I remember coming out of that training session feeling as though I’d really learned something useful about myself, but also feeling like I was now automatically a better person because of it. I’d identified and talked openly about my biases! Problem solved!</p><p>Yet here I was, a year later, having stumbled straight into the trap my biases had laid.</p><p>I thanked the TPM for asking me the question. It took courage to raise the issue, and I wanted first and foremost to acknowledge and validate it. She was right, and it mattered. It mattered not just because I had failed to manage my bias, but because my behaviour could actually enforce that same bias in others; a roomful of men just saw me explaining the complicated stuff to the woman in the room.</p><p>I also asked her to please continue to keep me on my toes, and to continue highlighting to me any time she saw my biases in action.</p><p>Most importantly, I developed a new tactic. I can’t conquer my biases, and I shouldn’t pretend they don’t exist, but I now have a concrete example of how they manifest themselves and I can compensate for that. In meetings, I need to divide my attention and focus equally around the room; <em>especially</em> if I’m explaining technical issues in front of a mixed-gender audience.</p><h4>The bit where I go meta</h4><p>Having reflected on this for a few weeks, I’d like to think there are some simple rules that I could follow in future.</p><ol><li>Always be open to feedback, especially feedback that pertains to known biases. Not just that; I need to be explicit about the fact that I welcome such feedback, e.g. by writing a blog post about it. (Told you it would get meta.)</li><li>Don’t beat myself up about this. These are unconscious biases. I screwed up, but I didn’t screw up with malicious intent. Being willing to have the conversation lessens the likelihood of a similar screw up down the road.</li><li>Say thank you. It takes courage to give feedback like this, especially feedback that swims upstream against a prevailing power dynamic (e.g. a woman giving feedback to a man; an intern giving feedback to an engineer). The TPM, in finding that courage, has gifted me a valuable, clear, actionable piece of feedback.</li><li>Think about strategies to help me counter my biases. For example, in this case I’ve started making a conscious effort to address everyone in the room equally. It’s not easy, but now I have that tactic in my mind I exercise it every opportunity I get.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e2c9f3da4e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>