But yeah, we do have a 5 to 1 male to female ratio and a geekier than average audience.
Given that we selected 4,000 man and 4,000 women (randomly), how does the preponderance of men in our broader dataset effect this particular analysis?
Sorry if I'm being obtuse-- I didn't do the actual analysis and I'm really pretty rusty on my stats.
Though, that's not why I use RescueTime - I just love data. (And by the way, would love to download the fine-grained CSV for all of my activity for all time)
So yes, you've adjusted for the tendency to have more men than women. But you still haven't wound up with a random sampling of people out there.
To get that you'd have to select a random set of people, ask them to participate in your study, and go from there. Which would immediately hit you with the fact that over half of the USA is functionally illiterate and therefore does not use computers very much.
More realistically, I think it'd be interesting to correct/adjust by profession. i.e. do this same analysis for JUST software engineers, for example, to correct for the likelihood that RescueTime women probably have a different distribution among the assorted career paths.
How many teachers are in your sample? How many nurses? (extremely few - how would the tool capture that?)
Or more insiduously compare the number of engineers to the number of people in marketing. Both are "knowledge workers", but they have a very different gender breakdown. And they also have a very different day. Someone in engineering is on their computer all day, someone in marketing or sales probably not. If you are making sales calls all day instead of looking at an IDE, you can be vastly more productive than an engineer staring at a blank screen, but that doesn't show up in RescueTime at all. It's one thing one you are on a team and can account for that, it is another when you make a generalization about the population.
All of your data can be explained with other rational besides "men are more productive than women". Your company approaches the world from the view of engineers to begin with, and then slaps that bias on top of a faulty set of data. You should be careful with this or you are going to have NOW breathing down your neck (I guess all press is good press, but do you really want to make your product piss of women to that extent?).
Again, it's SUPER obvious to us (and to you, apparently) that our dataset is NOT representative. Do you think it'd help if I added that to the bottom of the post? We just assumed that's obvious once we described the value proposition.
He said picking an even sample of male and female removes the male/female bias, but only that bias.
Edit: Granted, that's not strictly sufficient because the human population is not 50:50 M/F, but that's a side issue.
AKA, if the gender bias was caused by an occupation bias fixing the gender bias does not fix the occupation bias.
Anyway, this blog post and much of the surrounding discussion make me really sad about how poorly people understand data analysis.
probably a better model: productivity ~ gender + occupation + gender:occupation