The Psychology of Software Teams

by Cat Hicks

Genres: Psychology, Management, Programming, Nonfiction, Technology, Leadership

196 pages, Hardcover

First published July 14, 2026

Reviews

[Thom]

Software is everywhere, and not just apps running on a screen. This book looks at the team dynamic behind writing great software - which is pretty much never a solo effort.

Historical anecdotes often cite the "lone genius", and that creates problems not just for the team around them but also the genius themselves. Not surprisingly, this is a thing psychologists have been studying for a while now, and this book details related studies that show both problems and proposed solutions to building a better team. The focus is primarily software, of course, but the psychology would apply to other teams as well.

The author spends a good section on AI, which proponents sell as either a genius developer or competition for them. The negative effects from this are not balanced by many gains, and Hicks gives good examples of this.

Data gathering, done properly, can provide the best management and measurement of teams. This book details that, along with how best to propose changes within the team and achieve success. No quick fix here, but this is a great blueprint for solid software teams.

Not a lengthy book, but it is a solid read. I pre-ordered it shortly before release (July 14 2026), and received it soon after. I already have friends asking to borrow it! Highly recommended.

[Jan Ryswyck]

In this day and age of probabilistic text generators, this book based on empirical evidence might become one of the most important and influential work for current and future software engineers. It’s my hope that the software industry will come to it’s senses at some point in the future, and transition to a more humane approach towards people inside organisations, and finally move away from the brains-in-jars mindset.

[Niklas]

It puts experiences and beliefs I already had into a psychological context, explaining why they matter and how we can use these ideas to create a more sustainable work environment.

Sadly, the “brains in jars” faction probably won’t read or understand this book. So I hope we can succeed in addressing these problems from the ground up.

[martyn benny]

The Psychology of Software Teams promises to be a timely and essential contribution to the growing conversation about the human side of software engineering. While technical expertise often dominates discussions about successful software development, Cat Hicks shifts the focus toward the psychological, social, and organizational dynamics that truly determine how teams perform.

One of the book's greatest strengths is its recognition that exceptional software is built by people, not just processes or programming languages. By examining the cognitive and interpersonal factors that influence collaboration, communication, decision-making, trust, and resilience, Hicks highlights the often-overlooked elements that separate high-performing engineering teams from struggling ones.

The subject could not be more relevant. As software development becomes increasingly collaborative and globally distributed, understanding team psychology has become just as important as understanding technical architecture. This book appears poised to provide leaders, engineers, researchers, and managers with valuable insights into creating healthier, more productive, and more innovative engineering cultures.

Drawing on psychological science while remaining grounded in real-world software development, the book promises to bridge the gap between academic research and practical application. Rather than offering simplistic management advice, it appears to explore the deeper human systems that influence creativity, problem-solving, psychological safety, and sustainable performance.

Perhaps its most valuable contribution is reminding readers that software engineering is ultimately a human endeavor. Great products emerge when individuals feel safe to contribute ideas, learn from mistakes, and collaborate effectively toward shared goals.

Insightful, relevant, and forward-thinking, The Psychology of Software Teams looks set to become an indispensable resource for software engineers, engineering managers, technical leaders, organizational psychologists, researchers, and anyone interested in building stronger, healthier, and more effective technology teams.

[Mark Sutherland]

The next book every software manager should read, but won't and will instead continue to perpetuate the same tired tropes and counterproductive interventions.

There is something extremely validating about seeing a trained psychological researcher come into the software field and clock the pervasive rakes we've laid out on the lawn for us all to collectively step on, one after another. For some reason, rather than despair and go find a more sensible industry to study, she's documented our main mistakes and laid out a path to overcoming them, complete with all the citations and references you could want. There's nothing completely revolutionary here, we've been arguing against 10x programmers and crunch and so on for decades, but having some of those arguments backed up by research and developed more fully than a collection of blog posts stapled together is a significant step forward.

Read it, tell your colleagues and managers to read, and maybe in a few years time we'll be having more interesting arguments.

[José Maia]

Nothing is especially original or directly applicable, the material covered reads like a summary of best practices and research around these topics, almost like a State of the Art.

The magic is how the book integrates all this information into a people-centric framework. Solid read, especially if you're not familiar with stuff like psychological safety in teams.

[Steve Fenton]

Having followed Cat Hicks' work for some time, I knew this book would be golden. The themes of collaboration and conditions for innovation remain crucial topics if you want to have successful software delivery over the long term.

[Pawel]

Nothing interesting, unfortunately. A lot of „when’s and if’s”, not a lot of specific advice or examples from the real world. A huge letdown for me.

[heidi]

Review on Amazon: Solid, smart research on how to build teams that work their best https://a.co/01ZYwN0B

[Isidro López]

Highly recommendable.

[Richard Bown]

I was really looking forward to this book, but as an experienced software engineer and engineering leader who's read most of the previous books on psychology in dev, I didn't find anything revolutionary. As an engineer, I'm already interested in and well-versed in the socio-technical landscape, so I was hoping for more depth on *what* I can do differently day-to-day. As an experienced leader in software dev, I didn't feel there was much I could use practically at an organisational level beyond changing cultural approaches, which I feel are covered better elsewhere around how to organise/devolve work. The book did at least validate my observations. It's nice to have the research formalised and brought together, although I felt it was reference-heavy in a way that wasn't very approachable. It may be good for those new to leading software organisations and wanting to get started, but even then, I would say it's a little opaque in places. I found myself constantly asking "who is this book for?" so perhaps it just wasn't for me.