I read a fair bit, and increasingly, I’m kind of holding my nose and reading business-oriented books in hopes of leveling up my game as a worker who leads people. A couple of years ago, I might have struggled more with technology challenges in my work, as I was writing code and chiefly leading people who were writing code. About a year-and-a-half ago, I took on a split role in which I was still leading a team of developers but was also leading a handful of leads in our support division (the division under which my developer team worked). In the latter portion of 2017, I switched my full-time focus to leading leads, and at present I have 10 folks under my direct care and about 70 under my care directly or indirectly. This tightening of focus gives me more mental bandwidth to spend on learning how to improve as a leader than I had had previously, when I was also focusing on how to be a producer of software. Now I think a lot more about things like trying to help articulate and execute a vision for the departments I work with, helping navigate change more effectively, designing and implementing programs in the service of professional development for the folks in my overall department, and other abstract things I hadn’t had a lot of prior experience with.
So I’ve really ramped up my focus on reading business-oriented books. I don’t typically enjoy this kind of writing. I prefer to get lost in an imagined story or to think about the architecture and plumbing — the technique — that goes into making a piece of fiction resonant and innovative or just well put-together. I don’t generally like the tone that self-styled gurus can strike, and I think there’s a lot of this tone in the world of business books. I have tended to find these kinds of books kind of boring, or at any rate inapplicable to my life and thus not useful. Well, now, with a more intense focus on the kind of work these books tend to address, I’m finding the practice of reading them more useful.
For a couple of years now, I’ve kept very brief remind-myself sorts of reviews at GoodReads, but these aren’t comprehensive at all or really useful to anybody but me. Part of my goal in developing myself as a lead is to also help develop the leads I work with. One way of doing this is to act as a sort of — I forget where this colorful term came from, but it applies here — a shit umbrella for the things I’m reading. That is, I’d like to be able to tell people “it’s not worth your time to read this book; its salient points are A, B, and C, but you don’t need to kill time reading the whole book” or “this book is well worth a deeper read and will help you further develop your thoughts on X.” Because I’m forgetful, my path to providing this sort of service is to take better notes on the things I’m reading and to go ahead as soon as I finish something and determine whether I think it’s worth somebody else’s time or not.
To that end, I’ve started BookNotes.blog. I tend in general toward maximalism in my writing, but here I’m trying to offer brief summaries with in most cases a verdict about whether the book is worth a closer read or not. My hope is that this’ll help me preserve my verdicts and memories of these books in a way that’s useful to others. I’m just one shit umbrella with one opinion, of course, so it’s worth only whatever the value of my specific opinion is. At some point, I may invite others to contribute to the blog as well. My summaries aren’t terribly incisive or consistent in rigor or tone. But there they are, for whatever they may be worth — if you’re thinking of reading a business-oriented book and have found conversations with me about books to be worthwhile, maybe these short articles will help you decide where to spend some of your reading attention, or where not to.