A team view that is a stack of individual profiles has described the members and not the team.
Why it matters when the plan changes
What a team can carry is a property of the group: what it covers between them, how the pieces fit, and whether something critical rests on one person. None of that is visible in a set of individual reports read in sequence, which is what most team assessment produces. Conflict style, per the Thomas-Kilmann Conflict Mode Instrument, sits on axes of assertiveness and cooperativeness, and the mix in a group shapes disagreement; separately, strategy execution research found only 9% of managers could rely on colleagues elsewhere in the organisation, showing a team's edges matter as much as its inside.
The tension is between the group view and the individual's privacy. A map of a team necessarily describes patterns that individuals contribute to, and in a small team those patterns can identify people. Keeping the map about the work and the arrangement, rather than about who is responsible for each pattern, is what makes it usable.
In practice
A leadership team of six receives a map describing where the group is strong, where its coverage is thin against the plan, and which pillar rests on one person. It names no individual as a problem. The conversation that follows is about redistributing two areas of work rather than about anyone's performance.
Evidence
Conflict styles sit on axes of assertiveness and cooperativeness, and the mix present shapes how a group handles disagreement.
Thomas-Kilmann Conflict Mode Instrument, Wikipedia (2026)Cross-unit commitments are the least reliable part of execution, which is what a team's interfaces with others determine.
Donald Sull, Rebecca Homkes and Charles Sull, Why Strategy Execution Unravels and What to Do About It, Harvard Business Review (2015)
What it cannot tell you
A Team Map describes a team against one plan at one point in time; it does not predict how the group will behave under a different plan, under new membership, or under sustained pressure. It is silent on causes outside the evidence case, such as reporting lines, incentives or history that shaped the patterns it observes.
How Atlas reads it
The Team Map is one of three evidence views drawn from a decision case, and it can be ordered without a workshop; doing so does not create another main package. Three scores per pillar sit behind it: coverage, complementarity and concentration.
Questions
The team as a unit: its dynamics, including conflict style as mapped by the Thomas-Kilmann Conflict Mode Instrument, where friction sits, what the members cover between them, how those strengths complement each other and where something critical rests on one person, all read against what the plan asks the team to deliver.
It describes patterns in the group rather than assessing each member. In a small team some patterns can be traced to people, which is why the map stays focused on the work and the arrangement. Individuals receive their own results separately.
Yes. A Team Map can be ordered on its own and does not create another main package. The Common Ground Session includes the underlying read and is never sold without it, so the relationship runs in that direction rather than the reverse.
Coverage asks whether the behaviour the plan needs is present at all; concentration asks whether it rests on one person. Complementarity asks whether pieces fit together, which matters given Harvard Business Review research finding only 9% of managers could rely on colleagues in other functions and units all the time.
Both are views of evidence inside one decision case. A Contribution Map covers a person against a role; a Team Map covers a group as a unit. Where the two appear to disagree, that difference is informative rather than an artefact, because both rest on the same evidence.