Should Employers Buy a Personality Assessment for Team Friction?

Should you buy the assessment now?

Usually, no. When the source of conflict is unknown, a personality assessment is an indirect first tool: it measures reported tendencies, while the employer needs to understand a particular work problem. A score may describe how someone generally says they plan, decide, or respond. It cannot, by itself, show whether a late handoff happened because ownership was unclear, the schedule was impossible, information arrived too late, or colleagues interpreted one another’s behavior differently.

The evidence gap matters to the purchase decision. A 2024 meta-analysis, “Revisiting the relationship between team members’ personality and their team's performance,” updated earlier work using team means and variation on Big Five traits and task-performance outcomes. Its accessible abstract reports several weak relationships and important moderators. That is evidence about average relationships across studies, not evidence that a team report can pinpoint local conflict. The Chartered Institute of Personnel and Development’s public 2021 evidence summary says the impact of widely used personality scales on performance and development remains unclear and finds little support for broad use as development tools. Its underlying resource is restricted, so this conclusion should be kept to the published summary.

The first purchase should therefore improve the employer’s understanding of the recurring problem. That may mean time with the people involved, a neutral facilitator, or a review of a particular workflow. These options are not guaranteed remedies. Their advantage at this stage is that they can collect information about the actual episodes and conditions the employer needs to explain. A personality report can enter later if the inquiry identifies a narrower question about work preferences or interaction habits that participants want to explore.

Sources: Revisiting the relationship between team members’ personality and their team's performance: A meta-analysis; Are personality tests over-rated?

Name the friction before choosing a measure

The same visible argument can arise from different sources. Team-conflict research commonly distinguishes task conflict, process conflict, and relationship conflict. Task conflict means disagreement about the work’s content or goals. Process conflict concerns how the work is arranged, including responsibilities, timing, or resources. Relationship conflict concerns interpersonal incompatibility or personal tension. A real episode may combine them; these categories are questions to investigate, not boxes into which a person should be placed.

Consider a recurring handoff that arrives late. One colleague says the draft needs another review; another says the delay is blocking a dependent task. The dispute could concern the standard of the work, the person responsible for approving it, or an unrealistic sequence in which the receiving team gets too little time. If the exchange has become personal, relationship tension may now add to the original issue. A personality profile cannot tell which explanation is operating simply because one person reports a preference for detail and another reports a preference for speed.

The distinction changes the next question. For a task disagreement, ask what standard or evidence would settle the substantive issue. For a process dispute, ask who owns each step, when a decision is due, and what information must travel with the handoff. For a relationship concern, ask what observable interaction is making collaboration difficult, without treating an inferred motive as fact. Also ask whether several people face the same bottleneck; a recurring problem across roles may point toward a workflow or resource condition rather than an individual tendency.

A review of conflict research in medical teams describes these categories and concludes that process and relationship conflict tend to detract from team functioning. Task conflict is also generally difficult, though its effects depend more on context and whether the discussion can remain about the work. The review is relevant as a map of distinctions, but its focus is medical teams and it does not evaluate purchases of workplace personality tools. A separate meta-analysis of 116 studies and 8,880 groups likewise found that task-conflict outcomes varied with moderators, while relationships between conflict types and outcomes were not interchangeable. Neither source says a questionnaire can distinguish the causes in a specific group.

Before commissioning any measure, write down two or three competing explanations for the friction and what observation would help distinguish them. This simple step makes the choice of tool accountable to the question. If the explanations remain broad, assessment results are likely to create more interpretations rather than settle the decision.

Sources: Conflict in medical teams: opportunity or danger?; The paradox of intragroup conflict: A meta-analysis

What can team personality research actually establish?

Team-composition research asks whether aggregated personality characteristics of team members are associated with some team outcomes. It does not ordinarily ask whether buying a report for an already-frictional team identifies the conflict’s cause, changes the work system, or improves collaboration. Those are different questions, with different designs and outcomes. The first kind of evidence can make personality worth studying without validating every product or intervention that uses personality language.

The 2024 meta-analysis focuses on the means and standard deviations of team members’ Big Five traits and team task performance. The abstract says several relationships were weak and that moderators influenced them. The accessible university record does not provide the full set of effect estimates, included-study count, or moderator details, so those should not be inferred here. The result is still useful in one respect: it cautions against assuming a simple, universal mapping from a team’s trait profile to how well it performs. It does not tell a manager that two people’s different profiles caused a particular argument.

An earlier meta-analysis, “Deep-level composition variables as predictors of team performance,” synthesized research on team composition and outcomes. Its abstract reports that some personality-performance relationships differed between laboratory and field settings and depending on how traits were represented at team level. This is a reminder that a group average, the range of scores, and the lowest or highest individual score are not equivalent descriptions. The study is broad team-performance evidence, not a local conflict diagnosis, and its older evidence base cannot settle what a current vendor’s particular report can support.

There is a tempting counterargument: if traits sometimes relate to how teams perform, then profiles may reveal the friction pattern. That inference moves beyond the evidence. A group-level association does not identify direction or cause in one team. A difference can be present without causing a problem; a work-system constraint can produce friction among people with similar profiles; and the same tendency can have different consequences depending on role, task, power, and timing. A profile can suggest a conversation hypothesis, but the team would still need to check it against observable work.

The practical conclusion is modest. Personality research can support treating tendencies as one possible influence among several. It cannot establish that personality is the principal explanation for a particular conflict, that a given product detects it, or that reporting a profile will improve the outcome. Employers should ask a provider for evidence about the exact instrument, interpretation, population, and intended developmental use rather than borrowing credibility from personality research in general.

Sources: Revisiting the relationship between team members’ personality and their team's performance: A meta-analysis; Deep-level composition variables as predictors of team performance: a meta-analysis

Start with episodes and work conditions, not labels

A short episode review gives the employer a closer view of the phenomenon it wants to change. It is not a personality test or a formal research study. It is a practical way to make a vague label such as “poor communication” specific enough to investigate. Select a few recent, comparable episodes rather than asking people to summarize one another’s character. Record the task, the relevant exchange or decision, the expected process, and the effect on work. Keep facts separate from explanations: “approval arrived after the release cutoff” is an observation; “the reviewer is controlling” is an interpretation.

For a handoff, the inquiry might ask: What item was being handed over? Who believed they owned the next decision? What was the agreed deadline? What information did the receiver need? When did each person learn about a dependency? What changed after the handoff? Ask each participant independently for their account before comparing them. This can expose a mismatch in expectations without requiring the employer to decide immediately whose account is correct. The process should also make space for status or power differences: a person may not feel safe naming an issue in a meeting led by someone who controls their workload or evaluation.

The US Office of Personnel Management describes job analysis as examining work tasks, required competencies, and the links between them to support assessment decisions. That guidance is written for federal assessment and selection, not as a conflict-investigation protocol. The cautious application here is a principle: define the work and the decision before choosing a measure. For a team issue, that means tracing what the team is expected to do and where the actual episode departed from the agreed conditions, not importing the federal method as a mandated procedure.

Then test several explanations. If the handoff is unclear because responsibility changes between two roles, clarify the owner and approval point. If the receiving person repeatedly lacks the same information, review the handoff template or upstream access. If deadlines conflict with available capacity, escalate the workload or sequence decision. If expectations are clear but an exchange repeatedly becomes dismissive, identify the behavior and its impact, then decide whether a facilitated conversation or other support is needed. None of these observations proves a person has a fixed trait. They show what happened under particular conditions.

Use a small record rather than a sprawling investigation: date or project stage, task, expected handoff, what occurred, consequence, and unresolved question. Protect access to notes, share the purpose with participants, and do not quietly repurpose comments as performance evidence. The record is useful when it changes the next action. If it repeatedly points to an individual interaction pattern after workflow explanations have been checked, a voluntary assessment may help people discuss preferences. If it points to role ambiguity or workload, the more relevant intervention is likely to sit there.

Sources: Job Analysis; Conflict in medical teams: opportunity or danger?

Compare the report with a direct inquiry into work

The comparison is not between a sophisticated test and an informal chat. It is between tools that answer different questions. A personality assessment asks people to respond to statements that are interpreted as tendencies. A structured episode review asks what happened in defined work situations and what conditions shaped it. The first may provide language for self-reflection; the second is closer to locating whether an observed problem concerns task content, process, roles, dependencies, or interaction. Neither guarantees a correct explanation, and neither alone repairs a conflict.

For the delayed handoff, a profile might prompt a participant to reflect on whether they tend to seek more review or move forward with incomplete information. That can be useful if the person recognizes the tendency and wants to decide when it helps or hinders. But the report cannot establish whether the delay arose from a missing approval rule or a deadline set without enough capacity. The episode review can reveal those conditions, but it cannot by itself summarize how a participant generally prefers to plan. Each tool should be judged by the question it can actually answer.

Work samples are sometimes proposed as a more direct alternative. OPM defines them in selection as tasks identical or similar to job tasks, with assessors observing behavior or measuring task outcomes. This is not a recommendation to stage a team conflict or to turn existing employees into candidates. It illustrates the difference between observing performance on a bounded task and inferring broad tendencies from a questionnaire. For a live collaboration problem, reviewing naturally occurring work episodes is usually less artificial than designing a test exercise, though it still requires care about privacy and fairness.

The CIPD’s selection factsheet likewise says psychometric tests can assess individual differences, including personality, while skill-based assessment tasks should reflect the role’s real work. That material concerns selection. It should not be stretched into evidence that work samples or personality tests resolve team friction. Its narrower lesson is useful: the closer the method is to the intended question, the easier it is to explain why the result matters. If the question is “Who owns approval at this stage?” a process map or role clarification is more direct than a trait score. If it is “What planning preference should I discuss with my colleague?” a self-reflection tool may be relevant.

A manager can compare options with four prompts: What question will this method answer? What evidence will it produce? Who will interpret it and how? What action could reasonably follow? If the answer to the first prompt is “understand why these people conflict,” a generic personality report is too broad. If the answer is “give willing participants a shared prompt to discuss different approaches after we have clarified the workflow,” the assessment may be proportionate. The distinction prevents a tool’s polished output from being mistaken for a diagnosis of the work system.

Sources: Are personality tests over-rated?; Selection Methods; Work Samples and Simulations

What evidence would justify the purchase?

Before paying, require evidence that matches the intended use. Reliability concerns the consistency of scores under specified conditions; validity concerns whether evidence supports the interpretation and decision being made. A reliable score is not automatically an accurate explanation of a workplace event. Evidence that supports use in one setting or for one purpose does not automatically support another. An instrument used for selection, for example, cannot simply inherit that evidence when offered as a voluntary team-development tool.

OPM’s assessment strategy guidance makes this purpose-specific point in a federal employment context. It says validity evidence depends on how a method is used, and contrasts evidence needed for a work sample with evidence for a personality test intended to forecast job success. The article applies the general logic, not OPM’s selection rules: ask the provider what claim the assessment makes in this exact use, what evidence supports the score interpretation, and whether that evidence concerns learning or development rather than another purpose. The page’s statistics and validity table are adapted from older selection research, so they should not be presented as current estimates of the value of team-development reports.

Ask for the instrument name and version; the construct and score meaning; the population on which evidence was gathered; the intended use; the evidence for score consistency and interpretation; and the limits the provider places on conclusions. If the tool produces group summaries, ask how those are calculated and what a facilitator should do when participants disagree with the description. Ask what happens to item responses and reports, who can access each, how long they are retained, and whether an employee can decline without penalty. A vendor’s testimonials or attractive sample output do not answer these questions.

A useful proposal also names a behavior to examine and a review point. For example, participants might agree to test one meeting practice for several project cycles, such as circulating options before a decision meeting, then discuss whether it changed who contributed or how decisions were documented. This is an illustrative development plan, not a proven intervention or a guarantee of improvement. The measure of success should be an observable work practice that participants can inspect, not a claim that scores have made the team compatible.

The minimum defensible procurement file can still be concrete: the question and intended use, the provider’s technical materials, an explanation of privacy and access, the facilitator’s qualifications for the work, a plan for voluntary participation, and a specific follow-up action. If the provider cannot supply those details or makes broad claims that the report will reveal the root cause, defer the purchase. Uncertainty about fit is a reason to ask for better documentation, not to fill gaps with confidence.

Sources: Job Analysis; Selection Methods; Designing an Assessment Strategy

When could a personality report be worth buying?

A report may be worth buying after the employer has narrowed the question and participants want a structured way to reflect on individual work tendencies. For example, a team may have clarified who approves a handoff and still find that members differ in how much review they prefer before release. A voluntary report could offer a vocabulary for discussing that preference. It should be treated as a prompt to compare with examples and context, not as proof that one person’s style caused the delay or that another person must adapt.

This is the strongest case for the purchase: a bounded developmental conversation where the result belongs primarily to the participant, the group understands the limits, and the facilitator keeps attention on observable choices. The output could help someone ask, “When does my preference for a complete plan help this project, and when might it slow a decision?” A colleague can add a different perspective, but not an authoritative verdict on the person’s character. A tendency may show differently across tasks, pressures, relationships, and roles. Participants should be able to say that a description does not fit or needs qualification.

The CIPD summary is a serious caution against assuming broad developmental impact from the fact that an assessment is popular or commonly used. It reports little evidence for wide-scale use of personality tests as development tools and says their impact on performance and development remains unclear. Because its detailed review is member-restricted, the public summary cannot tell us which forms of facilitated use are more promising or how effects vary by instrument. It does not prove that every reflective conversation is useless. It does shift the burden to the purchaser to define a modest outcome and check whether practice changes.

The team-personality meta-analysis offers a complementary limit. Some aggregated trait relationships with task performance are weak and moderated. That finding makes it especially important not to turn group profiles into prescriptions such as “this team needs a decisive person” or “these two types should not work together.” Even when a team-level relationship exists, it does not establish that changing composition or assigning roles by personality would improve a particular team. Role decisions should remain connected to skills, responsibilities, workload, and the actual work required.

The purchase is harder to justify if participation is compulsory, results go directly to a manager without clear agreement, scores are used to rank or discipline staff, or an employer expects the report to resolve a structural problem. Those conditions change the stakes and may undermine candor. In this publication, the live Work Pattern Report is a non-validated, low-stakes self-report covering work tendencies such as decision-making, collaboration, conflict, and learning. It has no norms or selection score. Someone who wants private reflection on their own work pattern can use it, but it cannot assess an employer’s team or diagnose the source of friction.

Sources: Are personality tests over-rated?; Revisiting the relationship between team members’ personality and their team's performance: A meta-analysis; Personality Report

A proportionate next step

A practical decision has three stages. First, identify the recurring work episode and the decision the employer wants to improve. Second, gather enough accounts and workflow detail to compare plausible explanations, including role, resource, timing, and authority conditions. Third, choose the least indirect method that can answer the remaining question. This is a decision rule derived from the evidence distinctions above, not a procedure tested in a direct trial against personality assessment purchases.

If the inquiry finds that a role is unowned, clarify ownership and review whether the handoff works. If people disagree about the work itself, make the relevant standard or evidence available and set a process for deciding. If a repeated interaction is the central concern, identify the conduct and impact, and consider a skilled facilitator or manager support. If participants then want to explore different preferences in planning, feedback, or conflict, an assessment may support that conversation as one input. Check the tool’s intended use, supporting evidence, privacy arrangements, and follow-up plan before approving it.

The strongest exception to “inquiry first” is a team that already has a clear developmental question and wants a common prompt, rather than a diagnostic answer. In that case, assessment can be a reasonable purchase if employees can decline, control access to individual results, and discuss interpretations without being sorted into fixed categories. But if the employer cannot yet name whether the problem concerns the task, process, relationship, or conditions of work, the assessment is premature. Better information about the episode is the more useful first investment.

For an individual trying to understand their own contribution to a difficult collaboration, the live Work Pattern Report at [/assessment](/assessment) can offer a private set of prompts across decisions, planning, feedback, conflict, collaboration, and change. It does not assess coworkers or tell an employer what caused a team problem. Use it only if a personal reflection would help clarify a next conversation; otherwise, begin by writing down one recent episode and the question it leaves open. For further assessment-literacy guides, see [/topics](/topics).

Sources: Job Analysis; Revisiting the relationship between team members’ personality and their team's performance: A meta-analysis; Personality Report

Questions readers ask