As a mid-manager, the last two chapters in the ToC appeal:
6. Becoming an Organization That Wants to Understand Itself
7. Fighting Dirty for Good Culture
Giant cookie banner says "Do not sell my personal information" + "switch the toggle to opt out".
Which is it? Am I switching the toggle to opt out of selling my personal information or am I switching it to opt out of NOT selling my personal information?
I shouldn't have to read a paragraph of fine print to tell if they are intentionally using a dark pattern or merely incapable of composing a simple declarative sentence.
It's a shame, because it looks like an interesting book.
I feel like there could be a lot of value in understanding the psychology of teams and using it to build an environment where they can thrive.
However, every person I've worked with who was into these workplace-psychology books started thinking of themselves as expert diagnosticians of other people's psychology. Every personality or problem got mapped back to a scenario from a book they read, even when it wasn't a good fit. They started believing they understood other people better than those people understood themselves.
You couldn't talk to them about problems unless you could figure out which book(s) they were using, read them yourself, and then played a game where you explained things to them in a way that would get them to match the stereotyped situations in their books.
So instead of saying that the requirements are changing too haphazardly and too often (which would get you labelled as being too rigid or a complainer or something) you would have to explain that the requirements changing process is harmful to the team's psychological safety or other buzzwords. They've read enough books saying that a manager's job is to provide psychological safety, they see themselves as the hero manager, and therefore they need to fix this problem to provide psychological safety for the team.
I loathed it all so very much. It's refreshing to go back to managers who just talk to other people like people. I'm sure my good managers also read some of these books, but they didn't put any one book on a pedestal or take it all too literally.
co-worker started reading "Extreme Ownership" and it improved his mindset and approach to problems. at the same time became extremely unbearable towards own team. if someone was complaining it was hard to get follow-up on a task from someone external he'd jump in and say "you're not owning it".
the tipping point for me was when he started preaching "Never Split the Difference". he'd gotten so cocky to the point he'd start meetings with "I already know how this is gonna end".
i don't mind these books as long as they come from a place of need, but it seems the main crowd are wannabe master manipulators. also, they can often be distilled to a couple chapters, not sure why they're so long.
I really do not recommend to buy the ebook in this web shop.
Its the worst UX I have ever seen in an online shop.
Normally you would pay and then receive a link to download.
Here it goes like this:
- you receive an email: Please create an account on our website, you will benefit a lot from it
- then another email: If you want to get the book you just payed for, you must register first and then enter this code: #20 digit cryptic string#
- you create an account, eventually successfully bypass the dark pattern to seduce you to accept spam mails from them ("click here if you do not want to receive spam mails from us").
- You log in an see: "No books in your account", where can I enter the 20 digit cryptic code?
- Another look at the mails, oh, they said, "If you want to receive your book, you have to create an account on ANOTHER website
- You create another acccount
- Log in, you see a message: "Please click on the link in your confirmation mail"
- no confirmation mail received
- Go back, click on "send confirmation mail again"
- Some time later, confirmation mail arrives. But just a mail with header and footer but no content, no link to click
- Try again, same result
- Obviously something went wrong, can i report the bug somewhere? Of course not!
I'm unable to purchase it there even though it is way cheaper than getting it elsewhere because of blocking bugs with my Canadian physical address. Postal code which is valid is considered invalid... my city name which includes a dash is considered invalid. The postal code is blocking.
I preordered the paperback through bookshop.org the day before it was released. Received it in the mail a day or two after it was released. No bad/unexpected UI.
In https://mastodon.social/@grimalkina/116743715688970777 she gives a concise explanation of the minimal groups paradigm where "People assigned to arbitrary groups immediately form strong allegiances, even though they haven’t been given any other psychologically meaningful cues about their group"
I wish I was on a software team so I could justify buying it. But but my $DAY_JOB is answering phones and fixing printer-jams in a medical practice, so not a lot of application there.
yikes. this is very out of touch with current trends.
i respect writing a book - ive written three, but if there’s a time when most tech leadership cared LESS about understanding software team psychology, i havent seen it.
truly a sad state of things. i love this topic and plan to read the book but i dont expect most people to care - the only mantra in software rn is to go as fast as possible on shitty features and burn people out.
of course above assessment is about the general state of big tech co’s. some pockets of sanity out there still at smaller companies but not many!
I found this one interesting. The authors note that often, developers avoid code reviews, and engage in a lot of unproductive behavior around them. They claim that a pretty simple one-session cognitive-behavioral intervention can dramatically change that.
Anyway, the longer I work in this field the more I see psychology as the dominant factor in team productivity. Assuming the job is doable, and you’ve hired good people, and the team has adequate control over their own work, that’s what’s left. You might argue that tool use or team practices are more important, but what stops you from adopting them or using them correctly? What stops you from learning from your mistakes? Usually something about your group psychology.
A lot of smaller organizations really struggle to collaborate with their software teams. Collaboration is hard, in general, but especially so if the organization isn't fluent and competent in software product development. Before you go diving into the psychology of your sad and despondent software team, look around them. Are the people working with them capable of supporting and engaging with these engineers?
software teams treat trust and conflict as soft concerns, then seem surprised when delivery slows and people leave. the subject is real, but the value depends on whether the book stays empircal instead of becoming another set of management scripts. useful frameworks help you notice failure modes, not give you new vocabulary to impose on poeple.
25 comments
[ 0.23 ms ] story [ 33.2 ms ] threadWhich is it? Am I switching the toggle to opt out of selling my personal information or am I switching it to opt out of NOT selling my personal information?
I shouldn't have to read a paragraph of fine print to tell if they are intentionally using a dark pattern or merely incapable of composing a simple declarative sentence.
It's a shame, because it looks like an interesting book.
However, every person I've worked with who was into these workplace-psychology books started thinking of themselves as expert diagnosticians of other people's psychology. Every personality or problem got mapped back to a scenario from a book they read, even when it wasn't a good fit. They started believing they understood other people better than those people understood themselves.
You couldn't talk to them about problems unless you could figure out which book(s) they were using, read them yourself, and then played a game where you explained things to them in a way that would get them to match the stereotyped situations in their books.
So instead of saying that the requirements are changing too haphazardly and too often (which would get you labelled as being too rigid or a complainer or something) you would have to explain that the requirements changing process is harmful to the team's psychological safety or other buzzwords. They've read enough books saying that a manager's job is to provide psychological safety, they see themselves as the hero manager, and therefore they need to fix this problem to provide psychological safety for the team.
I loathed it all so very much. It's refreshing to go back to managers who just talk to other people like people. I'm sure my good managers also read some of these books, but they didn't put any one book on a pedestal or take it all too literally.
the tipping point for me was when he started preaching "Never Split the Difference". he'd gotten so cocky to the point he'd start meetings with "I already know how this is gonna end".
i don't mind these books as long as they come from a place of need, but it seems the main crowd are wannabe master manipulators. also, they can often be distilled to a couple chapters, not sure why they're so long.
https://geraldmweinberg.com/Site/Programming_Psychology.html
Here it goes like this:
- you receive an email: Please create an account on our website, you will benefit a lot from it
- then another email: If you want to get the book you just payed for, you must register first and then enter this code: #20 digit cryptic string#
- you create an account, eventually successfully bypass the dark pattern to seduce you to accept spam mails from them ("click here if you do not want to receive spam mails from us").
- You log in an see: "No books in your account", where can I enter the 20 digit cryptic code?
- Another look at the mails, oh, they said, "If you want to receive your book, you have to create an account on ANOTHER website
- You create another acccount
- Log in, you see a message: "Please click on the link in your confirmation mail"
- no confirmation mail received
- Go back, click on "send confirmation mail again"
- Some time later, confirmation mail arrives. But just a mail with header and footer but no content, no link to click
- Try again, same result
- Obviously something went wrong, can i report the bug somewhere? Of course not!
I am still waiting for my book.
In https://mastodon.social/@grimalkina/116743715688970777 she gives a concise explanation of the minimal groups paradigm where "People assigned to arbitrary groups immediately form strong allegiances, even though they haven’t been given any other psychologically meaningful cues about their group"
I wish I was on a software team so I could justify buying it. But but my $DAY_JOB is answering phones and fixing printer-jams in a medical practice, so not a lot of application there.
i respect writing a book - ive written three, but if there’s a time when most tech leadership cared LESS about understanding software team psychology, i havent seen it.
truly a sad state of things. i love this topic and plan to read the book but i dont expect most people to care - the only mantra in software rn is to go as fast as possible on shitty features and burn people out.
of course above assessment is about the general state of big tech co’s. some pockets of sanity out there still at smaller companies but not many!
1) Human Technology (online journal, papers) - https://ht.csr-pub.eu/index.php/ht/index
2) Psychology of Programming Interest Group (papers) - https://www.ppig.org/
3) Cognitive Biases in Software Engineering: A Systematic Mapping Study - https://arxiv.org/abs/1707.03869
https://catharsisinsight.com/ , scroll way down to “Developers deserve science.”
I found this one interesting. The authors note that often, developers avoid code reviews, and engage in a lot of unproductive behavior around them. They claim that a pretty simple one-session cognitive-behavioral intervention can dramatically change that.
https://link.springer.com/article/10.1007/s10664-024-10550-9
Anyway, the longer I work in this field the more I see psychology as the dominant factor in team productivity. Assuming the job is doable, and you’ve hired good people, and the team has adequate control over their own work, that’s what’s left. You might argue that tool use or team practices are more important, but what stops you from adopting them or using them correctly? What stops you from learning from your mistakes? Usually something about your group psychology.