3 ms·
Seriously, I don't know why this is such a hard problem for people. "We're building tax software. Should we get a tax consultant to look it over and identify p
by danShumway 8y ago
Seriously, I don't know why this is such a hard problem for people.
"We're building tax software. Should we get a tax consultant to look it over and identify problems?"
"We're building a programming IDE. Should we get some programmers on our design team? Should we maybe eat our own dog food and have our programmers use it internally for development?"
"We're building a screen reader. Should our QA team have some blind testers on it?"
"We're building a product that we're marketing to women. Should women be involved in building it?"
Sure you can get around these issues by doing extra market research, but in basically every other area of development we understand that it is an asset to have your designers and builders be intimately familiar with the problems you're trying to solve. The cheapest, most efficient way to make your design team intimately familiar with problems that women face is to hire women.
It's no different than hiring security experts if you're building serverside software - you want some people on your team to be an early voice of reason; to be able to raise their hand early in a code review or a tech demo and say, "Hey, just so you know that's an XSS attack vector," or, "Hey, just so you know I've actually had periods that last longer than 10 days."