I was honored to speak at the TRANSform TECH summit last week put together by the Transgender Law Center, Lesbians Who Tech and SFDC (at SFDC headquarters no less!).
Here are the slides of my presentation. What the slides don't convey is the context. Us data geeks love for data to be rigid. It makes for such pretty data. But does it really need to be? No, the answer is no. We can be more fluid in our data collection and use.
If you need ammunition for your higher-ups to implement such changes, these best practices are universal. They are relevant to so much of your client/constituent community.
For instance, I used myself as an example. TJ is not my legal name. However, I have gone by TJ instead of Tracy for almost two decades. It drives me batty when my legal name is gathered and then used in emails, direct mail, internally at work in staff rosters, etc. My gender is also assumed and mass updated. I often get calls and mail to Mr. TJ Warfield. Guess what, those end up straight to the do not call list or in the trash, I don't even bother to look at them.
For me, a privileged, cis, white female, this is an annoyance - a frustration. To those in the Trans and gender non-conforming community, it is a matter of safety and security. Do you really want to be the organization that makes your clients, customers, donor and employees feel threatened and violated?