Skip to main content

Rands in Review

Do you work with people? Are you a person? Can you read?

Yes. Yes. Yes? Read on.

Are you reading a book?

Yes? Go and find that book and put it away now. Go on, and then come back. No? Good news, I am about to help you out.

Ready? OK: you should immediately read Managing Humans by Michael Lopp because it contains something of value to you. I can't tell you what it is, because I don't know you and your interests and your circumstances and your experiences and your co-workers and the other myriad things that make up who you are with your working head on.

But what I can tell you is that there is something - at least one thing, and probably more - in here that will have you nodding along in agreement, or gawping at the perspective that challenges your own, or shaking your head at the unwarranted certainty of a curt categorisation of colleagues and then shortly afterwards finding yourself mentally fitting your company's staff to it, and adding the archetypes that you need that Lopp doesn't describe.

Lopp - or Rands on his blog, Rands in Repose - writes from vast experience across a bunch of companies you have heard of. Slack, for now, but also Pinterest, Apple, Netscape and Borland amongst others. His prose has the patina of a practitioner and, as with Managing the Unmanageable by Mantle and Lichty that I reviewed recently, if you have any experience of working in a tech company you'll find episodes or characters or atmospheres that you can use as touch points to satisfy yourself that Lopp is a reliable witness, a plausible primary source, even if some of his stories and their participants are composites.

For me, interested at the moment specifically in resources that a new manager might appreciate, the message isn't so different from Mantle and Lichty's either. You can read my summary of that but Lopp characterises his take on it succinctly in the first words of the book:
Don't be a prick.
The 50 or so stylish essays that follow (in the third edition; I haven't read earlier ones) cover management and leadership of others, interpersonal relationships at any level, and self-management, all intertwined with the challenges of having to operate in a corporate environment, the structure and logic of which you'll have a better grasp of at some times than others.

Lopp offers short shrift the to the oft-discussed distinction between management and leadership and a sharp pin to the balloon that is the management ego in the book's glossary (which is also online):
  • Leader — A better title than "manager."
  • Manager — The person who signs your review.

The same glossary defines some terms that you've probably come across but would have preferred not to:
  • Human Capital — HR term that refers to the people you work with. You should never ever say this.
  • Individual Contributor — HR term that describes a single employee who has no direct reports. Don’t say this either.

Yet page 1 of Part 1 says (my emphasis)
We all have managers, and whether you’re the director of engineering or an individual contributor, one of your jobs is to figure your manager out.
A case of do what I say, not what I do, perhaps? I'm not so sure. More likely just one of those things. This book describes how Lopp goes about making sense of, and dealing with the world. He explains at length how and where and why he gathers his data, how he analyses it, what conclusions he draws from it, and the actions he takes as a result.

But that can't prepare him for all eventualities, can't account for all the googlies, can't prevent or catch all errors, can't predict all the points at which the rails and the wheels lose contact. All day long, we're in the real world, dealing with real humans in real time. And one of the key messages in the book, and laid out very early in it, is this:
Every single person with whom you work has a vastly different set of needs. They are chaotic beautiful snowflakes. 
So when a usually courteous colleague does something outlandishly rude it ... could be malicious. Could be a mishap. Could mean they hate you, and they've always hated you but manage to hide it. Could mean their marriage is breaking up. Could mean their project failed and they feel responsible. Could mean they've got indigestion. Could mean they have a new job and can't find a way to tell you. Could mean they just got a text telling them their mum won the lottery. Could mean nothing at all, it just happened. And now you have to deal with it, and with something else from the next person and a third thing with the one after that.
 ... that means great managers have to work terribly hard to see the subtle differences in each of the people working with them.
See. See the people who work with you. They say repetition improves long-term memory, so let’s say it once more. You must see the people who work with you.
As I reflect on the book while I'm writing this - and the writing is key for me to understand my reflections - I begin to see it as a guide for making a manual: a manual for becoming a better manager (big and small "m") of people. Lopp's descriptions are of his way of making his manual. And though his manual changes over time his guidance on constructing it do not or, at least, not as much.

You might feel that there's a little too much cop out, places where he says that he can't tell you what the best course of action is because your mileage will vary. But, for me, that's a self-evident truth. Any book that purports to tell me the right way to act in a situation devoid of the context of that particular instance of that kind of situation with those actors at that time is going to need some other extremely redeeming feature to get a place on my shelves. What you get from Lopp is the justification, the method or analysis (or both) and his result, with an implicit or explicit invitation to find your own.

For example, when he breaks meeting attendees down into personalities such as The Snake, Curveball Kurt, Sally Synthesizer, Chatty Patty, The Anchor and others he's not telling you that your meetings must have the same cast (although doubtless some recognition will exist). He is saying that if you were to observe with the same diligence that he has and does, you could find your own heuristics for navigating the tedium and politics, and heading off those ridiculous outcomes.

Lopp was a tester earlier in his career and one of my favourite blogs of his is The QA Mindset which ends like this:
It’s not that QA can discover what is wrong, they intimately understand what is right and they unfailingly strive to push the product in that direction.
I believe these are humans you want in the building.
This book is the QA mindset applied to interaction with other people in the face of their, and your, idiosyncrasies and the final chapter, titled Chaotic, Beautiful Snowflakes, reminds us of that:
The hard work of great leadership isn’t just managing the expected tasks that we can predict—it’s the art of successfully traversing the unexpected.
Yes. Yes. Yes.
Image: Google Books 

Comments

Popular posts from this blog

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested ...

The Best Programmer Dan Knows

  I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Beginning Sketchnoting

In September 2017 I attended  Ian Johnson 's visual note-taking workshop at  DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers  (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito...

ChatGPTesters

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00--  "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the T...

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w...

Build Quality

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in gener...

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report.  Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia.  ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...