The Team with Resolve

Some years before I sold my consultancy, I took my senior team away for two days and came home with the best plan we had ever written. Three weeks later a difficult client made us an offer that cut across it, and the plan quietly died. Nobody lied at the away-day. The alignment was real. It just wasn't built to carry weight.

That is the territory of this book, the second in the series. The first asked what pressure does to an individual leader's discipline. This one moves up a level, to the leadership team, the single unit that either holds together under load or comes apart. Its central idea also fits in a sentence: pressure reveals what a team is really aligned on. What a team agrees when nothing is at stake tells you very little. What it holds to when something is at stake tells you everything.

The first part is an honest look at how teams come apart. It maps the alignment illusion, where the room agrees and the diaries disobey, the seams that pressure goes looking for, and a failure cascade that starts with a silence rather than a fight. It also visits the car park meeting, where the real conversation happens ten yards from the room where it could have changed something. The second part rebuilds the five disciplines of the RESOLVE Framework as shared practices, things a team does together rather than five things its members do separately. The later chapters turn to Resolve itself, the shared will and mutual commitment that make the disciplines hold, and to the machinery that keeps them holding: meeting design, decision rights, a maturity ladder that runs from Polite to Resolved, and the one-page Team Standard that survives its authors and its first hard test.

A team can fail while every person in it is doing their job well. I watched it happen, in my own firm and in the businesses I have coached since, and I have also watched ordinary teams build the opposite. There are no personality profiles in this book and no trust falls. Nobody will be asked to describe themselves as an animal. There is a set of learnable disciplines, the stories of teams that held and teams that didn't, and one question to start with: the last time it really mattered, did your team hold together, or did everyone protect their own patch?