Most lower-middle-market leadership teams I work with are stuck in Norming.
They don't know it. From the inside, Norming feels like success. The team has settled. The arguments have stopped. People have figured out how to work around each other. The leader looks at the calm and concludes that the team is healthy.
It isn't. It's just quiet. Norming is where most teams die because the path from Norming to Performing requires going back through Storming on purpose, and almost nobody does that voluntarily.
This post is how Tuckman's four stages and Edmondson's safety-accountability 2x2 combine in practice. I'll be specific about what the work looks like and why almost every leadership team I see needs the same intervention.
Tuckman's stages, briefly.
Bruce Tuckman published the four-stage model in 1965, looking at therapy groups, then expanded it across team types. The stages are not optional and they're not skippable. Every team that becomes high-performing passes through each one.
- Forming. Polite. Tentative. Everyone is figuring out what the team is and what their role is. Performance is low because nobody is sure what to do.
- Storming. The polite veneer cracks. People disagree. Roles get contested. Authority gets tested. Performance often dips because conflict consumes attention. This is the stage most teams try to skip.
- Norming. The team has settled. Roles are clear. Conflict has either been resolved or buried. Performance climbs because coordination overhead drops.
- Performing. The team operates as a high-trust unit. They surface problems early, dissent productively, and can self-correct without leader intervention. Performance is high and stable.
Tuckman later added a fifth stage, Adjourning, for project teams that disband. For ongoing operating teams, Performing is the destination.
Why most teams stop at Norming.
Norming feels like the goal because it feels stable. The pain of Storming has stopped. People are getting along. Decisions are getting made. From the leader's chair, this looks like a team that's working.
The trap: Norming is bought by suppressing conflict, not by resolving it. Most LMM teams arrive at Norming through one of three patterns:
- The dominant voice wins. One person, often the founder, settled the arguments by being louder or by being the boss. The team agreed by default. Underlying disagreements still exist; they just don't surface anymore.
- The team self-segregates. Functions stop interacting on contested topics. Sales does sales, ops does ops, the hand-off is mediated by tickets and emails because face-to-face conversation produces friction. Calm is bought by avoidance.
- The dissenters left. The people who would have kept storming got tired and quit. The remaining team is calm because everyone there has accepted the status quo.
None of these is Performing. All three look like it on the surface. The performance is a local maximum on top of suppressed information, and the moment the business hits a real challenge (a downturn, a major customer loss, a leadership change), the brittleness shows.
Edmondson's 2x2.
Amy Edmondson's framework gives us the diagnostic for whether a team's calm is real or suppressed. It's a 2x2: psychological safety on one axis, accountability on the other.
| Low accountability | High accountability | |
|---|---|---|
| High safety | Comfort zone | Learning zone (Performing) |
| Low safety | Apathy zone | Anxiety zone |
Norming-via-suppression usually puts a team in the Comfort zone (high safety, low accountability) or the Anxiety zone (low safety, high accountability), never the Learning zone. Comfort zone teams are pleasant to be on and produce mediocre output. Anxiety zone teams produce decent output for a while and then burn out or revolt.
Performing teams sit in the Learning zone. They have both. People speak up, including with bad news. People are accountable for their commitments. The combination is rare because most leaders think safety and accountability are opposites. They aren't.
What the intervention actually looks like.
Moving a team from Norming-via-suppression to Performing requires reopening the storms. Not all of them, and not all at once. The specific method we use inside the Stabilize and Document phases of an Axis Method engagement:
Week 1: Surface the suppressed disagreements.
1:1 interviews with every member of the leadership team. We ask one question across all of them: "What's a topic this team has stopped discussing?" The list is always long. By week two we've cataloged 8 to 15 buried disagreements that are quietly costing operational time.
Week 2 to 4: Restage one of them, deliberately.
We pick one buried disagreement, usually the highest-cost one, and put it on a meeting agenda explicitly. Not "let's revisit X," which the team will smooth over. Specifically: "I have heard from members of this team that we have a disagreement about X. We are going to discuss it and reach a decision." The principal, or us, runs the meeting.
The first time is uncomfortable. It will not feel productive. The point is not to resolve the disagreement in one meeting. The point is to demonstrate to the team that surfacing it does not get them punished, that the leader can hold the conflict without exploding, and that the meeting produces a real decision.
Week 4 to 8: Install the practices.
The behaviors that produce sustained safety, repeated in every leadership cadence:
- Public mistake-of-the-week from the principal in writing. Specific. Not performative. The team learns by example what acceptable disclosure looks like.
- "What did we learn" replaces "who screwed up" in incident reviews. Same questions, every incident, no exceptions.
- Devil's advocate role rotated weekly. One person assigned to argue against the dominant view in every leadership meeting.
- Calibrated leader reactions to first-instance bad news. We coach the principal explicitly in the first 30 days because the team is watching how leadership reacts and calibrating their future disclosure to that reaction.
Week 8 to 12: Add the accountability dimension.
Safety without accountability produces the Comfort zone, not the Learning zone. After safety practices are stable, we install the accountability discipline: explicit commitments at the close of every meeting, written, with owners and dates; a weekly review of last week's commitments before any new work is added; consequences for missed commitments that are visible and consistent (not punitive, but visible). Edmondson's distinction matters: accountability is about the work, not about the worker.
What "Performing" looks like in practice.
Three observable signals. None of them are "the team gets along."
- Bad news travels fast. When something breaks, the person responsible raises it within hours, not days. Often before leadership has noticed.
- Decisions stick. When the team decides X, X actually happens. Re-litigation drops to near zero. Disagreements get raised before the decision, not after.
- The team improves itself. Process changes, SOP updates, and small experiments come from line members, not from leadership memos. The team is in the Learning zone, which is the point.
If the team has all three, it's Performing. If it has none of them and is "calm," it's stuck in Norming via suppression and the operating system is not going to compound.
Why this is operational, not HR.
Most operators read this material and file it under "people stuff" and assume HR will handle it. Two problems with that.
First, HR rarely owns the leadership team. The principal does. Team-level interventions at the leadership level have to be driven by the leadership.
Second, this is not a soft skill. It's an operational lever. Psychological safety determines whether documented operating systems actually run. Without it, the SOPs are decoration. The fastest way to install operational excellence at the LMM scale is to fix the team-performance dimension first, because it gates every other improvement.
Tuckman tells you the path. Edmondson tells you the destination. The Axis Method is how you walk it without burning the team down on the way.
Keep reading.
- Replacing the SaaS Stack with $75/mo of Cloudflare, Most small operators run on $500–$3,000/month of SaaS that compounds with every new hire. …
- What We Cut in the First 90 Days, A typical $10M–$50M operator carries 30–40% operational waste. The first 90 days of an Axi…
- How to Read an Operational Waste Audit, Three numbers come out of the Diagnose phase of every fractional COO engagement. Most oper…
- Lean Six Sigma for the Lower-Middle Market, Without the BS, DMAIC, SIPOC, Black Belts, control charts, kaizen events. At enterprise scale these earn t…
Talk through it.
If any of this is applicable to where you are, book a scoping call. No pitch deck.