A manager's example of a delayed decision may point to a real work problem; a report's description of a cautious tendency may be a useful prompt. Neither proves that personality caused that incident or fixes what you can do next. Ask what you did, in which situation, and what work effect followed. Then agree on one observable behavior to try and a date to review it. If the report is shaping assignments, promotion, or another formal outcome, ask what job-related evidence supports that use. Treat the report as a hypothesis about a tendency, not as a verdict about the person.
What is the manager observing, apart from the label?
Start by separating two plausible readings. The manager may be describing a specific behavior that affected the work. Or the manager may be using a personality label to explain the behavior as if it were permanent. Ask for the event before accepting either account: “Which recent situation are you referring to? What did I do or say, and what effect did it have?”
A personality tendency is a pattern that may be more likely across some situations, not a script for every moment. A report might describe someone as careful about decisions. That does not establish why a particular choice took longer. The person may have been waiting for missing information, lacked authority, faced conflicting priorities, or been unclear about who owned the decision. Those possibilities should be checked against the event, not assumed from a score.
Keep the observation distinct from its interpretation. “The decision was still open at the end of Tuesday’s meeting” names an event. “You are indecisive” turns it into a broad trait judgment. The first can be checked against notes, deadlines, and the decision process; the second does not say what should change. You can acknowledge the concern without adopting the label: “I hear that the timing affected the project. Can we look at what information was missing and what you needed from me by that point?”
A small qualitative study helps frame this carefully, but it does not document stereotyping cases. Lundgren, Poell, and Kroon used grounded theory and inductive analysis of semistructured interviews with 18 human-resource development professionals. Their pattern analysis identified six practical strategies for personality testing: ethical-protective, scientific-selective, cautious-avoiding, cautious-embracing, user friendly-pragmatic, and knowledgeable-accommodating. The abstract also reports that professionals regularly faced cognitive dissonance and paradoxical situations in their use of tests. These findings describe varied approaches and tensions within this small interview sample; they do not show how common any approach is across workplaces or establish what happened in your manager’s case.
How can you turn the feedback into a fair test?
If the manager can name an event and its effect, turn that feedback into a small, reviewable experiment. First, reflect the concern in neutral terms: “You needed the decision before the meeting ended, and I did not give it then.” Next, ask what effective behavior would look like in that situation. Agree on one action you can try, when it applies, and when you will review whether it helped.
For example, if the concern is a delayed decision, one possible trial is to state the decision deadline, the information still missing, and the person responsible for providing it at the start of the meeting. That is an illustrative option, not a research finding or a recommendation for every job. In another setting, the useful change may be asking for a clearer deadline or confirming which trade-off the manager wants you to prioritize.
A fair test also leaves room for context and counterexamples. Note whether the needed information arrived, whether the deadline changed, and whether the action improved the handoff. If practical, review more than one relevant occurrence rather than treating a single success or failure as proof of a stable trait. The purpose is not to prove the report right or wrong. It is to learn whether a specific action works under the conditions that matter.
If the manager cannot supply an example, ask to keep the conversation on expectations: “I’m open to feedback, but I need a behavior and work outcome to act on. What should I do differently next time?” If the manager does offer details and remains open to revising the explanation, agree on the trial and follow-up. If the label is repeated instead of evidence, calmly ask that the performance description name the behavior and expectation rather than treating a personality category as the cause.
At the review, compare the agreed expectation with what happened, including the conditions: Was the deadline clear? Was the needed information available? Did the action improve the handoff? If the behavior recurs under comparable conditions, discuss a specific adjustment; if it does not, revisit the original explanation instead of carrying the label forward. Either result informs the next step, not a verdict about personality.
When does a label become a consequential assessment use?
A development conversation and a formal employment decision are different uses. In an informal discussion, the immediate question is whether the feedback identifies a concrete behavior that can be discussed and reviewed. If a report is used to restrict assignments, promotion, or another formal opportunity, it is reasonable to ask what the assessment was intended to measure, whether evidence supports that use for this role, and how the decision connects to actual job requirements. Without the instrument, score meaning, norm group, and intended use, no one can responsibly infer that a particular report supports that decision.
The Society for Industrial and Organizational Psychology’s December 2025 statement on employee selection procedures recommends identifying important work behaviors through job analysis, validating selection procedures using an appropriate strategy, and documenting reliability, validity, and job-relatedness. This is guidance about selection procedures, not a rule that every coaching conversation needs a formal validation study. Its relevance is that a score or report does not justify itself when an organization uses it to make consequential choices about people.
In the United States, the EEOC’s Title VII guidance describes a narrower legal condition: where an employment standard has a significant disparate impact on a protected group, the employer must show that it is job-related and consistent with business necessity, and a less discriminatory alternative may matter. The guidance gives a personality test for deciding who is “management material” as an example when that impact condition is met. It does not mean that every personality report use is unlawful, and it is not a general ruling on feedback or law in other countries.
If the result is affecting an opportunity, ask for the written policy, the role-related basis, and the evidence behind the decision. Keep a factual record of what was said and which work examples were given. If the decision feels discriminatory or the explanation remains unclear, use an appropriate HR channel, employee representative, or qualified adviser in your jurisdiction. The verdict is simple: accept a specific observation as something to examine, not as proof of a fixed cause; agree on an action and review point; and question a formal decision that relies on a personality label without a clear job-related basis.
Sources: The Uniform Guidelines on Employee Selection Procedures: Federal Guidance for Merit-Based Employment Decisions; Section 15: Race and Color Discrimination
Sources and notes
- “This is not a test”: How do human resource development professionals use personality tests as tools of their professional practice?
The accessible publisher abstract reports grounded-theory and inductive analysis of semistructured interviews with 18 HRD professionals. Pattern analysis identified six strategies for personality-test use—ethical-protective, scientific-selective, cautious-avoiding, cautious-embracing, user friendly-pragmatic, and knowledgeable-accommodating—and recurring cognitive dissonance and paradoxical situations. This small qualitative study does not estimate prevalence, document stereotyping cases, or establish the effectiveness of any feedback script.
- The Uniform Guidelines on Employee Selection Procedures: Federal Guidance for Merit-Based Employment Decisions
SIOP's December 2025 professional statement recommends job analysis, appropriate validation strategies, and documentation of reliability, validity, and job-relatedness for employment selection procedures.
- Section 15: Race and Color Discrimination
The EEOC guidance describes the conditional Title VII disparate-impact framework and uses a personality test for identifying management potential as an example when the test has significant disparate impact based on race or another protected trait.
Apply it to your work
Turn a broad work-style label into a question you can observe
From this guide: If the feedback leaves you unsure which part reflects a recurring tendency and which part came from the situation, compare the decision, evidence, planning, conflict, and collaboration patterns you want to examine.
The Work Pattern Report offers a private, low-stakes self-report across ten work continuums, including decisions, evidence, planning, conflict, collaboration, and change. It can help you name patterns to reflect on before a follow-up conversation, while the manager’s concrete examples and the conditions around the work still need to be considered separately. It provides no norms or employment recommendation.