Most leaders experience conflict inside a new team as a problem to be shut down rather than a stage to be recognised, which is exactly the mistake Bruce Tuckman's model was built to correct. Tuckman (1965) proposed that small groups move through a predictable developmental sequence: forming, when members are polite, uncertain of their roles, and dependent on a leader for direction; storming, when that politeness breaks down as real differences over roles, approach and authority surface, often as open friction; norming, when the group works out enough shared expectation and trust to resolve those differences without a referee; and performing, when the team can direct its own energy at the task rather than at itself. Tuckman's own later review of the literature with Mary Ann Jensen added a fifth stage, adjourning, covering the deliberate disbanding of a team once its task is complete and the mix of relief and loss that can come with it (Tuckman and Jensen, 1977). The model's most practically useful claim is the one leaders most often ignore under pressure: storming is not a sign that team-building has failed, but a stage every real team is expected to pass through on the way to performing.

Tuckman's sequence assumes stages unfold roughly in order as a team matures, but Connie Gersick's (1988) study of eight project groups found something stranger and, for anyone managing a team against a deadline, more useful. Rather than progressing steadily, the groups Gersick observed spent long stretches in a stable pattern of behaviour — an equilibrium — then underwent a sudden, concentrated burst of change that reset their whole approach to the task, a pattern she called punctuated equilibrium. The trigger for that burst was rarely the completion of a developmental stage; it was far more often the group's own growing awareness of time, with the project's temporal midpoint acting as a kind of alarm that the current approach needed to change before the deadline arrived. The two models are not rivals to pick between but different lenses on the same reality: Tuckman names what a particular period of friction is (a normal stage, not a crisis), while Gersick explains why it so often arrives in a sudden burst rather than building gradually, and specifically why the middle of a project is a more likely moment for it than the start.

Diagnosing a team's stage is only useful if it changes what a leader actually does next, and John Maxwell's The 17 Indisputable Laws of Teamwork (2001) names several of the specific behaviours that move a team through a difficult one. The Law of the Niche holds that "all players have a place where they add the most value" (Maxwell, 2001) — a leader's job during friction is often less about resolving a personality clash and more about checking whether people are actually placed where their contribution counts, since misplacement produces exactly the kind of frustration that gets mistaken for a conflict between people rather than a mismatch of role. The Law of the Big Picture states that "the goal is more important than the role" (Maxwell, 2001): re-anchoring a storming team in the shared goal, rather than relitigating whose role is whose, gives people a reason to stop defending territory. The Law of Significance — "one is too small a number to achieve greatness" (Maxwell, 2001) — is a direct challenge to the leader who absorbs credit or carries a disproportionate share of the hardest work alone, both of which quietly teach a team that its performance depends on one person rather than on itself.

A second, more mundane leadership behaviour sits underneath all three laws: how a team actually runs its meetings, which is where most of its collective attention gets spent. Leach et al.'s (2009) survey of 980 employees about their most recent meeting found that perceived effectiveness tracked specific, checkable design characteristics — principally whether the meeting had a clear agenda, whether the facilities and logistics worked, and whether it started and ended on time — rather than anything mysterious about who was in the room. Rogelberg's (2019) broader meeting-science research makes the stakes concrete: organisations routinely devote a sizeable share of their payroll to time spent in meetings, and fewer, smaller, better-designed ones tend to improve both productivity and how people feel about their work, not just satisfaction with the meeting itself. A leader moving a team out of storming gains more from running fewer, purpose-led meetings that end with named actions than from scheduling an extra meeting to "talk it through."

A leader's default response to someone who seems stuck is to tell them what to do, which solves the immediate problem but leaves them no more capable of solving the next one themselves. The GROW model offers a deliberate alternative: a four-part structure — Goal, Reality, Options, Will (or Way Forward) — for a conversation that helps someone build their own solution rather than receiving the leader's. GROW was developed in the UK during the 1980s by the business coaches Graham Alexander and Alan Fine working alongside Sir John Whitmore, drawing on Timothy Gallwey's "inner game" coaching method from sport, and it was Whitmore who first set the model out in print, in Coaching for Performance (1992) — crediting the model to Whitmore alone, as is common in casual use, erases the two collaborators whose work shaped it from the start.

Each stage asks a different kind of question. Goal establishes what the person is actually trying to achieve in this conversation, stated in their own words rather than assumed by the coach. Reality asks what is actually happening now, without the coach supplying the diagnosis. Options opens up what the person could do, deliberately before judging any option's merit, so the list is genuinely theirs rather than the coach's shortlist dressed up as a question. Will — sometimes rendered "Way Forward" — commits to a specific next action and a way of checking it happened. The structure's value is also its limit: GROW works well for someone who is motivated but stuck, less well for someone who is missing a skill no amount of reflection will supply, and not at all as a way of avoiding a direct conversation about a performance problem that actually needs direct feedback rather than a question.

Tuckman and Gersick both assume a team gets the chance to recover from friction; resilience is what actually determines whether it does. Sarkar and Fletcher's (2014) review of psychological resilience in elite sport performers identified five families of protective psychological factor that buffer individuals against the negative effects of stress: a positive personality, strong motivation, confidence, the ability to focus, and perceived social support. The research is drawn from sport, not from business teams under a change programme, and that context matters — the mechanism Sarkar and Fletcher describe, specific psychological factors moderating how stress affects performance, generalises more confidently than the exact five labels transfer untested into a logistics depot or a project squad, and a leader should treat the parallel as a useful frame rather than a proven, like-for-like fit.

What the sport-performer research does not settle is where those protective factors actually come from in a team setting, and here the distinction between individual and team resilience matters most. An individually resilient person dropped into a team with an unsustainable workload, no visible support and a habit of assigning blame after every setback will still struggle, because resilience is not purely a personal trait a leader can select for — it is also a property of the environment a team works in. A team culture that processes setbacks without blame, keeps workload sustainable rather than reliant on heroics, and makes support visibly available and actually used, rather than merely offered, does more to sustain performance through a demanding programme than any amount of individual grit, however well-evidenced that grit is in a different context.