A team personality assessment measures each person on a validated personality test, then combines the results into one picture of the team: which working styles are covered, which are missing, and where the group could split under stress. There's a free one below, and this page is the manual for using it well.
A team, mapped
This is a complete team personality assessment report, computed live in your browser by the same engine that builds real ones. Click through the five chapters; on the Goal Fit tab, change the objective and watch the reading change.
Take a minute with it before reading on. Most of what this page explains, you'll meet first as a chart up there: the working-styles map on Overview, the floor and spread readings on Dynamics, the role gaps on Roles, the discussion guide on Playbook. The next section walks each chapter in order.
Reading the map
Five chapters, each answering a question a team lead actually has.
One chart places every member by warmth (candid to warm) and social energy (reserved to outgoing). You see at a glance who drives and challenges, who steadies and supports, and who works best heads-down. Every position is a strength; the chart has no good corner.
Pick an objective, from shipping fast to stabilising quality, and the map scores how well the current mix supports it. The same team can be superb for one goal and thin for another, which is why this chapter exists. Try switching objectives on the sample above; the verdict moves.
Here's the part most tools get wrong. Averaging every trait assumes every trait works the same way in a group. The research says otherwise, so the map reads each trait its own way:
| Trait | What the map reports | Why |
|---|---|---|
| Conscientiousness | Team floor (the lowest member) | Deadlines are missed by the least structured member, not by the average. The floor is the honest number. [2][3] |
| Agreeableness | Team floor (the lowest member) | One persistently blunt or guarded member sets the tone in conflict. In field teams, the minimum carried more signal than the mean. [3] |
| Openness | Team average | Curiosity adds up. Teams with a higher average adapt better when the task changes under them. [3] |
| Emotional stability | Team average | Composure is roughly additive. The group’s general steadiness under pressure is what colleagues and clients feel. [2][3] |
| Extraversion | Team spread | A room of equally loud voices competes for the floor. Some spread is healthy: drivers and heads-down finishers need each other. [10] |
Dynamics also reads pairs: who works easily together, and which combinations deserve a little deliberate care. If one member sits far below the group on a floor trait, the chapter shows the number and leaves the judgement with you.
Nine classic team roles are assigned to the members best placed to hold them, based on traits. The strength of each trait-to-role link varies, so every assignment carries a confidence tier, from research-backed down to face-valid. Roles nobody naturally fills are listed as gaps. And if one person tops three or more roles, the map says the bench is thin rather than pretending the load is shared.
The last chapter turns the pattern into practice: operating norms tuned to this composition, a facilitator's discussion guide, and the team's motivation mix. It's the bridge from "interesting chart" to "different Tuesday", and the debrief agenda below is built to run with it open.
What it measures
Underneath every serious team assessment sits an individual instrument. Ours is a 60-question Big Five inventory in the tradition of the BFI-2, the modern research standard[1], scored against adult norms. Each person gets a score on five continuous traits: openness, conscientiousness, extraversion, agreeableness, and emotional stability. No types, no boxes; two colleagues who differ by one answer differ by one point, not by an identity.
The questions themselves are plain statements about everyday behaviour. You'll have an opinion on each within seconds:
"I keep my promises, even the small ones."
Disagree Agree
Reads conscientiousness: follow-through, structure, reliability.
"I take charge when a group needs direction."
Disagree Agree
Reads assertiveness, part of extraversion: who drives, who prefers to be consulted.
"Unexpected changes throw me for longer than I'd like."
Disagree Agree
Reads emotional stability: how pressure moves through a person, and then a room.
Measuring individuals is the easy half; anyone can take the free Big Five personality test and get their own profile. The hard half is combining five profiles into one honest team picture, because a team is not an average of its members. Four careful planners plus one chronic improviser don't make an "above-average" team. They make a team whose delivery floor is the improviser, and everyone already knows it. That's why the map reads each trait the way the composition research says to[2][3][4], floor for some, average for others, spread for one.
One boundary worth naming early. A team assessment is for an intact team understanding itself. It's not a hiring screen; selection has different rules and different stakes, and mixing the two ruins both. If you're here for yourself rather than a group, the work personality test is the individual version of the same instrument.
Personality also isn't the whole picture. The same library includes a motivation test, and teams often run the two together: the map shows how people work, the motivation profile shows what each person is working for, and the gap between those two answers is where most well-meant management misses.
Personality is continuous, like height. A type system draws a line through the middle of each distribution and calls the halves different species. People near a line, which is most people, can flip sides on a retest: between 39% and 76% of MBTI takers get a different four-letter type when they retake it, some within five weeks[15].
Types survive because they're memorable and kind, and that's worth something in conversation. But a team map has to add and compare scores, and you can't do arithmetic on nicknames. Measure with traits; chat with whatever labels your team enjoys.
The odds of a gap
Call someone a strong carrier of a trait if they'd land in the top fifth of adults on it. Now draw a team at random. The chance that nobody on the team is a strong carrier of any given trait falls as the team grows, but it falls slower than intuition expects:
26%
chance a random six-person team has no strong carrier of a given trait.
0.8⁶ = 0.26, assuming independent draws
78%
chance that, across all five traits, a six-person team is missing a strong carrier of at least one.
1 − (1 − 0.8⁶)⁵
>78%
the realistic figure: real teams are more alike than chance, because we hire people like us.
Attraction-selection-attrition[19]
These are the random-draw odds, and real teams do worse. Organisations attract, select, and keep people who resemble the people already there, so actual teams cluster more tightly than dice would[19]. The point isn't alarm. A gap is only a problem when it collides with the work, and plenty never do. The point is that "we're probably fine" is a guess with roughly one-in-five odds, on arithmetic alone, and checking takes eight minutes a head. What your team should do about a gap it does find is a question of what personality diversity actually buys, which cuts both ways.
Running it well
The test is the easy part. The difference between a team that gets something out of this and a team that rolls its eyes is decided before anyone answers a question.
Say what it is, what it isn't, and who sees what, before you send a single link. A version that works: "I'd like us to map how this team works: what styles we have covered, what we lean on too few people for. Everyone gets their own report and keeps it. The team map is the only shared artefact, and we'll read it together. Nothing about this touches reviews or pay." Then take the test first yourself, and say so.
For sceptics, show rather than argue: send the sample map above so people can see exactly what will exist about the group before agreeing to it. Most resistance to workplace tests is really resistance to being labelled or judged. Both concerns are legitimate, and both have answers: no trait on the map is bad, and the map reads the group, not any one person.
And keep it voluntary. A forced test yields careless answers and a poisoned debrief. In a team of eight, six honest profiles beat eight resentful ones every time.
The four ground rules
Consent. People take it knowingly, told what's shared and why. Ownership. Each member keeps their own report; sharing details is their choice. Dignity. No trait is bad, so the map has no bottom of the class. Purpose. The map informs how the team runs. The moment it becomes a lever against an individual, stop.
Distributed teams are, if anything, the better use case: personality friction that an office absorbs through hallway repair lands raw in Slack. The mechanics are easy, since the assessment is async by design: share the link, let people finish across time zones, and watch the map fill in. Run the debrief on a video call with the map screen-shared, and give remote voices the first word on each chapter, because the room always speaks first otherwise. For fully async teams, a written thread works: post the map, ask each person for one "this fits" and one "this overstates", then meet only to agree the norms.
Two people are enough to compute a map, three unlocks the full working-styles chart, and faultline detection needs four. The sweet spot is 5 to 15: enough people for real patterns, few enough that everyone fits in one conversation. Past about 20, map pods or departments separately; a 40-person map is a poster, not a mirror. Group-size research points the same direction: per-person effort shrinks as groups grow, in the classic experiments to 49% of solo capacity by eight people[14].
Traits are stable; rosters aren't. Re-run when membership changes, and refresh roughly yearly so the map matches the team that actually exists. Between runs, the map earns its keep as a reference: new conflict, new goal, new hire, same chart.
The debrief
A team personality assessment without a debrief is a horoscope with better methodology. This agenda is the one we'd run: timed, scripted where scripts help, and printable for the meeting itself. It works with our map or any test's results.
Team debrief agenda 45 minutes · everyone has taken the assessment · map on screen, Playbook chapter open
0:00 – 0:05
Name the purpose and the limits before anyone looks at anything. This is the sentence that decides whether the next 40 minutes feel safe.
"This map describes how we work, not how good we are. There's no best profile on it, nothing here touches reviews, and each of us is the final authority on our own result."0:05 – 0:15
Each person shares one thing their personal report got right and one thing it overstates. Starting with self-descriptions, including disagreements, establishes that the instrument is fallible and that people outrank charts. Keep it brisk: a minute each.
"What's one line yours nailed, and one it got a bit wrong?"0:15 – 0:25
Open the Overview chapter. Let people find themselves, then walk the group reading: who anchors which strength, and which styles the team has nobody covering. Name gaps as facts about the roster, not failures of anyone present.
"Where did the map put you, and does your neighbour agree?"0:25 – 0:35
Pick at most two patterns from Dynamics: a pair that clashes, a floor, a gap. For each, ask for one recent, concrete moment where it showed up. Concrete beats general; the goal is "ah, that Tuesday", not a theory of each other.
"When did we last feel this one? What did it cost us?"0:35 – 0:43
From the Playbook chapter, choose one or two operating norms that answer the frictions you just named. Each norm gets an owner and a review date. Two kept norms beat five aspirations.
"Which single change would make the pattern we named cheaper to live with?"0:43 – 0:45
One sentence each: something learned about a colleague, or something they'll do differently. End on people, not charts.
If the debrief surfaces a pattern worth working on properly, our guide to personality tests for team building turns each map pattern into a runnable exercise, and managing different personalities has scripts for the one-on-one conversations that follow. The norms you agree in the last ten minutes deserve a home: a team charter keeps them visible after the meeting ends. And if the map keeps surfacing friction, the free conflict management styles assessment shows each person how they argue under pressure, which is usually the missing half of the story.
Four common patterns
Worked examples: what the map shows, what it feels like from inside, and what to actually do. The trait grids are illustrative; your team will draw its own.
Pattern one
Everyone drives, nobody rides. Meetings are loud and fun and circular, because the room competes for airtime instead of building on it. The research is blunt here: groups where speaking turns spread evenly think better together, and problem-solving groups do best with some extraverts, not a room full of them. [6][10]
What to do: Put structure where volume used to be. Written proposals before discussion, a rotating chair, and explicit turn-taking in decisions. The quietest voice in this room is not the least valuable one; it is the least heard.
Pattern two
Five warm colleagues and one guarded one, and somehow every disagreement lands hard. That is the floor effect: in real work teams, how conflict goes tracks the least agreeable member more than the average. Experiments that planted one difficult member in small groups saw performance drop by 30 to 40 percent. [3][5]
What to do: Do not read the map at the person. A low floor is often a role mismatch, burnout, or a bad season, not a character verdict. Fix it with private conversation, clearer norms for how disagreement is voiced, and work that plays to the person’s strengths.
Pattern three
A team of explorers. Ideas everywhere, energy in every kickoff, and a graveyard of version 0.7s. Nobody here is lazy; the team simply has no natural finisher, so structure is a tax everyone resents paying. Spread matters too: mixing very diligent with very lax members correlates negatively with performance. [4]
What to do: Borrow the discipline you did not hire. Shared checklists, a definition of done, one rotating "closer" role per project. And when a seat opens, the map has already written the job spec.
Pattern four
No open conflict, but the same three people land on the same side of every question. That is a faultline: a dormant dividing line that costs nothing in calm weather and organises the team into camps the first time stakes rise. Reviews of the group research link aligned subgroups to more conflict and less cohesion. [11][12]
What to do: Mix across the line before stress arrives. Pair people from opposite sides on real work, rotate who presents, and give the whole team goals that only cross-line collaboration can hit.
Pair-level frictions get their own treatment in how two specific people are likely to work together, including a read you can do on your own when the colleague in question will not take a test.
The gap finder
Six questions about behaviour you've already observed. You'll get a working hypothesis about your team's most likely gap, and then, if you want the real answer, the assessment at the top measures it.
In your team’s meetings, who does the talking?
What the evidence says
The honest table. Direction, the number worth remembering, and a grade for how much to trust it: A for meta-analytic or replicated for a century, B for strong but narrower evidence, C for famous and contested.
| Factor | Direction | Evidence | The number to remember |
|---|---|---|---|
| Psychological safety | Helps | B One large internal program | Google’s strongest factor across 180 teams; who was on the team barely registered [18] |
| Keeping teams together | Helps | B Field studies | 19% fewer software defects when team familiarity rose 50%, across 1,015 project teams [13] |
| Floor on agreeableness | Helps | A Meta-analysis, 89 studies | The least agreeable member predicts team performance about as well as any composition score [3] |
| Average conscientiousness | Helps | A Meta-analysis | ρ = .20 with team performance; higher-average teams earn better ratings [3][4] |
| Even turn-taking | Helps | B Lab groups; influential, debated | Speaking-turn inequality correlated −.41 with a group’s measured collective intelligence [6][7] |
| Relationship conflict | Hurts | A Meta-analysis, 30 studies | ρ = −.22 with performance and −.54 with member satisfaction [8] |
| Task conflict | Depends | A Two meta-analyses disagree | Negative on average in 2003; near zero overall, and positive for senior teams, by 2012 [8][9] |
| Spread in conscientiousness | Hurts | A Meta-analysis | ρ = −.24: diligent-plus-lax mixes underperform evenly moderate teams [4] |
| Concentrating star talent | Depends | C Famous, contested | Hens bred from top individual layers pecked each other to dysfunction; group-selected flocks lifted output ~160% [16] |
| Adding more people | Costs | A A century of replications | Per-person effort fell to 49% of solo capacity in groups of eight [14] |
Two research traditions look like they disagree. Google's Project Aristotle studied 180 of its own teams and concluded that who was on the team mattered far less than how the team treated each other, with psychological safety the standout: its safest sales teams beat revenue targets by 17% while the least safe missed by up to 19%[18]. Meanwhile the peer-reviewed composition literature keeps finding that trait mixes do predict performance, modestly but consistently[3][4].
The reconciliation arrived in 2021. A reanalysis of 22 studies covering 1,356 groups found both effects, with process contributing about twice as much as member composition[7]. So: composition sets the odds, interaction decides the game. That's also the right way to hold a team map. It won't tell you whether people listen to each other on a bad day. It tells you where the listening will be hardest, which is exactly the layer Google found decisive, and exactly what a 45-minute debrief can move.
Numbers we deliberately didn't use
Team-building content leans on a few statistics that don't survive contact with their sources, so you won't find them on this page. The McKinsey "diverse companies outperform by 25/35/39%" figures: correlational, not peer-reviewed, and an independent replication on the S&P 500 found no significant effect. "Psychological safety makes teams 27% more productive": not in Google's published findings. "Communication is 93% nonverbal": a misreading of a narrow 1967 study its own author disowns. And the largest faultline meta-analysis (2011) was retracted in 2016, which is why our faultline claims cite the surviving 2012 review[12] and stay qualitative.
When it goes wrong
Most of the damage this tool category has done comes from four misuses, all avoidable and all common enough to name.
Typecasting. The map says someone anchors the finisher role, and within a month they're not invited to brainstorms. A description of tendency hardens into a job description. Antidote: roles on the map are patterns, not permissions, and the debrief should say so out loud.
The horoscope trap. People rate vague, flattering feedback as uncannily accurate; psychologists have measured it since 1949, when a class rated the same recycled newspaper-astrology profile 4.3 out of 5 as a personal description[17]. A good instrument fights this with specific, falsifiable statements, and a good debrief invites people to disagree with their own report. If nobody in your session pushed back on anything, the session was too polite to be useful.
Results as ammunition. "Well, the map says you're low on agreeableness" is the fast way to make sure nobody answers honestly again. The map describes water; it doesn't excuse splashing. Any use of a result against a person, in an argument or a review, breaks the tool permanently for the whole team.
Development data drifting into selection. A team-building result quietly consulted in a promotion decision moves the exercise into territory with real legal rules, where instruments face fairness and validity standards this use was never designed to meet. Keep the wall solid: team maps for the team, and if you need assessment for hiring, use a process built for selection, which is a different discipline with different guardrails.
The legal position, briefly: a standing team reflecting on how it works together isn't making an employment decision, so the demanding rules that govern selection testing don't attach. That's not legal advice, and it stops being true the moment results touch hiring, promotion, or termination. The four ground rules in Running it well are what keep the ethical bar higher than the legal one.
Choosing a framework
Five families you'll meet, described by what they're actually for. Any of them beats nothing; they're not interchangeable.
| Framework | What it measures | Where it shines | One honest caution |
|---|---|---|---|
| Big Five | Five continuous traits (openness, conscientiousness, extraversion, agreeableness, emotional stability) | Measurement. It is the model nearly all team-composition research is written in, so published findings actually apply. The free assessment on this page uses it. | Trait language is less catchy than type language. That is mostly the point. |
| DISC | Four communication styles (dominance, influence, steadiness, conscientiousness) | Fast shared vocabulary for talking about friction without it turning personal. A team can learn it in an afternoon. | Little published evidence links DISC composition to team performance. Use it as language, not as evidence about people. |
| MBTI | Sixteen types built from four either-or letters | Memorable, popular, and a gentle on-ramp to talking about differences at all. | Between 39% and 76% of people get a different type on retest, some within five weeks. Even its publisher advises against using it for selection. |
| Belbin team roles | Nine preferred team roles, from Plant to Completer Finisher | Role language for who-does-what conversations, which is often the conversation a team actually needs. | Role coverage is a discussion tool with mixed validation, not a measurement of traits. |
| CliftonStrengths | 34 talent themes, ranked per person | A positive vocabulary for individual strengths, backed by a large engagement research base. | Themes do not map onto the five traits the composition literature measures, so team-level findings do not transfer. |
These combine better than they compete. Plenty of teams measure with Big Five traits and still enjoy DISC or type vocabulary as shared slang, which works fine as long as everyone remembers which one is the measurement. For the deeper comparisons, see Belbin team roles vs the Big Five and the DISC assessment for team building guide.
Questions
A team personality assessment measures each member of a team on a validated personality test, then combines the individual profiles into one team-level picture. It shows which working styles the group has covered, where it runs thin, and which subgroups could drift apart. Done well, it uses continuous traits rather than type labels, and it combines each trait the way the research says to. The result is an input for better conversations, never a verdict on any person.
Good ones are useful; none are oracles. Well-built Big Five inventories are reliable on retest and predict real outcomes like job performance at modest, well-replicated levels. Type-based tests are weaker: many people get a different MBTI type when they retake it weeks later. Every self-report test also depends on honest answers. Treat scores as a good first draft of how someone works, then let the person edit it.
For measurement, yes. MBTI and DISC sort continuous traits into boxes, and the box edges are unstable: two nearly identical colleagues can land in different types. The research linking team composition to performance is written in Big Five terms, not type language. Type vocabularies still make friendly conversation starters. The practical compromise: measure with traits, and chat in whatever labels your team enjoys.
Two members are enough to compute a map. From three, you also get the full working-styles chart and a named team identity. Faultline detection switches on at four, because a subgroup needs at least two people on each side. The tool is built for teams of roughly 5 to 50. Past that, map departments or pods separately rather than one giant chart.
Each person receives their own full personal report, and that copy is theirs. The team map itself is a group artefact. It names who anchors which strength, so present it to the team together rather than reading it about them in private. Teams that share the map openly get the real benefit: a common language for differences that were already there.
Broadly, your traits shape where you naturally add the most: high-openness people tend toward exploring and challenging, high-conscientiousness people toward finishing and quality, warmer members toward keeping the group connected. The Roles chapter of the map assigns nine classic team roles to the members best placed to hold them. Take the free assessment on this page and the map will show you where you land.
It depends on the trait, which is why one blanket answer is always wrong. Being alike on conscientiousness and agreeableness helps: shared standards, less friction. Spread on extraversion helps: a team needs both drivers and finishers of conversations. On openness, the average matters more than the mix. So the useful question is not "are we diverse?" but "are we diverse in the places diversity pays?"
No. Make it voluntary and easy, and take it yourself first. A forced test produces careless answers and quiet resentment, which corrupts the map and the conversation it was meant to start. In practice, showing the sample report and explaining who sees what wins over most sceptics without pressure.
Run one 45-minute debrief while the results are fresh: reports first, map second, then agree one or two operating norms with an owner and a review date. The agenda on this page walks through it minute by minute. After that, revisit the map when something real changes: a new member, a new goal, a conflict you want to understand rather than referee.
Personality is stable, so the map changes when people change, not with moods or quarters. Re-run it when the roster shifts, and refresh it roughly yearly so newer members are included and the conversation stays current. Running it monthly measures nothing except your team’s patience.
Team development sits in a much lower-risk category than hiring, because no employment decision hangs on the result. The rules that govern selection procedures apply when a test screens candidates, not when an intact team reflects on how it works together. Ethically, the bar is transparency: tell people what is measured and why, let each person keep their own report, and never use the map to single anyone out. None of this is legal advice.
About 8 minutes per person: 60 questions in plain workplace language, on any phone or laptop. The map recomputes the moment each report lands. A team that starts after lunch is looking at its own map before the end of the day.
If your question is about culture rather than composition, start with the free culture fit test.
Keep reading
That's everything we know about doing this well. When you're ready, the free assessment at the top of the page takes a team name and gives you a link to share. Eight minutes a person, and the map is yours.
Methods & sources
The individual instrument is a 60-item Big Five inventory in the tradition of the BFI-2, the peer-reviewed modern standard whose domain scales show strong reliability (alpha .83 to .91) and 8-week retest stability (.76 to .84)[1]. Scores are computed against adult norms, in your browser. The team layer then combines members per construct: conscientiousness and agreeableness by team minimum, openness and emotional stability by team mean, extraversion by spread, following the composition literature that introduced and tested those operationalisations[2][3][4]. Subgroup detection is informed by faultline theory[11] and its surviving review literature[12].
Limits, stated plainly: team-composition effects are modest correlations, reported here as decision support, not destiny. Personality is one input among several. It informs how a team is likely to run; it never determines what a team or a person can do. Where the evidence is contested, the grade column above says so rather than rounding up.