Two Competing Work Tendencies Before a Difficult Collaboration

What should you do with two competing work tendencies before a difficult collaboration?

Before a difficult collaboration, treat each work tendency in your report as a provisional clue, not a verdict about either person. Check what the report measures, translate both descriptions into observable actions under particular work conditions, and compare them with episodes. Then agree on one behavior and a signal to review together. Prepare for the work; do not decide which tendency is the “real” you. Start with the task. Is the decision unclear? Is there a deadline or unresolved dependency? A broad description does not specify what you will do in this meeting. “I like to consider options” and “I prefer to decide promptly” may suggest different actions, but do not establish a conflict in every task. Gathering input might reveal a missing constraint; deciding promptly might matter when time is short. Check possibilities against report definitions and episodes, not as conclusions about scores. The instrument and scales are unspecified, so wording alone cannot establish what either score means, how precise it is, or whether descriptions are comparable. Do not infer a percentile, reference group, or prediction of an exchange. The report can prompt questions; this sequence is an editorial framework, not a tested intervention. Translate each description into an action and identify when it could help or hinder the task. Compare past episodes, including one that challenges your interpretation. Belbin’s *Working Relationship reports* concern a different product. Its provider recommends discussing differences, finding work examples, and agreeing on a plan. This is provider guidance, not evidence that it validates another report or guarantees collaboration. Use what you learn to make one request. You might propose unresolved questions first, followed by a named decision owner and time to decide. Ask whether that fits the task and what the other person needs. You need not disclose a private report or assign a label. Agree on a visible signal, such as whether the owner and next step are clear. Choose one behavior to try; do not treat two tendencies as a forecast.

Sources: Belbin Working Relationship reports

What does the report's wording and score actually establish?

Only the instrument documentation can show what a report’s scale names, score format, comparison group, and intended interpretation mean. Two descriptions that sound opposed may refer to different constructs or different parts of a report. Without those details, you cannot tell whether the language describes a measured score, a broad summary, or an interpretation layered on top of the score. So begin with the report’s own definitions, not with the everyday meaning of words such as “careful,” “flexible,” or “decisive.” First identify what kind of number, if any, appears beside each tendency. A raw score is the result on the instrument’s original scale. A standardized score has been transformed onto a defined scale, while a percentile states the share of a specified comparison group whose scores fall at or below a point. A norm is that reference group used to interpret a score. These formats answer different questions: a percentile is not the percentage of situations in which a tendency appears. Its meaning depends on the documented comparison group. Then check whether the two phrases name the same scale, different scales, or a scale and a narrative interpretation. They may sound inconsistent in ordinary conversation while referring to separate measured dimensions. The wording alone does not show how scores were calculated or whether a difference matters. Check whether documentation defines each scale and explains how scores inform its descriptions. If it does not, preserve that uncertainty: “these descriptions point to two questions I can examine” is more defensible than “my report proves I am contradictory.” Also separate reliability from validity. Reliability concerns the consistency or precision of scores under specified conditions; validity concerns the evidence for a particular interpretation and use. A report’s polished wording establishes neither. ISO 10667-1:2020 says assessment quality, including relevance, validity, reliability, fairness, and standardization, matters in relation to the assessment’s purpose and conditions. Its abstract is broad guidance, not an evaluation of this instrument. The U.S. Office of Personnel Management’s “Personality Tests” guidance likewise treats personality assessment in a specific employment-selection context; it cannot validate a private report or establish what its scores mean. Before the collaboration, write down the two exact scale names, score types, stated reference group, version, purpose, and any explanation of uncertainty or measurement error. If a detail is absent, mark it unknown. Use the phrases as prompts for observable questions about the work, not as precise or predictive facts about how you or a colleague will behave.

Sources: ISO 10667-1:2020; Personality Tests

Why can two tendencies coexist in the same person?

A person can show different behaviors as task demands change. A broad tendency does not require the same action in every episode. Two opposed phrases may describe useful responses at different moments, different scales, or wording too loose to compare. Context is plausible, not proof. A trait is a relatively broad pattern of tendency; a state is a momentary expression in a particular situation. The distinction helps because a tendency is not a script for every meeting. Imagine a shared task with an uncertain requirement and a firm deadline. Asking a colleague for input early might surface a consequential omission. Later, closing the discussion and assigning a decision time might keep the work moving. “Seek input” and “decide promptly” need not compete if they apply to different phases of the same task. Ask what each action serves, and when. That sequence would not resolve every conflict. If two people must choose incompatible options at the same moment, or if consultation itself consumes the remaining decision time, the demands may be in genuine tension. The task may require a tradeoff: accept less input to meet a deadline, or delay to avoid a costly error. Calling both responses “strengths” does not remove that cost. The report cannot say which cost matters more; that depends on consequences, authority, and available information. Research makes context a reasonable question to ask, while leaving an individual prediction out of reach. In “Beyond Personality Traits: A Study of Personality States and Situational Contingencies in Customer Service Jobs,” researchers followed 56 customer-service employees over ten workdays. They reported that task immediacy was associated with momentary conscientiousness, while the other party’s friendliness was associated with momentary extraversion and agreeableness. This customer-service study does not show how a reader with an unspecified report will behave in a difficult collaboration. “Distinguishing Four Types of Person × Situation Interactions” reports two preregistered online studies, with 622 and 818 participants responding to standardized pictures or first-person videos. The researchers found broad person-by-situation variation in personality states, but specific trait-by-situation effects were significant yet very small. Thus, behavior may vary with situations while a particular trait label says little about a specific response. The studies were not workplace collaboration tests and do not validate this report. The MIT Collaboration Toolbox’s discussion of conflict modes likewise says the usefulness of a mode depends on the conflict’s requirements and the skill with which it is used. That is educational guidance about its named framework, not evidence that every report tendency is interchangeable or that a particular tactic will work. Together, the sources support asking what the task needs during exploration, decision, and handoff. They do not support averaging the two tendencies or suppressing one. Check whether actions can be sequenced; otherwise name the tradeoff and decide by the task’s consequences.

Sources: Situation and Personality at Work: An Experience-Sampling Study of the Role of Situational Characteristics in the Expression of the Big Five; Distinguishing Four Types of Person × Situation Interactions; Collaboration Toolbox: Conflict Management

What does workplace evidence say about traits, states, and situations?

Workplace research supports keeping three kinds of information separate: a person’s broad tendencies, their momentary behavior, and the features of the situation. It does not show that an unspecified personality report can forecast how two colleagues will handle one difficult collaboration. The studies examine particular measures, populations, and outcomes. Their findings can guide better questions about context, but applying them to this reader’s report or meeting would be an inference. A 2024 preregistered study, “Distinguishing Four Types of Person × Situation Interactions,” helps explain why apparently mixed findings need not conflict. In two online studies of 622 and 818 participants, people responded to standardized pictures and first-person videos while researchers measured Big Five traits, situation characteristics, and personality states. The authors found substantial broad person-by-situation variation in states and meaningful individual differences in how situation characteristics related to states. Yet the specific interactions between particular traits and situation characteristics were significant but very small. In other words, people can differ in their responses across situations without a simple rule such as “this trait means this person will act differently in this specific kind of situation.” The studies used standardized online stimuli and measured states, not workplace collaboration outcomes; they cannot tell a reader which tendency will appear in a meeting. A study of teachers examined a different question: how traits, momentary states, situation characteristics, and their interactions related to momentary job performance. During 13 or 14 days, 173 teachers, 98 supervisors, and students in 69 classes provided repeated ratings. The study reported associations between traits, states, situation characteristics, and performance. With one exception, it found no statistically significant interactions in the tested models. This does not mean situations never matter, nor that traits and circumstances operate independently in every setting. It means that in this teaching sample, the measured main effects were more consistent than the particular interaction effects tested. Teacher internships and performance ratings are also a long way from validating an unspecified report as a prediction tool for a pair of coworkers. The 2026 narrative review “Personality states at work” identified 33 studies and describes this as an emerging, fragmented area, with varied frameworks, measures, and designs. That review helps explain why a single result should not be turned into a universal workplace rule. The teacher study’s limited interactions and the online studies’ broad person-by-situation variation address different levels of analysis: overall variability across people and situations is not the same as a reliable, specific trait-by-situation prediction. For a difficult collaboration, an unclear owner, decision authority, deadline, incentive, or missing information may explain behavior more immediately than either tendency in a report. That is a practical alternative to check, not a result these studies establish about the reader’s situation. Use the research to ask what the task demands, what is uncertain, and what behavior is observable. It supports treating person and context as distinct clues; it does not settle which clue will matter most in one meeting.

Sources: Understanding Person-Situation Dynamics at Work; Distinguishing Four Types of Person × Situation Interactions; Personality states at work

What is a fair comparison between the report and your work episodes?

A fair comparison starts by turning each report phrase into a prediction you could check, rather than searching memory for proof that the label is true. For each tendency, write down a visible action, the work condition in which you expect it, and an episode that might count against it. “I value input,” for example, is broad; “when a decision has an unresolved dependency, I ask the affected person before committing” names an action and a condition. The second tendency needs the same treatment. Do not assume the phrases describe opposite ends of one scale unless the report defines them that way. Use more than one episode, and record the setting before interpreting the behavior: the task, deadline, decision owner, people involved, available information, and outcome. Then keep three questions separate: What did I do? What did I think was driving it? Did it help the work? The third may depend on other people’s needs or constraints, not just your intention. These notes are self-observation, not an independent test of the report or proof that the behavior is stable. An invented worksheet row might read: “Deadline unclear; asked for more input; decision was delayed.” This records a possible cost, not a flaw. A second row could read: “A key dependency was missing; checked with its owner; avoided reopening the decision later.” It cannot validate the report or show that asking always prevents rework. Look for a counterexample too: a time when you made a sound decision without further input, or when consultation did not resolve the uncertainty. The provider page for Belbin Working Relationship reports recommends using its paired Team Role report as a discussion document: consider similarities and differences, look for supporting examples from work together, then discuss a future plan. This offers a comparison for examining report language. It is guidance from the provider about its own product, not independent evidence that the method works for every personality assessment or that one report can explain a pair’s behavior. Workplace findings also counsel against treating a tendency as a direct forecast. In a 13- or 14-day study of 173 student teachers, with ratings from supervisors and students as well as teachers’ own ratings, “Understanding Person-Situation Dynamics at Work” found associations between traits, momentary states, situation characteristics, and momentary performance; nearly all tested trait-by-situation and trait-by-state interactions were not statistically significant. Those ratings do not validate this unspecified report or predict a difficult collaboration. The practical result is two checkable predictions, a counterexample to seek, and a clearer question about what the task actually requires.

Sources: Belbin Working Relationship reports; Understanding Person-Situation Dynamics at Work

How can you tell a tendency conflict from a work-design problem?

Before calling a collaboration problem a personality clash, check the work conditions that could produce the same behavior. Who owns the deliverable? Who has authority to decide, and when is input required? What deadline, success criteria, information, resources, and incentives are in play? A general personality report cannot separate these causes. The question is whether a tendency explains this episode better than a specific constraint does. Consider waiting for more input. Under an unclear decision rule, a person may keep consulting because no one has said who decides or what evidence is enough. Under a tight deadline, the same delay may reflect a preference for reducing uncertainty, but it may also be a response to missing information or real risk. Conversely, a quick decision can look dismissive when colleagues have no agreed chance to raise dependencies. It may instead be an attempt to meet a deadline for which that person is accountable. These are illustrations, not diagnoses: visible action alone does not establish its cause or a stable tendency. A useful comparison sets two explanations beside observable facts. The personality hypothesis asks whether the action fits a report phrase across more than one relevant episode and under identifiable demands. The work-design hypothesis asks whether ownership, authority, criteria, information, or resources were unclear, and whether friction changes when that condition changes. A report cannot decide between them. Look for details that could challenge each account: a clear decision owner who still receives no input, or a missing dependency that explains why a usually decisive person paused. Treat remembered episodes as clues, not proof. The workplace study “Understanding Person-Situation Dynamics at Work” followed teachers twice daily over 13 or 14 days. Teachers, supervisors, and students rated momentary teaching performance; analyses found contributions from traits, momentary states, and situation characteristics, while nearly all tested trait-by-situation and trait-by-state interactions were not statistically significant. This supports keeping person and situation in view together, but its teaching context and performance ratings do not tell you what caused a particular disagreement or validate your report’s predictions. The findings caution against assuming a trait explanation automatically wins whenever behavior seems familiar. If evidence points to a work condition, address it directly: name an owner, set the decision rule, identify missing information or resources, or agree on a deadline. If conditions are clear and a recurring behavior still matters, make a specific request about the work, without presenting a report label as its cause. ISO 10667-1:2020 frames work-related assessment around its rationale, conditions, approach, and decisions about results; its public abstract is guidance about assessment use, not a way to diagnose this collaboration. This distinction matters because changing a process may resolve friction that a personality explanation would leave untouched.

Sources: ISO 10667-1:2020; Understanding Person-Situation Dynamics at Work

What working agreement can you make before the meeting?

A useful working agreement names a shared result, one behavior, when it should happen, and a signal both people can review. The Belbin Working Relationship reports page recommends using its paired report as a discussion document: explore differences, consider supporting examples from work together, and agree on a future plan. This is provider guidance for a specific Belbin product, not evidence that every personality report predicts a relationship or that the format has been tested here. Start with the task in neutral terms: “We need to decide which changes go into the client draft by Thursday.” Then name the difficult condition without casting either person as the problem. Perhaps unresolved dependencies invite more questions, while the deadline creates pressure to close the decision. Turn both tendencies into a timed request: “Let’s surface the dependency before we lock the draft, and set a point when we decide with the information available.” Inquiry and closure now serve different phases. This is not a forced midpoint between “ask more” and “decide now”; the sequence depends on which information matters and who has authority. Invite the collaborator to identify what the plan misses: “What would you need to contribute before that decision?” Agree who must be consulted, who owns the final call, and what happens if an answer is still missing at decision time. A review signal could be whether each unresolved item has a named owner and dated next check-in. These signals describe the work, not whose style is correct. If authority is unclear, resolve that separately; a personality description cannot assign decision rights. The MIT Collaboration Toolbox’s conflict-management material makes a related contextual point about its own modes: no single mode is universally right, and usefulness depends on the specific conflict and the skill with which a mode is used. That page concerns a particular framework, so it does not validate tendencies in an unspecified report. Nor should every disagreement be settled by splitting the difference. If one option carries a material risk or the decision belongs to one role, a midpoint may hide the actual need. Keep the agreement small enough to try: state the shared outcome, name when to pause or decide, invite missing input, assign the decision, and choose one visible follow-up signal to review together. Afterward, compare that signal with the task result and revise the sequence if needed. This is a practical coordination proposal, not a proven intervention.

Sources: Belbin Working Relationship reports; Collaboration Toolbox: Conflict Management

What can a short preparation plan reasonably change?

A plan can clarify what you will ask for, when you will make a decision, and how you will tell whether the next step is clear. It cannot ensure that you feel calm, that your collaborator agrees, or that the work goes well. Treat preparation as a way to make your contribution observable and the coordination request easier to answer, not as a technique that controls another person’s response. There is a useful counterweight to claims that planning reliably improves difficult conversations. The West Virginia University dissertation “Exploring the Effects of Implementation Intentions and Goal Formation on Anxiety and Communication Effectiveness when Discussing Difficult Interpersonal Topics” reports an experiment with 182 participants assigned to implementation-intention, goal-formation, or no-message control conditions. Participants identified difficult topics and recorded a message two weeks later. The abstract reports no effect of planning on state anxiety, self-rated communication effectiveness, or motivation. Participants in the goal-formation condition produced shorter messages than the control group; that result does not establish that the messages were clearer or more effective. This dissertation studied non-work interpersonal discussions, not personality reports, workplace meetings, or the preparation sequence proposed here. It challenges a promise of better outcomes, while leaving open whether a specific work agreement helps people coordinate. Keep process control separate from outcome control. You can propose a sequence, ask who owns a decision, name information still needed, and suggest a time to revisit the issue. You cannot decide whether the other person will respond constructively or whether external constraints will allow the plan to work. Before a deadline discussion, for example, ask which unresolved dependency needs input, agree on a decision time, and identify who will decide if information is still missing. A modest success signal is that the owner and next check-in are explicit. Agreement and a successful deliverable depend on more than your preparation. The evidence that would justify a more confident recommendation is specific. Repeated observations across your own work episodes could show whether a behavior helps under a particular condition, though they would remain personal observations rather than proof about a stable trait. The instrument’s manual could establish what its scales and scores support, for its documented version, population, and intended use. A formal assessment intended for an employment decision would need evidence tied to that decision and role. The U.S. Office of Personnel Management’s “Personality Tests” guidance discusses assessment in selection and notes that which factors predict performance depends on the job. That guidance does not validate an unspecified report for informal collaboration or turn a self-reflection score into a job judgment. For the next meeting, choose one action, its cue, and a review point. A practical test is whether the collaboration ends with an explicit owner and next check-in, even if disagreement remains. If the plan does not help, inspect task conditions, authority, or missing information before treating the result as evidence that one tendency is the problem.

Sources: Exploring the Effects of Implementation Intentions and Goal Formation on Anxiety and Communication Effectiveness when Discussing Difficult Interpersonal Topics; Personality Tests

What is the next step after the collaboration?

After the collaboration, compare what happened with the behavior you agreed to try and the work signal you chose to watch. Was a decision owner clear? Did the next check-in happen? They show whether the agreement supported this task, not whether a broad personality tendency caused the outcome. Keep the behavior if it helped. Revise it if the task changed. If friction continued, examine authority, information, or resources before treating it as a personal failing. End with one adjustment for next time, not a verdict about either person.

Use the report as a prompt for self-reflection or appropriately scoped coaching, not as a diagnosis. ISO 10667-1:2020 frames work-related assessment around purpose, conditions, approach, and use; its broad guidance does not establish what an unspecified report predicts. The U.S. Office of Personnel Management’s personality-test guidance concerns employment selection and emphasizes job relevance and measure-specific evidence. It does not make a general self-report a hiring recommendation or a way to judge a colleague.

If you want prompts about your decision and collaboration tendencies, the live Work Pattern Report is a low-stakes reflection tool. It has no norm, cutoff, type, or selection score, and is not validated for career matching or hiring. It cannot resolve the collaboration . Carry one observation or agreement into the next task, then judge it by what happened.

Sources: ISO 10667-1:2020; Personality Tests

Questions readers ask