Playbook
Fixing a Struggling Team
Four frameworks for a team that is not working: find the layer that is actually broken, judge whether you are watching a fault or a phase, check the team was built for the job in the first place, then have the one-to-one conversations that change things.
When one of my teams was struggling, my instinct was always to fix the noisiest thing in the room. The missed deadline, the argument, the person everyone had privately decided was the problem. Twenty years of running a business taught me that the noisy thing is rarely the broken thing. A struggling team usually struggles for a reason that sits several layers below the symptom, and no single framework will take you all the way down. So this sequence works the way a decent doctor works: diagnose before you prescribe. Five Dysfunctions finds the deepest broken layer, which is usually trust, whatever the presenting complaint says. Tuckman then asks whether you are looking at a fault or a phase, which saves a great deal of overreaction. Belbin checks whether the team was ever built to do the job at all, because some teams struggle by design rather than by dynamics. GROW turns the diagnosis into one-to-one conversations with dates attached, because in the end change happens one person at a time. Run them in this order and you treat the cause. Jump straight to coaching and you will spend months helping people cope with a structure that keeps putting the problem back.
Org, people & execution
The Five Dysfunctions of a Team
Lencioni's pyramid of five cascading team dysfunctions, from absence of trust at the base to inattention to results at the top, used to diagnose why a leadership team underperforms and to decide where the repair work has to start.
Start at the bottom of the pyramid rather than at the symptom that put the team on your agenda. Missed commitments and poor results sit at the top; the cause almost always sits lower, and the lowest layer is trust. Lencioni means the vulnerability kind, being able to admit weakness, rather than confidence in each other's competence. Teams score themselves well on the second while lacking the first entirely. Your output is short: which layer is the deepest broken one, because that is where the repair starts.
Watch forThe trap is marching in and exhorting everyone to focus on results, when the whole point of the pyramid is that the top cannot be fixed at the top.
Org, people & execution
Tuckman's Stages of Group Development
A five-stage account of how small groups develop: forming, storming, norming, performing and adjourning. Each stage pairs a relationship problem with a task problem, giving leaders a language for why a capable team is not yet delivering and what the current stage needs from them.
Now put the friction in time. Tuckman's stages exist to make one claim worth keeping: conflict is a normal phase of development rather than proof the team is broken. A team that has just formed, or just changed leader, or just absorbed three new members, may simply be storming on its way to performing. Judge the stage by observed behaviour rather than elapsed time, and match your leadership to it. Diagnosing dysfunction in a team that is developing normally is how leaders create the dysfunction they feared.
Watch forStorming can become a euphemism that buys patience for bullying, structural conflict or a wrong hire, all of which need intervention rather than time.
Org, people & execution
Belbin Team Roles
A vocabulary of nine behavioural roles that people tend to adopt in teams, grouped into thinking, action and people clusters, used as a checklist for whether a team's composition actually covers the work in front of it and where the gaps and duplications lie.
Some teams struggle because of how they were assembled, and no amount of trust work fixes a missing contribution. Belbin maps who genuinely covers the nine behavioural roles against the task in front of you. The gaps predict failure with useful precision: no Monitor Evaluator and bad ideas survive scrutiny, no Completer Finisher and the work ships at ninety per cent. The duplications predict friction, because two Shapers will fight for the wheel. I find this map most valuable when it exonerates people who were being blamed for a design fault.
Watch forRole labels harden into personality verdicts, and 'she is a Plant' said as identity closes down the very flexibility the model depends on.
Org, people & execution
GROW Model
A four-stage structure for a coaching conversation: agree the Goal, examine current Reality, generate Options, then secure the Will to act. It turns a manager's instinct to hand out answers into disciplined questions that leave ownership with the person being coached.
The diagnosis has to land somewhere, and it lands in conversations with individual people. GROW keeps those conversations honest. Your instinct, especially with a struggling team, will be to hand out answers, and handed-down answers do not stick. Agree the goal, spend proper time on reality, generate the options together, then secure a commitment with a date on it. The reality stage is where the value lives; most weak sessions spend two minutes there and twenty on solutions, then wonder why the solutions miss the real problem.
Watch forQuestions used as camouflage for instructions, the 'have you considered doing it my way?' variety, kill ownership quietly, and the coachee always notices.
In the end
By the end you should know which layer of the team is actually broken, whether you are watching a phase or a fault, whether the composition covers the work, and what each person has committed to doing by when. What the frameworks will not do is hold the line for you. Trust work starts with the leader going first, and the behaviours regress under pressure, so put the follow-up conversations in the diary before you close the first one. Teams are rarely fixed at the away-day; the fixing happens in the weeks afterwards, when nobody is watching.