Comparing Maturity Across Teams Without Starting a Blame Game

Once an organisation has assessed one team or site, the next question is almost always: "How do the others compare?" It is a natural question. Differences between teams reveal where good practice exists, where support is needed and where the organisation is inconsistent.

But comparison has a dark side. Turn results into a league table and the lower-scoring teams become defensive, the higher-scoring teams become complacent, and everyone learns to manage their scores in future. The assessment stops telling the truth.

This article sets out how to compare maturity across teams in a way that encourages learning rather than blame.

Why comparison is valuable

Done well, comparing maturity helps an organisation:

• Find bright spots. A team doing something notably well often has practices others can adopt.
• Spot inconsistency. If one site follows a process carefully and another ignores it, customers and staff experience very different organisations.
• Target support. Limited improvement resources can be directed where they will make the biggest difference.
• Build shared standards. Seeing differences prompts a conversation about what the organisation's common standard should be.

Why it so often goes wrong

League tables

Publishing ranked scores invites people to treat maturity as a competition. The natural response is to protect your position, not to describe reality honestly.

Ignoring context

A team that recently merged, lost key staff or took on a difficult new service may score lower for reasons that have nothing to do with its competence. Comparing raw scores without context is unfair and misleading.

Different interpretations

Different teams may read the same question differently, or apply different standards of honesty. Some teams are naturally self-critical; others are optimistic. Without calibration, differences in scores may reflect differences in attitude rather than practice.

Linking scores to rewards

As soon as maturity scores affect budgets, bonuses or reputations, they will be inflated. This is one of the most reliable patterns in measurement.

Principles for fair comparison

1. Agree the purpose up front

Be explicit that the purpose is learning and support, not ranking. Say what the results will and will not be used for, and stick to it.

2. Use the same model and the same process

Every team should use the same assessment and similar conditions: a mix of roles answering independently, then discussing. Our guide to running a maturity assessment workshop describes a format that works well across teams.

3. Calibrate

Before comparing, bring a few people from different teams together to discuss a sample of questions. How did each team interpret them? What evidence did they use? Calibration sessions reduce differences caused by interpretation and build a shared understanding of what each level means.

4. Compare profiles, not totals

An overall score hides more than it reveals. Compare the shape of each team's profile: which areas are relatively strong or weak. Two teams with the same average may need completely different kinds of help.

5. Look at the spread within teams

Within each team, how much did individual answers vary? A team with a wide spread of views has a different issue, inconsistent practice or poor shared understanding, from a team where everyone agrees on a low score.

6. Present results with context

Show results alongside relevant context: team size, recent changes, the complexity of the work. Let each team explain its own results before conclusions are drawn.

7. Share practices, not rankings

The most useful output is not a chart showing who is ahead. It is a list of specific practices that work well somewhere and could be adopted elsewhere, and a list of shared weaknesses the organisation should address together.

Turning comparison into learning

A practical format:

1. Each team assesses itself and agrees its own priorities.
2. A cross-team session looks at anonymised or aggregated results to find common themes.
3. Bright-spot teams describe their practices, in their own words, to others.
4. The organisation agrees a few shared improvements, plus team-specific actions.
5. Teams pair up, so a team strong in one area supports another, and vice versa.

When people see that comparison leads to help rather than criticism, honesty improves in every subsequent round.

A note on quality and consistency

Consistency across teams is a central concern in quality management. Customers expect the same standard whichever team, site or shift serves them. Organisations at higher levels of quality maturity use comparisons between teams routinely to find and spread better practice, and to reduce variation.

The Quality Management assessment covers standards, process control and consistency, measurement, customer expectations, root cause analysis and continuous improvement culture. It works well as a common tool for comparing sites or teams that deliver similar services.

Frequently asked questions

Should we show teams each other's scores?

Share themes and practices widely. Share individual team scores only if teams have agreed to it and the culture is genuinely focused on learning. Anonymised comparisons are often a good starting point.

How do we handle a team that scores itself much higher than others think is fair?

Use calibration rather than confrontation. Ask the team to walk through the evidence behind its answers alongside another team. Differences in interpretation usually become clear quickly.

How often should we compare teams?

Annually is usually enough. More frequent comparisons tend to focus attention on scores rather than the improvements that change them.