Building Teams for ISO Certification: Why Structure Wins

Building teams for ISO certification is where most certification projects are quietly won or lost — long before the first internal audit. Leaders inherit a group that looks productive on paper and stalls in practice the moment the system work begins. Meetings run long. Document ownership is unclear. Two people quietly carry the QMS while everyone else waits to be told what to do. The diagnosis is rarely a talent problem. It is almost always a team-development problem — and once you can name the stage your team is in, you can lead it to the certification finish line.

There is a well-validated map for how groups become high-functioning teams. Bruce W. Tuckman's 1965 paper in Psychological Bulletin identified four developmental phases — forming, storming, norming, performing — after reviewing 50 studies of small groups. Twelve years later, Tuckman and Mary Ann Jensen added “adjourning” in Group & Organization Studies, completing the five stages of team development that leaders still use six decades on. That sequence is the foundation that organizations from Harvard Business Review to Google's Project Aristotle still point to when explaining why some teams perform and others stall.

MSI client experience suggests something the certification checklists rarely state plainly: building teams for ISO certification follows that same predictable arc — and the organizations that recognize the arc move through it faster. The reasons are mechanical, not magical. Nearly three decades of ISO consulting work points to the same conclusion from a different direction: the standard itself supplies most of the structure a developing team would otherwise have to invent. This guide walks through each stage, mapping every phase of team development to the specific certification work it unlocks.

The Framework

What Does Building Teams for ISO Certification Actually Require?

Name. Normalize. Navigate.

Building teams for ISO certification requires more than assigning a quality manager and hoping for the best. It requires moving a group through the five stages of team development — each defined by a recurring set of behaviors, and each calling for a different leadership posture. Skip the work of any stage and the gap shows up later, usually under audit pressure, usually expensively.

• Forming — orientation, polite caution, dependence on the leader. The team needs to learn what the management system asks of each role.
• Storming — competing views on how to document, who owns what, and how strict the system should be.
• Norming — emerging agreements, shared standards, documented working procedures the QMS can rely on.
• Performing — distributed ownership, mutual accountability, a system that runs without the leader in the room.
• Adjourning — closure on the certification project, lessons captured into management review, transition to maintenance.

Two misconceptions trip up leaders building teams for ISO certification. First, the stages are not optional. A team that appears to “skip” storming is usually suppressing disagreement about how the system should work — and that suppressed conflict resurfaces during the audit. Second, the stages are not strictly linear. A new hire, a scope change, or a registrar's findings can pull a team back into an earlier stage, and that is normal.

For organizations pursuing certification, this is operational, not theoretical. ISO 9001 Clause 5 requires top management to demonstrate leadership and commitment. Clause 7.1.2 requires the organization to determine and provide the people it needs. Clause 7.2 requires competence. ISO went further and published a dedicated guidance document on the subject: ISO 10018:2020, Quality management — Guidance for people engagement, which addresses how to involve people in a quality management system and build their competence within it. None of those requirements are abstract — they describe a team that actually functions, which is exactly what building teams for ISO certification produces.

The Stalling Problem

Why Certification Teams Stall — and What ISO-Aligned Leaders Do Differently

Diagnose. Decide. Deliver.

Organizations typically report that the difference between a certification project that lands on schedule and one that drags comes down to whether anyone names what is happening inside the team. Building teams for ISO certification gives leaders a vocabulary. Without it, storming gets misread as “the wrong people,” forming gets misread as “low buy-in,” and norming gets misread as “we're done” — when none of those are true.

In MSI's 28 years of supporting 80+ certifications and attending 200+ audits, a consistent pattern shows up. Organizations that ran into people problems on the way to certification almost always had unresolved storming-stage conflict that no one had named. Organizations that certified cleanly almost always had documented roles, defined processes, and management reviews that surfaced disagreements before they hardened. Building teams for ISO certification does not remove the stages of development — it makes them legible and leadable.

Three structural factors slow certification teams regardless of talent: ambiguous roles, unclear decision rights, and absent feedback loops. Each maps to a specific clause family in ISO 9001 and its sister standards — and addressing those clauses well is, in practice, the act of building teams for ISO certification. That is not a coincidence; it is why the standard works. MSI's treatment of organizational context and structure is where that role-clarity work usually begins, and MSI's decoder ring for the five standards explains why the same team pattern repeats whether the system is quality, environment, safety, devices, or healthcare.

Stage One

Stage 1: Forming — Setting the Foundation for Building Teams for ISO Certification

Orient. Onboard. Anchor.

Forming is the orientation phase. Members are polite, cautious, and reliant on the leader for direction. They are privately answering three questions: What's expected of me in this system? Who are these other people? Is it safe to be honest here? Until those questions are answered, the documentation work that certification depends on moves slowly. This is the first real test of building teams for ISO certification.

What forming looks like in a certification project

Surface-level agreement dominates. Questions about who owns which procedure go to the leader rather than across the room. Meetings end with ambiguous next steps and undocumented owners. None of this is dysfunction — it is the predictable signature of stage one in building teams for ISO certification.

Five leadership moves that compress the forming stage

1. Document roles in writing. Vague roles are the single largest accelerant of confusion. A one-page responsibilities document — what you own in the QMS, what you contribute to, what you escalate — does more than any team-building exercise. MSI's vision, values, and mission alignment work typically produces those documents, and MSI's human resource management procedure analysis explains why competence and role definition cut across every function rather than living inside HR.
2. Set communication norms early. Which channel for which decision, response-time expectations, meeting cadence. Document it. Review it monthly.
3. Engineer an early win. Pick one procedure, scope it tightly, document it inside two weeks. Forming teams need evidence that this group can produce audit-ready work together.
4. Model considered vulnerability. A leader sharing a real past mistake does more for psychological safety than any charter exercise. Amy Edmondson's research is unambiguous on this, and MSI's work on psychological safety at work shows how quickly it erodes when an organization is under structural stress.
5. Hold individual check-ins inside the first 30 days. Group dynamics in forming are unreliable signal. One-to-one conversations reveal what the team actually thinks about the certification effort.

For organizations moving toward certification, the forming stage maps directly to onboarding and competence requirements. Building teams for ISO certification at this stage is less about the documents being magical and more about the act of writing them forcing a clarity that ambient conversation never delivers.

Stage Two

Stage 2: Storming — Turning Conflict Into Certification Progress

Surface. Sort. Settle.

Storming is where the polite veneer cracks. Members start expressing real opinions about how strict the system should be, who owns which process, and whether the documentation is worth the effort — not because something has gone wrong, but because trust has finally reached the threshold where disagreement feels survivable. Of all the stages in building teams for ISO certification, storming is the most likely to be misread as a hiring mistake.

Recognizing storming behaviors

Open disagreement in meetings. Subgroups forming around “keep it lean” versus “document everything.” Questioning of the overall certification approach. These are not warning signs; they are progress signals — provided leadership engages rather than suppresses.

Four moves that turn storming into structural strength

1. Name the stage out loud. “What we're feeling is normal — it's what teams that are about to perform well go through.” This reframing gives the team permission to disagree productively about the system.
2. Move from positions to interests. Ask what problem the documentation is actually solving and what success looks like for each person. Positions are what people say they want; interests are why. Storming dissolves when the conversation moves down a layer.
3. Teach the vocabulary of constructive conflict. “Help me understand your thinking.” “Here's where I disagree, and why.” These phrases are load-bearing when building teams for ISO certification.
4. Know when to step in versus step back. Disagreements about process and documentation belong to the team. Personal attacks or breaches of psychological safety belong to the leader — immediately.

In a certification context, storming is where most management systems either earn their keep or expose their gaps. A team in storming with a working management review procedure can route the disagreement into the system. This is also where risk culture shows itself: teams that treat risk discussions as blame conversations stall in storming; teams that treat them as forward-looking decisions move through. Prolonged, unresolved storming is also one of the quieter drivers of attrition — MSI's analysis of how to reduce employee turnover traces the same pattern from the retention side.

Stage Three

Stage 3: Norming — Cohesion and Documented Agreements

Align. Agree. Anchor.

Norming is where the team consolidates the agreements that storming surfaced. Decisions accelerate because the underlying questions — who decides, with whose input, against which criteria — have been worked through. In the arc of building teams for ISO certification, norming is the quiet stage that makes the loud stage (performing) possible, and it is where the QMS documentation starts to write itself.

Signs your certification team has reached norming

• Meetings get shorter, not longer, when the agenda is full.
• Disagreements are aired and resolved inside the meeting, not litigated afterward.
• Process ownership is named openly: “ask her, that's her procedure.”
• The team starts using “we” more than “I” about the system.

The single most valuable move in norming is writing the working agreements down — not as rigid rules, but as living documentation of how this team decides, communicates, and handles disagreement. MSI's seven-step quality improvement culture sequence follows the same logic: surface, decide, document, review. When building teams for ISO certification, the agreements that come out of resolved storming-stage conflict are the ones that survive the audit.

Three categories of working agreement consistently pay off: decision rights (who decides what, with whose input, by when), communication response expectations, and a conflict resolution process. Norming inside a certifying organization has a bonus: the documented agreements often satisfy clause requirements without anyone needing to “write for the auditor.” ISO 9001 Clause 7.4 requires determined internal and external communications. A norming-stage team has already done that work in human terms; translating it to the QMS is editing, not authoring — a distinction MSI unpacks in its guide to what makes an ISO procedure actually effective.

This is also the stage where most certification teams lose the most time. Not because the agreements are hard to reach, but because turning them into documented procedures means making dozens of small judgment calls — what to measure, where the decision points sit, which records prove the process ran — with nothing to work from but a blank page and a clause number.

Stage Four

Stage 4: Performing — The Peak of Building Teams for ISO Certification

Trust. Translate. Transcend.

Performing is the stage organizations brag about and few teams reach. Google's Project Aristotle studied 180 teams and concluded that high performance correlates most strongly with psychological safety — exactly the conditions the prior three stages, done well, produce. A performing certification team handles complexity that would fracture a less-developed team, makes decisions at the right level, and recovers quickly from registrar findings.

What performing looks like in a certified system

• Distributed decision-making. Process owners decide within their scope without escalating routine items.
• Real-time feedback. Nonconformities get raised when they're small, not after they've compounded.
• Flexibility under change. Scope shifts and resource constraints get absorbed without weeks of churn.
• Standards held in the leader's absence. The most reliable test of all — and what a surveillance audit actually measures.

Three moves that keep a certification team performing

1. Calibrate the challenge. Boredom is a quieter failure mode than overload, and it is the one most performing teams fall into once the certificate is on the wall. Raise the standard periodically — a tougher internal audit scope, a stretch objective — in conversation with the team, not by surprise.
2. Refresh perspective. Bring in outside expertise, rotate audit assignments, build cross-functional exposure. Performing teams stagnate when they stop encountering ideas they did not already hold, and a stale team is where surveillance findings quietly accumulate.
3. Connect work to consequence. A team that sees specifically how its quality system protects customers and the business sustains motivation through the dry months between audits. This is the difference between a system that is maintained and one that is merely survived.

These three moves are what separate a team that earns certification once from a team that holds it for years — and they are the part of building teams for ISO certification that begins, rather than ends, at the audit. MSI's work on leadership tenacity makes the case that persistence is a property of the system a leader builds, not a trait they happen to have.

The largest risk at performing is complacency. Teams at the top of their game stop noticing the small drift that, two quarters later, has them solving last year's problems. The discipline of structured management review — required under every ISO standard MSI implements — is the institutional counterweight, and it is the reason SureResults exists as a year-round program rather than a pre-audit scramble. The top five ISO maintenance risks almost all trace back to complacent performing-stage teams, and MSI's broader piece on what an ISO audit actually tests explains why the surveillance cycle finds them. This is also why ISO 9001:2026's emphasis on ethics and quality culture matters — performing teams want to be part of work that means something.

Stage Five

Stage 5: Adjourning — Closing the Certification Project the Right Way

Reflect. Recognize. Release.

Adjourning — sometimes called “mourning” — was the fifth stage Tuckman and Jensen added in 1977. In a certification context it accounts for what happens when the implementation project ends and the system transitions to maintenance. Many leaders skip this stage. Skipping it is one of the more expensive shortcuts in building teams for ISO certification.

What proper adjourning captures

• Lessons learned — what worked in the certification push, what didn't, captured while memories are accurate.
• Process artifacts — templates, checklists, and procedures that worked, ready for the next surveillance cycle.
• Acknowledgment — public, specific recognition of what each member contributed to certification.

For certified organizations, adjourning is the moment that feeds management review with real input. The “lessons learned from completed projects” line in your management review minutes is exactly this work, done well. Skip adjourning and your reviews drift toward status updates — which auditors notice. Treating each transition as adjourning-and-re-forming protects the team's progress through the earlier stages of building teams for ISO certification from being silently reset.

Regression and Recovery

When Certification Teams Regress — and How to Recover

Notice. Name. Navigate.

No team holds performing forever. Building teams for ISO certification describes a dominant pattern, not a permanent state. Three triggers reliably pull teams backward: membership change (a new hire resets parts of the team to forming), organizational change (a restructure can drop a performing team back into storming), and pressure spike (a recertification deadline exposes ambiguities the team had been quietly accommodating). MSI's playbook for supporting teams during crisis is the companion piece for leaders walking a team through a trigger in real time.

The recovery sequence is short: acknowledge the regression to the team without shame, temporarily raise structure (shorten feedback loops, restate decision rights), and rebuild connection deliberately. Organizations typically report that documented teams recover from regression noticeably faster than undocumented ones — because when the working agreements are written, the team has a baseline to return to. That is one of the quieter benefits of building teams for ISO certification inside a real management system.

Distributed Teams

Building Teams for ISO Certification Across Remote and Hybrid Sites

Connect. Codify. Continue.

Distributed teams move through the same stages, but the timing differs and the failure modes are sharper. The informal moments that quietly do forming and norming work in an office have to be engineered deliberately when building teams for ISO certification across sites. Forming takes longer because human cues are degraded over video; storming gets suppressed because typed disagreement reads sharper than spoken; norming needs deliberate codification because distributed teams don't accidentally accumulate shared habits.

Five practical adaptations hold up well: video on during forming, scheduled unstructured time, over-documenting decisions and owners, asynchronous-first for routine work but synchronous for the hard conversations, and recognition delivered in public channels. For organizations that run internal audits remotely — increasingly common — the same logic applies: distributed audit teams pass through every stage on each multi-site engagement, and leaders who name the stages out loud get cleaner audits with less retread.

The auditing guidance itself has caught up to this. ISO 19011:2026, published in May 2026, expanded its treatment of remote auditing methods and virtual locations, and raised the expectation that auditors be competent in the specific platforms they use. MSI's breakdown of the six essential edits to your internal audit procedure walks through what a distributed certification team needs to change before its next audit cycle.

Certifying to a Current Edition

Building Teams for ISO Certification When the Standard Just Changed

Current. Correct. Certified.

One variable reshapes a certification project more than team maturity does: whether the standard you are certifying to is the current edition. A team that spends four months documenting to a superseded edition has done forming, storming, and norming perfectly and produced the wrong artifact.

ISO 14001 is the live example. ISO 14001:2026 was published on April 15, 2026, and the 2015 edition is withdrawn. Any organization starting an environmental certification project today is building to the 2026 edition from day one — not transitioning to it later. The changes are real but contained: a new planning-and-managing-of-changes requirement, a broader environmental-conditions view of context that reaches past climate into biodiversity and resource availability, a strengthened life-cycle perspective, and operational control extended from outsourced processes to externally provided processes, products, and services. ISO's own summary of what changed in the 2026 edition is the primary reference.

For a team in the norming stage, this is a timing question with real money attached. The documented agreements are being written now. Written against the current edition, they carry the team to the certificate. Written against the withdrawn one, they become rework — and rework during norming is the fastest way to knock a team back into storming. MSI's essential guide to ISO 14001 certification covers the wider implementation picture, and organizations that already run environmental programs without calling them a management system should start with MSI's work on mapping an existing sustainability program to ISO 14001.

The same timing logic applies across the portfolio. ISO 19011 was revised in 2026, ISO 9001's next edition is in ballot, and MSI's overview of what the 2026 revisions mean for certification strategy maps which decisions can wait and which cannot.

The ISO Multiplier

How ISO Clauses Do the Work of Building Teams for ISO Certification

Document. Define. Deliver.

This is the part most team-development articles miss. The stages of development are about human behavior. Management systems — ISO 9001, ISO 13485, ISO 14001, ISO 45001, ISO 7101 — are about repeatable structure. They are not in tension. Building teams for ISO certification works precisely because the clauses supply the structural answers that early-stage teams would otherwise have to invent under pressure.

• Clause 4 (Context). Forces the organization to articulate who it serves and which stakeholders matter — forming-stage work at enterprise level. See organizational context and structure.
• Clause 5 (Leadership). Requires top management to take accountability. Storming-stage authority questions get an answer because the standard names who is accountable. See quality improvement culture, step by step.
• Clause 6 (Planning). Documents objectives and risks. Norming-stage agreements about direction get formalized.
• Clause 7 (Support — competence, awareness, communication). Defines who needs what skills and how communication flows. This is norming-stage codification by design.
• Clause 9 (Performance evaluation and management review). Provides the institutional rhythm that catches performing-stage drift before it becomes regression.
• Clause 10 (Improvement). Captures the adjourning-stage lessons-learned discipline in repeatable form.

Because those clause families are shared across standards under the harmonized structure, a team that learns them once can carry them into every system the organization runs — the argument behind integrated management systems. Across MSI's 28 years of work — 80+ certifications supported, 200+ audits attended, and 600+ professionals trained — the pattern is consistent: organizations that treat ISO as paperwork get neither great audits nor great teams. Organizations that treat the clauses as scaffolding for how real teams operate get both. This is especially visible in healthcare, where ISO 7101:2023 explicitly addresses workforce wellbeing and leadership engagement; MSI's coverage of ISO 7101 in practice explores it further. The same logic appears in ISO 45001, where worker participation is a clause requirement, not a slogan, and in ISO 13485 for medical-device teams.

One structural point is worth naming for teams new to this: the certificate at the end of the project is only meaningful because the certification body issuing it is itself accredited. Global ACI now provides the international accreditation framework that IAF and ILAC previously carried, and in the United States ANAB is the accreditation body most certification bodies work under. A team that understands why accreditation exists tends to take the internal audit program more seriously — a point reinforced by broader performance frameworks like the Baldrige Performance Excellence Program, which treats workforce engagement as a scored category rather than a soft one. For wider workforce research, Gallup's State of the Global Workplace, MIT Sloan's research on great teamwork, ASQ's teams resources, and SHRM's guidance on managing the stages of team development all reinforce the same conclusions.

For leaders weighing certification for the first time, this is the case the cost-benefit spreadsheets miss. The certificate is the visible artifact; the team that makes it sustainable is the actual asset — an argument MSI develops further in its piece on why ISO certification matters as a leadership decision. MSI's companion pieces on team building and hiring excellence and building team expertise in three steps, together with the role-aligned LearningPaths by MSI program, are all built for keeping that competence consistent across changing teams. For executives still deciding whether to certify at all, the ISO Executive Decision Briefs lay out the business case.

Implementation Readiness

How Ready Is Your Team to Lead the Implementation?

Structure. Align. Sustain.

The five stages tell you where your team is. They do not tell you whether it can carry an implementation — that depends on how well it handles the specific responsibilities the standard places on leadership: clear roles, shared objectives, honest communication, and follow-through. Two teams at the very same stage can be worlds apart on those, which is why building teams for ISO certification starts with measurement rather than assumption.

The gap usually hides in plain sight — a process owner no one formally named, an objective two managers quietly interpret differently — until it stalls the project weeks in. The fastest way to see it is to measure it before you begin.

• Eight dimensions mapped to the standard — the leadership, roles, planning, competence, communication, accountability, and improvement responsibilities built into ISO's harmonized structure.
• A maturity level you can act on — from forming to high-performing, so you know exactly where the team stands before kickoff.
• It surfaces quiet disagreement — where members privately read the team's readiness very differently, before it becomes a mid-project surprise.
• One tool for any standard — built on the structure shared by ISO 9001, ISO 14001, ISO 13485, and ISO 45001.
• Focused on a system that performs in practice — not just one that looks complete on paper.

Frequently Asked Questions

FAQs on Building Teams for ISO Certification

Ask. Answer. Apply.

How long does building teams for ISO certification typically take?

Can a certification team skip the storming stage?

What if our certification team is stuck in storming?

Who should be on a team built for ISO certification?

Which edition of the standard should a new certification team document to?

How do you keep a certification team aligned when members keep changing?

Your Next Move

From Building the Team to Earning the Certificate

Assess. Align. Advance.

Building teams for ISO certification is not a model you implement; it is a sequence you recognize and lead. Diagnose the stage your team is actually in, pick two leadership moves that fit it, run them for thirty days, and document the agreements that emerge. When you are ready to turn that team into a certified management system, the next step is a structured kickoff — or a turnkey route like SurePath if the team needs the whole system built alongside them.

Continue Reading

Related MSI Resources on Teams, Culture, and ISO Leadership