How to Discuss a Personality Report at Work

What should you say when a personality report comes up in a disagreement?

When a personality report comes up during a workplace disagreement, keep it in the first person and treat it as a question about a possible pattern. Say what the report suggests about your own tendency, describe the exchange, and ask what conditions shaped it. A score cannot establish why a colleague acted as they did, explain this disagreement, or decide who was right. Start with what happened and the work around it. The report can suggest something to notice across occasions: perhaps you want more time to compare options or speak up when a decision feels incomplete. It does not show that this tendency caused a specific exchange. Episode-level evidence is different: the words or actions people recall, when they occurred, what information was available, and what deadline applied. The broader pattern remains a prompt, not a verdict. Imagine a release date is approaching and one person asks for another review while a colleague wants approval now. Calling one “indecisive” and the other “rigid” turns labels into an explanation. A useful opening is, “My report suggests I may want time to evaluate options. In that review, I asked for another check as the release date approached. What constraint were you working with?” The account can be corrected without requiring either person to accept a label. The U.S. Office of Personnel Management’s “Personality Tests” guidance describes several assessment formats and says work relevance depends on the job. This employment guidance is not evidence that a score explains an informal disagreement. Its lesson is that a measure’s purpose limits what a result can support. Without knowing the instrument and intended use, do not give a score more authority than its report provides. Mentioning a report should be voluntary. You can keep it private and reflect on your responses. If you share it, offer one tentative sentence, return to the exchange, and invite the other person’s account.

Sources: Personality Tests

What does a report score describe—and what does it leave out?

A personality report score summarizes answers to a particular set of prompts under that instrument’s scoring method. It may prompt reflection, but it does not show why a disagreement happened, what another person intended, or who was right. Check what the report measures before bringing it into a work conversation. A self-report inventory is a questionnaire in which people describe themselves by responding to statements or questions. The U.S. Office of Personnel Management’s “Personality Tests” guidance lists self-report inventories alongside interviews, exercises and observer ratings. It says inventories ask applicants to rate agreement with statements designed to measure relatively stable traits, then use the profile in relation to job performance or satisfaction. That is a defined assessment purpose. A questionnaire response is not a recording of a meeting, and a profile does not provide a causal account of a later exchange. “Score” can mean different things. A raw score is calculated from responses before comparison with a reference group. A standardized score expresses a result on a transformed scale; a norm-referenced result compares it with scores from a stated group. Reports may translate a number into a band or label. Meaning depends on the instrument’s scale, scoring rules, comparison group and explanation. Without documentation, do not guess what a number means. Even an accurate description has a boundary. “The report suggests I may prefer time to evaluate options” is a tentative statement about the report’s interpretation of the respondent. “My score caused this disagreement” is a causal claim about an event, and the first statement does not establish the second. A causal explanation needs evidence about the exchange and alternatives such as unclear authority, missing information or a changed deadline. The score establishes none of these details, nor what a colleague thought or intended. Consistency and validity answer different questions. Reliability concerns whether scores are consistent under comparable conditions. Validity evidence concerns whether an interpretation or use of scores is supported. In “Designing an Assessment Strategy,” OPM explains that evidence should match the assessment’s purpose. For example, a personality test intended to forecast success in a particular job calls for evidence relating scores to later performance in that job. Such evidence addresses that prediction; it does not explain one disagreement between colleagues. Before sharing, ask: What instrument produced this? What tendency does it measure? Is the result raw, standardized, norm-referenced, or a band? What population and purpose apply? If those answers are unavailable, keep the claim modest: the wording may suggest something to notice about your own recurring pattern. Then examine what happened, what each person observed and which work conditions may matter. This keeps a score in its proper role: a prompt for a question, not a verdict on a disagreement.

Sources: Personality Tests; Designing an Assessment Strategy

How can a stable tendency and an unusual meeting both be true?

A trait-level tendency describes a pattern across occasions, not a rule that every moment must follow. A person may often prefer time to compare options and still approve quickly when the evidence is clear. Another may usually move fast yet pause when a risk is hard to reverse. The unusual meeting and the broader tendency can both be real. One disagreement cannot establish a person's overall pattern, and a report score cannot identify its cause.

This distinction is sometimes expressed as trait and state. A state is a short-term way of acting, thinking, or feeling in a particular moment; a trait describes a more general tendency across moments. In “Toward a Structure- and Process-Integrated View of Personality: Traits as Density Distributions of States,” three experience-sampling studies asked participants to describe current behavior several times a day over two to three weeks. The paper reports substantial variation within people alongside relatively stable averages. An average can describe a recurring pattern while leaving room for different particular actions.

That evidence concerns sampled everyday behavior, not workplace disagreement. It does not show that a personality score predicts what someone will do or why a dispute happened. It supports a narrower caution: treating one action as a complete description of a person ignores the other occasions needed to judge a pattern. The reverse shortcut is also weak. A score cannot tell us that a tendency produced this action, because it does not contain the meeting's circumstances.

Consider an illustrative decision, not a documented case: a draft is close to its release deadline, and a colleague asks for another review before approval. A score-first account might call the colleague cautious, or the approver impatient. Those labels do not tell us whether the request was typical, what risk it addressed, who had authority, whether key information was missing, or how much time remained. Timing, decision responsibility, or a late change in the draft may matter. These are questions to check, not causes to assume. The request could reflect a recurring preference, this assignment's demands, or both.

For this episode, begin with what happened: another review was requested before a stated deadline. Ask what information or risk it addressed and what decision was due. If relevant, the person can choose to mention the report as a question about their own pattern: “I may tend to want another check when a decision feels consequential. Does that fit across situations, or was something specific about this draft concerning?” The colleague need not accept the description; the score should not assign them a motive.

Keep the inquiries separate. To discuss the disagreement, examine the exchange and its constraints . To reflect on a possible tendency, look across comparable occasions, including examples that do not fit the report wording. An average pattern and a one-off exception answer different questions. Use the report to decide what you might notice next time; use observable details to decide what to clarify now.

Sources: Toward a Structure- and Process-Integrated View of Personality: Traits as Density Distributions of States

Why do self-report and observed behavior tell different parts of the story?

A report records answers to prompts; an observer records behavior visible in a setting. One may summarize a person's view of their tendencies; the other captures a limited slice of work through the observer's perspective. Neither automatically outranks the other in a disagreement. A study titled “Assessment of Personality through Behavioral Observations in Work Simulations” illustrates the distinction. In an assessment center, researchers rated 123 participants with a scale designed to capture personality-related behavior during work simulations, then compared those ratings with corresponding self-report traits. Correlations ranged from .11 for Neuroticism to .31 for Extraversion. The correlations show limited correspondence in that comparison, not that one method was accurate and the other mistaken. The study concerned trained ratings across simulations, not a coworker's memory of one tense meeting, and its instrument and assessment-center setting limit generalization. It cannot identify the cause of a specific exchange. A second study, “The Impact of Contextual Self-Ratings and Observer Ratings of Personality on the Personality–Performance Relationship,” asked a different question: how personality ratings related to job-performance criteria. Observer ratings explained additional variance in in-role performance and organizational citizenship behavior beyond general self-ratings. Work-specific self-ratings generally added no variance beyond general ratings. This concerns prediction of specified performance criteria. It does not establish that observers are better judges in every setting or that a supervisor can settle a dispute. Predicting a defined outcome and reconstructing one episode are separate tasks. The contrast matters because the evidence changes with the method. A questionnaire gives access to a person's answers, but not a recording of what they did under a deadline. An observer can describe visible words or actions, but may not know what information the person had, what alternatives they considered, or whether the observer saw comparable situations. A simulation samples behavior under designed conditions; a colleague's recollection may be shaped by what stood out. Observation alone does not establish intention or cause. Self-description can miss behavior; observation cannot reveal every private reason. When the accounts differ, compare what each can actually support. Ask which words or actions the colleague has in mind, when they occurred, and what part of the interaction they observed. Check whether the report names a broad tendency or specific behavior, and whether both accounts concern the same situation. Keep the event description separate from its interpretation: “I asked to delay approval after the deadline changed” is more checkable than “I am cautious” or “you resist change.” Then ask what each person may not have seen. Keep each account's limits visible while gathering evidence. Avoid turning this comparison into an informal rating exercise in which coworkers score one another. The studies concern particular measures, settings, and outcomes; they do not validate peer diagnosis or score-based explanations of conflict. Concrete examples and observation conditions are more useful than deciding whose account wins. A report can suggest a question to examine across occasions. It cannot replace the episode evidence needed to understand this disagreement.

Sources: Assessment of Personality through Behavioral Observations in Work Simulations; The Impact of Contextual Self-Ratings and Observer Ratings of Personality on the Personality–Performance Relationship

How can you discuss the report without assigning motives?

A useful conversation keeps three things separate: what the report tentatively says about your own tendencies, what happened in the exchange, and what you do not know about the other person’s reasons. The U.S. Office of Personnel Management’s “Personality Tests” guidance describes measures that take different forms and whose relevance depends on purpose. Consider this illustrative situation: a release date has been set, and approval is delayed while an issue remains unresolved. Your report describes a possible preference for more time to evaluate options. You decide to raise the delay with a colleague. A score-first version might say, “You are rigid about deadlines, and I avoid conflict, so this was bound to happen.” It assigns traits as the cause. It skips useful questions: who owned the approval, what information was available, whether the date had changed, and what risk each person understood. A more careful opening could be: “My report suggests I may want more time to evaluate options. In Tuesday’s review, I objected after the release date was set. I may be missing context. What information or constraint shaped your decision?” This illustrative script is not a tested intervention. Its first sentence offers a tentative self-description rather than a fixed identity. The second names an event the speaker can point to and the colleague can correct. The question leaves the cause open. Perhaps the colleague had new information; perhaps the deadline was firm; perhaps the objection came too late to change the plan. The score cannot decide among these possibilities. Precision makes the exchange fairer. “You always shut down questions” combines a broad frequency claim with an interpretation of intent. If the concern is one meeting, say what was observable: “I raised the unresolved issue after we agreed the date.” If the concern recurs, identify specific occasions and the effect on work, without turning examples into a personality verdict. Keep the claim proportional to evidence, while allowing information that could change it. The colleague should be able to decline the report discussion. A conversation may not feel equally voluntary when one person has more authority. Ask, “Would you be comfortable discussing a reflection I had from a report, or would you rather focus on the decision process?” If they prefer the latter, continue with the work issue. A report is not required to ask about an approval path, decision owner, deadline, or missing information. If someone uses your score to explain you, set a short boundary and redirect: “That report is a prompt for my own reflection, not an explanation of this disagreement. Let’s look at what happened and what we each needed.” Then return to the concrete issue. The report stays in a limited role: a possible prompt for noticing a pattern, while the people involved examine the exchange and its conditions together. Before mentioning it, decide whether the report adds anything useful to this conversation. If not, leave it private and discuss the decision in ordinary work terms.

Sources: Personality Tests

What if your account and a colleague's account do not match?

A mismatch between your account and a colleague’s is a reason to get more specific, not a verdict that one of you is dishonest or that the report has failed. Before interpreting it, check whether you are describing the same behavior, period, role, and setting. “I hold back in meetings” could refer to large planning sessions; “you speak up quickly” could refer to urgent project reviews. Both accounts might fit their examples. A report captures responses to its prompts, while a colleague sees only some of your actions. The views can differ without either one settling what happened in a disagreement. A study titled “Identifying Causes of Disagreement Between Self-Reports and Spouse Ratings of Personality” offers a comparison. In its first study, 47 married couples completed the Revised NEO Personality Inventory about themselves and each other. In a second study, the couples discussed substantial disagreements, and researchers coded the interview recordings. They identified 16 reasons for disagreement, including different understandings of an item, different time frames or roles, and a spouse’s lack of access to private experience. The study concerns spouses describing personality, not coworkers discussing a workplace conflict, and it does not test a conversation script. It cannot tell you which person at work is right. It does show why a gap between perspectives need not be reduced to deception or a faulty report. To examine the gap, compare the accounts along a few dimensions. First name the behavior in ordinary terms: interrupting, delaying a decision, asking for another review, or not raising a concern. Then identify the episode or period each person has in mind. Ask what each could observe: a colleague may recall what was said in one meeting, while you may also know what you were weighing silently or what happened before it. Check the report’s wording and time frame too. Does it describe a broad tendency, or are you treating it as if it described Tuesday’s exchange? Finally, list another plausible explanation, such as unclear decision authority, missing information, or a deadline change. These are questions to test, not facts to insert into the story. A calm way to start is: “Which situation are you thinking of?” Follow with a request for one example and a description of what each person saw or heard. You can then say what your own report led you to wonder, while making clear that it does not establish the cause. If your colleague recalls a different period, or you cannot verify a private motive, leave that part unresolved. Their account may be limited by the situations they witnessed or by the stakes of the disagreement; that possibility does not make the account worthless. Likewise, your broader self-view does not erase a specific example they can describe. The practical test is whether both accounts refer to comparable behavior and circumstances. Where they do, ask what each account explains and what neither explains yet. Where they do not, narrow the question before drawing a conclusion.

Sources: Identifying Causes of Disagreement Between Self-Reports and Spouse Ratings of Personality

When does a report's evidence matter to this conversation?

Evidence matters only in relation to the claim being made. A personality measure may support a particular interpretation for a defined purpose, yet that does not make its score an explanation for a disagreement in one meeting. The question is not simply whether a test is “valid,” but what its evidence supports someone doing with the result. Evidence linking a measure to a work outcome in a studied setting does not, by itself, reveal why two colleagues disagreed in one episode. That is a separate claim about that exchange and its causes. Reliability and validity answer different questions. Reliability concerns whether an assessment produces consistent scores under comparable conditions. Validity evidence concerns whether the evidence supports a particular interpretation or use of those scores. Consistency matters, but it cannot establish every claim someone might make from a report. In “Designing an Assessment Strategy,” the U.S. Office of Personnel Management (OPM) says relevant validity evidence depends on how an assessment will be used. A work sample designed to resemble job tasks calls for evidence about that match; a personality test intended to forecast success in a particular customer-service job calls for evidence that scores relate to later performance in that job. This distinction also applies when a report is shared informally. If its documentation supports using a scale to reflect on a broad work preference, the result may prompt its owner to ask whether a tendency recurs across situations. It still does not show that the tendency caused a particular objection, reveal a colleague’s motive, or establish who was right. Those claims require evidence about the exchange: what was said or done, what decision was pending, what information each person had, and what constraints shaped the moment. The stakes also matter. Voluntary reflection differs from using a measure to screen applicants or influence performance, promotion, or pay. OPM’s “Personality Tests” describes formats including self-report inventories, interviews, exercises, and observer ratings, and notes that factors relevant to job performance depend on the job. The page concerns employment assessment, not informal disagreement; it cannot validate an unnamed report or settle this conversation. It does show why a manager should not substitute a personality label for a defined assessment process tied to the work. If a manager brings a score into an evaluation, ask what claim is being made and what evidence supports that interpretation for this purpose. Ask which observable work behavior is relevant and request the organization’s formal assessment process, with criteria connected to the role. A score should not quietly become evidence of motive or fault. In a low-stakes conversation, ask: “What does this report support me in reflecting on, and what do we still need to understand about this disagreement?”

Sources: Designing an Assessment Strategy; Personality Tests

What should change when the disagreement involves power or harm?

Do not use a personality report to soften conduct that needs a work decision. A coordination disagreement, such as who owns a decision or when review is due, may be resolved by clarifying expectations. Repeated harm, retaliation, discrimination, safety concerns, or a possible policy breach call for attention to what happened and an appropriate workplace process. A score should not turn harm into a private mismatch or decide the response. The distinction depends on the decision at stake, not on labeling either person. Repeatedly excluding someone from needed information may affect their work in a way that cannot be addressed by saying one person prefers structure and another flexibility. That does not establish intent or prove a policy violation. It identifies conduct and impact for the relevant process. Severity, repetition, impact, and formal responsibilities matter more than a personality explanation. The U.S. Office of Personnel Management’s “Personality Tests” guidance describes employment measures as tools that may predict job performance or satisfaction, with relevance depending on the job. It addresses employment assessment, not informal disputes. “Designing an Assessment Strategy” ties validity evidence to intended employment use: a measure meant to forecast success in a particular job needs evidence relevant to that purpose. A report shared for reflection is not thereby a formal performance assessment, and neither kind of score establishes why an act occurred. If a manager uses a report to affect evaluation or promotion, ask what process governs the decision and what job-related evidence is considered. Power affects participation. A peer conversation where either person can decline differs from a manager asking a direct report to disclose a score or accept a label. The employee may wonder whether refusal will affect their treatment. A manager should not make disclosure a condition of resolving conflict or treat a report as evidence of motive. If a formal route may be appropriate, record what happened, when, who was present, what work was affected, and whether similar events occurred. Consult a suitable channel, such as a manager outside the reporting line, human resources, a union representative, safety contact, or established reporting process. If direct discussion feels unsafe, it need not come first. Procedures differ, so this article cannot determine which applies. Not every disagreement belongs in a formal complaint. Ask whether this remains a shared work problem that can be clarified safely, or whether seriousness, recurrence, impact, or power imbalance calls for another route. In the latter case, leave the report out of accountability decisions: describe conduct, and let the appropriate process consider what should happen. For a one-time misunderstanding, clarify the task and expectations first.

Sources: Personality Tests; Designing an Assessment Strategy

How can you test a practical explanation without turning it into a personality verdict?

A next step is a small process change that can be reviewed, not a verdict about anyone’s personality. Suppose a release decision stalled because one person asked for another review after a deadline was set. Possible explanations include: a report may have prompted the person to notice a tendency to seek more time; nobody may have been named as decision owner; the deadline may have shifted; or relevant risk information may have arrived late. The delay is observable in this example, but its cause is not established by the report or the delay alone. Choose one condition the people involved can change without settling those explanations first. For the next comparable release, they might write down who makes the final decision, what information must be available, and when review closes. If the same disagreement occurs with owner and deadline explicit, that is useful information, though it still does not identify a personality cause. If the exchange proceeds differently, the process may have helped; one smoother meeting would not prove the old process was the only problem. This is a coordination experiment, not a method tested in the studies cited here. Agree on what you will notice and when you will revisit the arrangement. After the next two comparable decisions, each person could note whether the owner was known, needed information arrived on time, and objections came before or after review closed. Check in on what changed and what still needs attention. Do not track a colleague as though this were an informal assessment; focus on the shared process and its observable effects. Privately, treat the report as a question to examine across occasions. Note examples that fit and those that do not, keeping their conditions visible. Fleeson’s “Toward a Structure- and Process-Integrated View of Personality: Traits as Density Distributions of States” reports three studies in which participants described current behavior several times daily over two to three weeks. The paper found substantial within-person variation alongside stable average tendencies. This everyday behavior research does not establish why a workplace disagreement happened or validate this review method. It supports caution about treating one episode as the whole pattern. The practical rule is modest: change one clear work condition, observe comparable situations, and keep results separate from claims about character. The U.S. Office of Personnel Management’s “Designing an Assessment Strategy” ties validity evidence to intended use, including relevant evidence when a test is meant to forecast success in a specific job. That differs from explaining one exchange. If friction continues, revisit the episode and its constraints; if it involves harm or a formal employment decision, use the appropriate workplace process rather than relying on a personality interpretation.

Sources: Toward a Structure- and Process-Integrated View of Personality: Traits as Density Distributions of States; Designing an Assessment Strategy

What is the next conversation to have?

Choose one exchange and begin with what both people could check: the decision, what was said or done, when it happened, and which constraint mattered. You might say, ‘In yesterday’s review, I asked to hold approval until we checked the late change. What deadline or information were you working with? Could we name the decision owner and review time before the next release?’ If you mention your report, keep it tentative and in the first person: ‘It gives me a prompt to notice whether I often want more time to assess risk.’ A single disagreement cannot show whether that is recurring or explain the other person’s response. The Office of Personnel Management’s “Designing an Assessment Strategy” ties validity evidence to intended use; evidence for a defined job prediction does not establish why one disagreement occurred. If the issue is repeated, materially harmful, or tied to an employment decision, a process tweak may be inadequate. Use the relevant management or reporting channel, and seek specific evidence for any formal evaluation. For private reflection, the optional Work Pattern Report presents ten continuums and a local summary; its page frames results as tendencies to examine, not labels. It is not a hiring score or conflict diagnosis. Ask: what should we make clearer before this happens again?

Sources: Designing an Assessment Strategy; Work Pattern Report

Questions readers ask