How to Manage Different Personalities on a Team
The hermit, the steamroller, the perfectionist, the firefighter. Every manager eventually inherits all four. A Big Five guide to what each pattern actually is, the move that works, and the move that quietly makes it worse.
Built on the Big Five · each person keeps their own report · free to start
Every manager runs the same private museum. There's the engineer who hasn't spoken in stand-up since March but whose design docs read like literature. The account lead who wins every argument, including the ones that didn't need winning. The analyst whose reports are flawless and eleven days late. The operations hire who was magnificent during the outage and has ignored the incident checklist ever since. You've been told to treat everyone the same, and you've noticed that treating these four the same fails all of them at once.
Here's the reframe this guide is built on: none of these people is a problem to fix. Each is a stable, readable pattern of traits meeting an environment that wasn't designed with them in mind. Patterns can be measured, and design can change. The four cases below map the classic "difficult colleague" onto Big Five profiles, and for each one gives you what it looks like, what it isn't, one move that works, and one that backfires. The measurement layer underneath is covered in our guide to the team personality assessment; this page is the craft.
First, a compass: the Big Five in one minute
The Big Five is the personality model that survived a century of psychometric argument: five continuous dimensions, each scored against population norms, each stable enough over the years to plan around. Openness is the appetite for the new versus the proven. Conscientiousness is the relationship to structure, standards and finishing. Extraversion is where energy comes from and how much of the room a person naturally fills. Agreeableness is the default in friction: accommodate or challenge. Emotional Stability is the size of the gap between a hard week and a crisis.
Two rules keep the model honest in a manager's hands. Neither pole of any trait is the good one; every position pays for its strengths somewhere, which is why each pattern below is written with respect. And a profile describes tendencies, never destiny; it tells you someone's defaults, and defaults flex when the environment makes flexing cheap. If you've never seen your own numbers, the free Big Five personality test takes eight minutes and will make the four portraits below considerably more vivid.
The brilliant hermit
Low Extraversion, high Openness
What it looks like. They're your deepest thinker and your quietest presence. In meetings they say nothing for forty minutes, then drop one sentence that reframes the whole problem, or more often say nothing at all and send the reframe by message at 9pm. Their written work is where the brilliance lives: careful, original, strange in the productive way. They decline the team lunch, again. New joiners assume they're unhappy. They're usually the most contented person on the team; they're just spending their energy where it compounds.
What it is not. Disengagement, arrogance, or a development gap called "visibility". Low Extraversion is a metabolism, a preference for depth over breadth of stimulation, and paired with high Openness it's the profile of people who do their best thinking alone and their worst thinking on the spot. Reading their silence as absence is the single most common way managers waste this person.
The move that works. Shift the arena to writing. Send the agenda and the hard question the day before; invite a written first take before any group discussion; let their document open the meeting instead of their voice. In the room, make one deliberate pass: "Sam, you've seen this shape before, what are we missing?" One genuine invitation beats ten "any thoughts?". And protect their calendar the way you'd protect a budget, because for this profile, three scattered meetings genuinely cost an afternoon of their best work.
The move that backfires. Prescribing performance: pushing them to "speak up more", making them brainstorm out loud, praising them theatrically in the all-hands to draw them out. Each of these takes the environment where they're weakest and raises the stakes in it. They'll comply for a quarter, drain, and start interviewing elsewhere, quietly, which is the only way they do anything.
The steamroller
High Extraversion, low Agreeableness under pressure
What it looks like. They arrive with momentum and opinions, usually good ones. They talk first and longest, interrupt with better versions of other people's sentences, and treat every decision as a contest that improves the decision, which, annoyingly, it often does. Under deadline pressure the style sharpens: the challenge gets blunter, the interruptions faster, and the two quietest people on the team stop offering ideas entirely. Results follow them around. So does a certain weather.
What it is not. Malice, ego, or contempt for colleagues. High assertiveness plus low accommodation is the profile of someone who shows respect by engaging hard with your content and expects the same in return; the aggression you're reading is, from inside, rigour. Felps and colleagues' bad-apple research is worth knowing here for its boundary: the damage pattern belongs to persistent interpersonal defection, and a challenging colleague with high standards is a different animal from a withholding one. Most steamrollers are the first kind wearing the second kind's reputation.
The move that works. Give the force a jurisdiction. Name who owns which decisions before work starts, so driving energy has lanes; give them the official red-team role on plans that need stress-testing, so the challenge lands where it's wanted; and contract privately about the room: "when you interrupt Maya, I lose her for the meeting; hold it for the last ten minutes and you'll get a better answer to argue with." Assertive people respect explicit rules far more than atmospheric disapproval, and the dominance research says pairing them with steadier colleagues works better than pairing them with mirrors.
The move that backfires. Vague niceness feedback ("soften your tone") and public correction. The first gives a precision instrument an unactionable target, and they'll conclude you value comfort over truth, after which you've lost the very candour that made them valuable. The second turns a colleague into an opponent, and this profile does not lose public contests quietly. Be exact instead: name the behaviour, the cost, and the replacement.
The perfectionist bottleneck
Very high Conscientiousness
What it looks like. Their work is the standard the rest of the team gets measured against, and it ships late. Reviews queue behind them; a document that was ready on Tuesday is still being polished on Friday; delegation happens rarely and gets partially redone when it does. The team has learned to route urgent work around them, which is a shame, because they're the only person who would have caught the error that's about to cost you a client.
What it is not. Control-freakery, insecurity, or an inflated sense of importance. Very high Conscientiousness genuinely perceives quality gradients other people can't see; asking them to "just ship it" reads to them the way "just leave the bug in" reads to you. Barrick and Mount's meta-analytic work made Conscientiousness the most dependable trait predictor of job performance we have. This is that asset, dialled to eleven and unmanaged: a strength that has quietly annexed decisions (what's worth polishing) that belong to the team.
The move that works. Externalise the quality bar so their conscience stops being the arbiter. Define tiers with them, in writing: which work is tier one, ship at ninety-five percent, and which is tier three, ship at eighty and iterate. Time-box polish ("two passes, then it goes"), and route the genuinely quality-critical path (the audit, the launch, the contract) straight to them, labelled as such. When "good enough" is a documented standard they helped set, meeting it stops feeling like a betrayal of craft and starts feeling like hitting a spec.
The move that backfires. Pace pep-talks and surprise squeezes. "Done is better than perfect" posters change nothing about how this person experiences an unfinished edge. And springing a moved-up deadline on them without renegotiating the standard forces a private crisis: your date against their conscience. They'll hit the date, silently work the weekend to protect the standard, and you'll have taught them that your deadlines are the enemy of their integrity. Renegotiate the bar out loud instead; they honour explicit trade-offs.
The firefighter
High Openness and steady nerves, lower Conscientiousness
What it looks like. When production went down at 2am, they were extraordinary: calm, inventive, three workarounds deep while everyone else was still finding the incident channel. Give them an ambiguous mess and they return with something nobody else would have tried. Then the crisis ends, the cadence resumes, and they wilt. Status updates arrive late or not at all; the checklist they wrote during the retro goes unused, including by them; the follow-through tickets rot. You've started to wonder if they only work when something's on fire. Roughly speaking, yes.
What it is not. Laziness or immaturity. High Openness with steady nerves and modest Conscientiousness is the improviser's profile: enormous appetite for the novel and the ambiguous, low tolerance for repetition, composure exactly when structure collapses. The trait that makes checklists feel like sandpaper is the same one that made them brilliant at 2am. Punishing the profile's cost while consuming its benefit is the standard mistake, and this person can smell it.
The move that works. Aim them at the volatile edge of the roadmap and pair them with a finisher. Incidents, spikes into unknown territory, the first draft of anything unprecedented: theirs. The productionising, the documentation, the third iteration: a natural finisher's, credited as equal work rather than cleanup. Then shrink process to the two rituals that genuinely matter and hold precisely those ("I don't care how you work; the Friday note and the handover doc are non-negotiable"). Complementary pairing at exactly this junction is what a team compatibility test shows you at a glance: who steadies whom.
The move that backfires. Process-maximalism: responding to each dropped ball with another mandatory field, template or ceremony, and grading them on tidiness rather than outcomes. Every added ritual taxes their strongest hours and confirms their suspicion that the organisation prefers compliance to results. Tighten everything, and the person who saved the quarter at 2am starts saving some other company's quarter instead.
One-to-ones with trait data on the table
The four portraits above are the acute cases. The chronic work of managing different personalities happens in one-to-ones, and this is where a measured profile quietly earns its keep, because it upgrades your questions from generic to specific. "How's the workload?" becomes, for the hermit, "which meetings this fortnight could have been a document?" For the steamroller: "which decision this month deserved more challenge than it got, and which got more than it needed?" For the perfectionist: "what are you polishing right now that's already at spec?" For the firefighter: "what's boring you, and what's the smallest structure that would stop it becoming a dropped ball?"
Ground rules keep this healthy. The profile belongs to the person: in SMP Assess, each member takes an eight-minute Big Five assessment and keeps their own personal report, so a one-to-one references what they can see and own, never a dossier you hold over them. Ask rather than announce ("your profile suggests X; does that match your experience?"), because the person is the authority on themselves and the score is one input. And use the team-level view, the team personality map, for what it's for: seeing how the styles combine, which pairs will mesh or grind, and where the group's floors and gaps are, so your one-to-ones and your team design tell the same story. When trait diversity helps a team and when it hurts is a research question with real answers; the evidence lives in personality diversity in teams.
A one-line upgrade for your next 1:1
Swap "any feedback for me?" for a trait-matched version: to a reserved colleague, "what should I start putting in writing?"; to a candid one, "where am I being too gentle with the team?" Specific doors open; general ones don't.
When to stop diagnosing and just ask
A warning, offered with affection, because trait language is genuinely useful and precisely that usefulness is the trap. Once you have the vocabulary, everything starts looking like a trait. The analyst who's gone quiet must be "low Extraversion", except she was animated until six weeks ago, and what's actually happened is her project got cancelled without anyone telling her why. The missed deadlines read as "low Conscientiousness", except his profile says the opposite, and the real story is a dependency on another team that he's too proud to escalate. Personality explains a person's weather patterns. It says nothing about the storm that arrived on Tuesday.
So hold a simple discipline: traits explain patterns, situations explain changes. A stable style that's been true since the day someone joined is trait territory, and the moves in this guide apply. A departure from someone's own baseline is a signal, and the response to a signal is a question, asked plainly: "you've seemed flat for a fortnight; what's going on?" The profile actually makes this easier, because knowing someone's baseline is what lets you notice the departure early.
And when a difference keeps costing the team despite good design, remember the third option beyond fixing the person or absorbing the cost: change the composition around them. Sometimes the kindest reading of a chronic mismatch is that the team lacks a complement (a finisher, a stabiliser, a challenger), and the fix is your next hire; a role-mapped hiring assessment turns that gap into a profile you can actually screen for. Personality informs all of these calls. It decides none of them. The person in front of you always outranks their dashboard.
Managing different personalities: FAQ
How do you manage a team with very different personalities? +
Start by separating pattern from character. Most recurring friction on a team is a collision of stable, measurable working styles: pace, social energy, candour, tolerance for ambiguity. Map the styles with a validated Big Five assessment so everyone can see the pattern, then manage to it: written pre-reads for the reserved, decision rules for the drivers, quality tiers for the perfectionists, and outcome-based goals for the improvisers. The differences stop being personal the moment they have names.
Should a manager see their team’s personality results? +
Yes, with consent and in the right shape. In a well-designed team assessment each person keeps their own personal report, and the manager sees team-level patterns and dignified pair reads rather than anyone’s raw answers. That balance gives a manager something genuinely useful to work with while keeping each person the owner of their own profile.
Can people change their personality? +
Traits are stable, and that stability is useful: it’s why a profile from this quarter still describes someone next quarter. But stable is a long way from fixed. People flex their behaviour around their traits constantly, especially when the environment makes the flex cheap: an agenda in advance lets a reserved person shine, a decision rule keeps a driver constructive. Manage the environment, and you rarely need the person to change at all.
What should I do when two strong personalities keep clashing? +
Two natural drivers contest decisions; that is the most predictable friction pattern in the research. The fix is jurisdiction, not personality surgery: name who owns which calls before the work starts, give each a domain where they genuinely lead, and agree what happens on a tie. Most "personality clashes" between two capable, assertive people are actually an undefined decision right, which the two of them can fix in one honest conversation.
Is it fair to manage people differently based on personality? +
Treating people identically and treating them fairly are different things. Fairness means everyone gets the same outcomes protected: the same access to your time, the same shot at growth, the same standards. How you deliver that (written questions in advance for one person, live sparring for another) should absolutely vary, because people do. What personality data must never do is decide who gets opportunities; it only informs how you support the people who already have them.
See the patterns you've been managing blind
Each person takes an 8-minute Big Five assessment and keeps their own report. You get the team map: styles, pairs, floors and gaps, ready before your next one-to-one. Free to start, no credit card.
References
- 1. Barrick, M. R., & Mount, M. K. (1991). The Big Five personality dimensions and job performance: a meta-analysis. Personnel Psychology, 44(1), 1-26.
- 2. Bell, S. T. (2007). Deep-level composition variables as predictors of team performance: a meta-analysis. Journal of Applied Psychology, 92(3), 595-615.
- 3. Tiedens, L. Z., & Fragale, A. R. (2003). Power moves: complementarity in dominant and submissive nonverbal behavior. Journal of Personality and Social Psychology, 84(3), 558-568.
- 4. Felps, W., Mitchell, T. R., & Byington, E. (2006). How, when, and why bad apples spoil the barrel: negative group members and dysfunctional groups. Research in Organizational Behavior, 27, 175-222.
- 5. Soto, C. J., & John, O. P. (2017). The next Big Five Inventory (BFI-2). Journal of Personality and Social Psychology, 113(1), 117-143.
The four patterns here are illustrative composites, described with the respect every trait position deserves. Personality is one input into how someone works, never a verdict on who they are, and nothing on this page supports using a profile to exclude or remove a person.