Recognize and recover from stage regression

A team that was Performing can drop back to Storming — and the recovery move is different from the original ascent.

Why it works

Disruptive events — leadership change, strategy pivot, key departure, or merger — can invalidate the norms and trust that carried a team to Performing. The team isn’t broken; it’s re-entering Storming with different material. The leader’s job is to recognize the regression and apply the Storming tools again rather than forcing Performing behaviors the team no longer has the foundation for.

How to do it

1. After any significant disruption, explicitly check-in with the team: "Where are we on the development arc right now?"
2. Lower the autonomy expectation temporarily and provide more structure while the new norms form.
3. Run a mini-norming session to re-establish working agreements under the new conditions.

Evidence

Observations of team dynamics post-disruption consistently show regression in cohesion metrics and increased conflict, consistent with Tuckman’s own discussion of non-linear progression. (observational)

Regression evidence is largely observational and case-based; systematic studies of which events reliably cause regression are limited.

Common mistake

Treating regression as failure and applying blame — rather than recognizing it as a normal response to disruption that calls for deliberate re-norming.