This Book Would Be Really Useful
I’ve often blogged about books I want to read that I don’t know enough to write; here’s another entry in that list:
I want ten chapters, each describing a study that an overworked VP Eng could feasibly implement to assess their software development team and practices.
In more detail:
-
Ten chapters, each about 15 pages long, because (a) I don’t think an overworked VP will read any more than that and (b) I think ten different studies will pretty much cover the possibilities.
-
Describing means both “here’s a template you can start from” (down to the level of specific questions in questionnaires and some Python scripts to analyze the data if the study is quantitative) and “here’s an explanation of the science behind it that someone with no training in psychology or the social sciences will be able to understand and will find persuasive”.
-
Feasibly implement means set up with a few hours of work given the template mentioned above. It also means having a rationale that’s comprehensible and acceptable to higher-ups. “We want to know if our developers feel fulfilled” is hard to sell to tech bros; “we want to get a handle on which parts of our AI spend are actually helping” is a lot easier, even if the questions and the analysis are the same.
-
Assess doesn’t just mean “measure quantitatively”. As I’ve said elsewhere, UX teams have a long history of using qualitative methods to answer interesting-to-capitalists questions in ways that are culturally acceptable in Silicon Valley.
So, who would write such a book? My first choice is probably too busy to do more than a single chapter (if that), but people who took part in It Will Never Work in Theory might find it interesting enough to contribute. I think it would be useful and timely, and a way to get researchers and practitioners to talk to each other. If this sounds like something you’d be interested in, please give me a shout.