Understanding Teams
Foundation and diagnosis — learning to see what's actually happening in teams before you try to fix anything
4–6 weeks · Team leads, new managers, and anyone trying to understand why their team isn't working
Foundation + Diagnosis — learning to see what's actually happening before you try to fix it
When I got my first real leadership role, my dominant feeling wasn't excitement, it was fear. Fear that I'd get it wrong, that the team would see through me, that people would start leaving and I wouldn't understand why until it was too late. Understanding how teams actually work, what holds them together and what quietly pulls them apart, became urgent in a way that reading about leadership in the abstract never had been.
What I kept discovering was that the instinct to fix things runs well ahead of the understanding to fix them well. A team that looks disengaged might be exhausted. A team that avoids conflict might have learned, through experience, that conflict gets punished. A team that appears to lack accountability might never have had the safety to admit when something's going wrong. The surface patterns repeat. The causes underneath them are almost never the same, and if you fix the wrong one you can make things significantly worse while feeling like you're being decisive.
This pathway is about building the capacity to see before you act. The sequence matters, and each piece earns the next.
Books and posts alternate throughout, sometimes a framework first and the lived experience second, sometimes the reverse, depending on what the sequence needs at that point. The posts are not summaries of the books that precede or follow them — they're a different angle on the same territory, grounding the ideas in specific situations rather than restating them.
Who This Is For
This pathway works for leaders at several different starting points:
- New managers inheriting a team — you want to understand what you've walked into before you change anything
- Leaders whose teams aren't performing but can't pinpoint why — something is off and you can't name it yet
- Anyone who's tried to fix a team and found it didn't stick — the process changed; the culture didn't
- People who've read the frameworks but want to see them in practice — you know what Lencioni says; this is what it looks like when you're in the middle of it
Some management experience helps, but you can start from zero.
What This Pathway Teaches
The core lesson: you need to learn how to see dysfunction before you can fix it.
You'll understand why honest feedback is the foundation of everything else and why most of us avoid it, the structural patterns that make teams dysfunctional and how they compound, what people actually need to feel safe and motivated, why invisible work creates invisible pressure, and what a spiral looks like before it becomes a crisis.
The deeper lesson, the one that takes longest to internalise, is that most team problems are not about skill or effort. They're about conditions. Change how you look at the team and you stop seeing only the symptoms.
The Reading Sequence
1. Radical Candor
By Kim Scott
Why start here: Before you can diagnose what's happening in a team, you need to be able to have honest conversations about it, and most of us are less equipped to do that than we think. Radical Candor is about the relationship between caring about people and being willing to challenge them, and why most of us default to one at the expense of the other.
What you'll learn: The Care Personally, Challenge Directly framework and the four quadrants that describe most feedback failures, why avoiding difficult conversations isn't kindness, why feedback without care just creates defensiveness, and how to move toward honest useful conversation without becoming brutal.
My experience: This was an early read for me and it immediately made sense of patterns I'd been watching in working relationships for years without having language for them. I'd worked with managers so careful not to upset people that they left problems to fester for months. I'd worked with others who challenged hard but never seemed interested in the person they were challenging. The 2x2 helped me see that both were failures, just different ones, and it helped me see where I was drifting depending on context and pressure, which I still do.
When to read it: First. You cannot diagnose what's happening in a team without the ability to have real conversations about it, and this gives you the foundation for everything that follows.
2. Care Personally, Challenge Directly (post)
Published on this blog
Why read this second: The book gives you the framework. This post gives you the specific situations where I watched the quadrants play out, including in myself.
What you'll see: What Obnoxious Aggression looks like when someone is technically right but has established no relationship with the people they're challenging. What Ruinous Empathy costs over time when someone quietly cleans up after problems rather than naming them. And the moments where I was the one drifting, staying silent in a meeting, not investing in a contractor, avoiding a conversation I should have had weeks earlier. This isn't a summary of the book. It's what happened when I tried to apply it.
3. The Five Dysfunctions of a Team
By Patrick Lencioni
Why read this third: Once you can have honest conversations, you need a map of what you might find. Lencioni's model is the most useful framework I've encountered for understanding how teams break down, not because of bad people, but because of structural failures that compound over time.
What you'll learn: The five dysfunctions and how they stack, absence of trust leading to fear of conflict, fear of conflict to lack of commitment, and so on up to inattention to results. How a team can look functional on the surface while quietly failing at every level. And the idea that stayed with me longest: that an A player isn't an A player if they don't play for the team. Talent density means nothing if the individuals aren't playing for the collective.
My experience: I read this early in my leadership journey and the trust layer has stayed with me ever since. Before conflict, commitment, accountability, results, before any of that can function, there has to be trust. Without it everything above it is performance, and teams that look like they're operating can be running entirely on compliance and self-preservation. That framing shaped how I thought about team harmony from the beginning.
When to read it: After Radical Candor. You've got the foundations for honest conversation — now you need the structural map of what you're looking for.
4. Leaders Eat Last
By Simon Sinek
Why read this fourth: Lencioni gives you the structure of dysfunction. Sinek explains the conditions that either allow trust to form or quietly prevent it. This book is about what leaders do, and don't do, that creates the environment for safety and performance.
What you'll learn: The Circle of Safety, why people perform differently when they feel protected rather than threatened, why short-term pressure decisions erode long-term trust, and why once people feel genuinely safe, ideas and creativity flow in ways they simply don't in environments defined by anxiety.
My experience: I'm a long-standing Sinek reader and Start With Why is a book I reference constantly, but this one earned its place in the pathway on its own terms. I read it later, after I'd already built what I'd now recognise as circles of safety with my first teams, partly driven by that early fear of losing everyone. Reading it gave me language for something I'd been doing by instinct. The circle of safety felt like a direct extension of what Lencioni establishes at the trust layer, and once you've built it, it functions as a genuine multiplier for performance, because people bring more of themselves to work when they're not spending energy managing threats.
When to read it: After Five Dysfunctions. Trust is the foundation — this explains how leaders build it or quietly undermine it over time.
5. Dysfunction from the Ground Up (post)
Published on this blog
Why read this fifth: The books have given you the frameworks. This post shows what dysfunction looks like from the ground floor, not dramatic, not villainous, just a quiet bureaucratic instruction to slow down, stay in your lane, and stop making things visible that people would rather not see.
What you'll see: A council job in Sheffield, a van full of recycling bins, and a system that had learned through painful experience that doing the work well was dangerous. Lencioni's absence of trust and fear of conflict made concrete in the most ordinary possible setting, before I had the language for any of it.
6. When Work Is Invisible: The Hidden Cost of What You Can't See (post)
Published on this blog
Why read this sixth: Dysfunction often isn't about behaviour or attitude, it's about visibility. When people can't see what's happening, what's blocked, what's in progress, what's creating pressure, they fill the gaps with assumptions. This post is about what that costs and what changes when you make the work visible.
What you'll see: A maintenance team being pulled from job to job, never finishing anything, and two sides of a working relationship, production and maintenance, both convinced the other didn't care, neither able to see the full picture. A print factory with cards on a production board and pallet spaces behind machines. Different contexts, same principle: visibility doesn't fix the problems, it makes them fixable.
7. Making Work Visible
By Dominica DeGrandis
Why read this seventh: The post gives you the experience. This book gives you the most practically useful framework I've read on where time actually goes and why work takes longer than it should.
What you'll learn: The five thieves of time, too much work in progress, unknown dependencies, unplanned work, conflicting priorities, and neglected work, how each one creates invisible drag on a team's capacity, and how making them visible is the first step to doing anything about them.
My experience: I came to this after years of running into the same patterns across manufacturing, maintenance, and software teams without having clean names for them. Reading it I kept recognising things I'd been fighting for a long time across very different contexts. It's probably the most practically useful book I've read on the topic, not theoretical, just a clear-eyed account of the patterns that steal capacity and how to surface them.
When to read it: After the post. The post shows you what the thieves look like in practice — the book gives you the framework to name them and act on them.
8. Three Signs of a Miserable Job
By Patrick Lencioni
Why read this eighth: Making Work Visible looks at how invisible work damages delivery. This book looks at how invisibility damages the person doing the work. The two are connected, and understanding both is essential for diagnosing what's actually happening in a struggling team.
What you'll learn: The three signs, anonymity, irrelevance, and immeasurement, and why people become miserable at work not because the work is hard but because they can't see whether it matters, whether anyone notices, or whether they're making a difference. Lencioni writes in parables and this one is typically accessible, a short readable story that leads into the framework cleanly.
My experience: Where Five Dysfunctions explains what breaks in the team, Three Signs explains what breaks in the person, and the two sit alongside each other rather than overlapping. In teams I've worked with that were genuinely struggling, I could see all three playing out: people who didn't know if their work mattered, people who couldn't measure their own impact because nothing was getting finished. That's misery, regardless of salary or title.
When to read it: After Making Work Visible. You've seen how invisible work creates system problems — this shows how it creates human ones.
9. Drive
By Daniel H. Pink
Why read this ninth: You now understand what breaks trust in teams, what makes work invisible, and what makes it miserable. Drive asks a more fundamental question: what actually motivates people? The answer is less intuitive than most management practice assumes.
What you'll learn: The distinction between intrinsic and extrinsic motivation, why autonomy, mastery, and purpose are the real drivers of performance for complex work, and why carrot-and-stick approaches that work for simple mechanical tasks actively damage performance for anything that requires thinking.
My experience: A recent read for me, but I recognised the patterns immediately in people I'd worked with over the years. The difference between someone who is intrinsically motivated and someone who isn't is visible every day in how they engage, what they bring, and how they respond to difficulty. Being on a team where people are intrinsically motivated is a completely different experience, and Drive gave me a model for something I'd been observing for years without having fully articulated it.
When to read it: After Three Signs. Lencioni identifies what destroys motivation. Pink explains what creates it.
10. Breaking the Spiral (post)
Published on this blog
Why read this last: The books have given you the frameworks. This post shows what it looks like to walk into a team where everything has already broken down, and what it actually takes to reverse it.
What you'll see: A development team of twenty-five people, 54% attrition, eNPS of -37, developers disconnected from the business, tickets sitting in blocked status, nobody sure whether their work mattered. One-to-ones that weren't interrogations. A tech ops meeting nobody believed in for the first six weeks. OKR sessions outside the building with post-its and whiteboards, the spiral reversing slowly and not cleanly, and what was actually driving it. Not a framework applied step by step, just showing up, caring personally, and helping people see that their work mattered. That's what most of this pathway is really about.
What You'll Learn
By the end of this pathway, you'll understand why honest feedback is the precondition for everything else and what happens when it's missing, how dysfunction compounds structurally from the absence of trust upward, what leaders do consciously or not that creates safety or destroys it, how invisible work damages both delivery and the people doing it, what motivation actually requires beyond salary and title, and what a negative spiral looks like in practice and what it takes to reverse one.
You'll be able to have difficult conversations earlier because you understand what avoidance costs, recognise the structural failure modes in a team before they become a crisis, see invisible work and name what's creating drag, diagnose motivation problems rather than labelling people as disengaged, and read a struggling team more accurately before you decide what to do about it.
What This Pathway Won't Teach You
This pathway is about diagnosis, not intervention. It won't tell you how to build a high-performing team from scratch, how to hire well, how to establish communication rhythms, or how to make change stick. Those are real questions — they belong to the next pathway, not this one.
It also won't give you a checklist. The frameworks here are tools for seeing more clearly, not scripts to follow. Every team is different. The patterns repeat; the specifics don't.
Understanding is not enough on its own. But acting without understanding is worse, and this pathway is the foundation — the ability to see what's actually happening before you decide what to do about it.
Estimated time investment: 4–6 weeks if you're reading actively and reflecting as you go. Lencioni writes short accessible parables — you can get through Three Signs or Five Dysfunctions in an afternoon. The posts take 10–15 minutes each. The thinking takes longer.
Next steps: Start with Radical Candor. Read it with a specific relationship in mind, someone you manage, someone you work alongside, someone you find difficult. The quadrants will do the rest.
A note on sequence: I didn't read these books in this order — some came years apart, in different roles, prompted by different problems. But if I were starting today, trying to understand teams and what makes them work or not, this is the sequence I'd recommend. Each one builds on the last. The posts ground the frameworks in something real.