Most of us have had a coworker whose way of working makes absolutely no sense to us.
You send a rough idea because you want to kick it around. They reply with a detailed list of unanswered questions.
You schedule a brainstorming meeting. They would rather have the document the day before and think about it alone.
You want to make a decision and move on. Someone else wants to make sure everyone has been heard first.
It is easy to turn these differences into judgments. Too slow. Too impulsive. Too quiet. Too controlling. Too theoretical. Too focused on details.
Sometimes those judgments are right. People do have bad habits. But quite often, two capable people are simply approaching the same work from different directions.
Learning to recognize those differences can make work considerably less irritating. It can also make teams better.
Different does not automatically mean better
There is a tempting version of the diversity story that says a team full of different personalities will naturally outperform a team of similar people. The research is much less tidy.
A recent meta-analysis revisiting decades of research on Big Five personality traits and team performance found that the relationships were generally weak and highly dependent on context. Personality matters, but putting a particular mixture of personalities in a room does not guarantee a high-performing team. 1
Older meta-analyses have found some meaningful relationships between team composition and performance, particularly around traits such as conscientiousness and agreeableness, but those relationships also vary by setting and by the kind of work a team is doing. 2 3
That is useful context for any workplace personality or workstyle tool. The goal should not be to engineer a supposedly perfect team from personality labels.
A better goal is much more practical: help people understand how their coworkers tend to approach work so they can communicate and coordinate with fewer unnecessary surprises.
There is some particularly interesting research behind that idea.
Being understood changes what differences do to a team
In a longitudinal study of 83 work groups, Harvard researchers Jeffrey Polzer, Laurie Milton, and William Swann examined something they called interpersonal congruence: roughly, whether people in a group saw one another in ways that were consistent with how those people saw themselves.
The result was striking. Diversity tended to improve creative performance when interpersonal congruence was high, while diversity tended to hurt performance when it was low. The same pattern appeared in social integration, group identification, and relationship conflict. 4
That does not mean coworkers need to agree with one another or spend an afternoon exchanging personality labels.
It suggests something simpler: differences are easier to use when people have a reasonably accurate picture of the person on the other side of the table.
Think about a colleague who asks a lot of questions before committing to a plan. If you interpret that behavior as resistance, every question can become irritating. If you understand that this person generally wants to test assumptions before making a decision, the same behavior becomes predictable. You may even start sending them the assumptions in advance.
The behavior did not change. Your interpretation did.
The meeting where everyone thinks everyone else is the problem
Imagine four people starting a new project.
One wants to understand the system before deciding anything. Another immediately asks what can realistically be built by Friday. A third starts generating possibilities the group had not considered. The fourth wants to know how the decision will affect the people who have to live with it.
None of those instincts is automatically superior.
The problems begin when each person quietly assumes that their own instinct is what competent people are supposed to do.
The analytical person thinks the practical person is oversimplifying.
The practical person thinks the analytical person is turning a two-hour decision into a doctoral dissertation.
The explorer thinks everyone else is closing down ideas too early.
The relationship-focused colleague wonders why nobody seems to notice that the implementation team hates the proposal.
At that point, the team's differences are producing friction instead of information.
Research on teams has repeatedly found that the way information gets shared matters. A meta-analysis covering 72 independent studies, 4,795 groups, and more than 17,000 people found that information sharing was positively associated with team performance, cohesion, decision satisfaction, and knowledge integration. 5
That gives managers a useful question to ask: Are our differences helping more information reach the decision, or are they making people stop listening to one another?
Workstyle patterns are useful when they start a conversation
Behaviture's Workstyle Spectrum is being designed around this idea.
Rather than treating people as one of a handful of rigid personality types, it measures continuous workstyle facets and then uses memorable patterns as a simple way to talk about the overall profile. Someone might resemble a Systems Strategist, Practical Builder, Insight Explorer, Precision Planner, Social Catalyst, Thoughtful Connector, Focused Expert, or Adaptive Improviser.
The names are shorthand. They are not diagnoses, job qualifications, or predictions of performance.
That distinction matters because people are rarely as neat as a label.
A Systems Strategist may also have a strong Insight Explorer influence. A Social Catalyst can still enjoy deep individual work. A Precision Planner may be highly adaptable when circumstances actually change. Someone may not fit one pattern closely at all.
The useful question is not, "What type are you?"
It is, "What might I understand about working with you that I would otherwise learn the hard way?"
Consider a few everyday pairings
Take a Systems Strategist working with a Practical Builder.
The strategist may naturally ask whether the team is solving the right problem and how the pieces fit together. The builder may want to turn the discussion into something workable and test it.
That combination can be excellent. It can also produce the familiar exchange:
"We're not ready to build this yet."
followed by:
"We're never going to learn anything until we build something."
A simple working agreement can help: let the strategist identify the assumptions that would make the prototype misleading, then let the builder create the smallest test that can answer them.
Now put a Precision Planner with an Adaptive Improviser.
One may be happiest when responsibilities, dependencies, and deadlines are settled. The other may do some of their best work when there is room to adjust as new information arrives.
The answer is probably not to convince one of them to become the other. It may be to agree on what must remain stable and what is deliberately flexible.
Or consider a Social Catalyst and a Focused Expert.
One may develop ideas through conversation and rapid feedback. The other may need uninterrupted concentration before they have anything useful to say. A manager who treats the first style as engagement and the second as disengagement can easily mishandle the quieter employee.
A better routine might be almost embarrassingly simple: send the question before the meeting, give people some thinking time, then use the meeting for discussion.
These examples are illustrations based on the workstyle patterns, not scientific claims that two labels predict how a pair will behave. Actual people have much richer profiles than their closest pattern.
Psychological safety determines whether differences become visible
Understanding workstyles is difficult if people do not feel comfortable showing how they actually think.
Amy Edmondson's foundational research on psychological safety studied 51 work teams and found that psychological safety was associated with learning behavior, which in turn was connected with team performance. Psychological safety is essentially the shared belief that a team is safe for interpersonal risk-taking: asking a question, admitting uncertainty, raising a concern, or saying that an idea may not work. 6
Google reached a similar conclusion in its Project Aristotle research. After studying hundreds of variables across its teams, Google reported that team effectiveness depended more on how the team worked together than on simply who was on it. Psychological safety was the most important dynamic identified in that research. 7
This matters for workstyle differences because a team can accidentally reward only one way of participating.
If meetings move quickly and the loudest person usually wins, colleagues who prefer reflection may stop contributing.
If every proposal is subjected to a long analytical cross-examination, people who generate ideas experimentally may stop bringing half-formed possibilities.
If disagreement is interpreted as disloyalty, direct colleagues learn to stay quiet.
If avoiding conflict is treated as politeness, important problems can survive for months.
A healthy team does not need everyone to communicate the same way. It needs enough safety and structure for different people to contribute what they know.
The best teams also stop and examine how they are working
There is another body of research that is particularly relevant here: team reflexivity.
Reflexivity simply means that a team periodically examines its goals, methods, and working processes and adjusts them when needed. A 2024 meta-analysis found that team reflexivity was associated with better team performance, although the size of the benefit varied by factors such as team size and tenure. The researchers also found that leaders who encourage participation in discussion and decision-making can promote reflexivity partly by supporting psychological safety. 8
This is where a workstyle assessment can become more useful than a colorful result card.
Instead of ending with:
"Alex is an Adaptive Improviser."
a team can ask:
- Where do we naturally approach work in similar ways?
- Where do we approach it differently?
- Which differences are useful?
- Which ones repeatedly create friction?
- What small change to our meetings, planning, feedback, or decision process would help?
That last question is important. The assessment should lead back to actual work.
Managers should be careful not to turn understanding into stereotyping
There is an obvious danger here.
Once people have memorable labels, those labels can become shortcuts.
"Of course she missed the deadline. She's an Improviser."
"Don't ask him to present. He's a Focused Expert."
"She should lead this because she's a Social Catalyst."
That is exactly the wrong use.
Personality and workstyle describe tendencies, not capabilities or fixed behavior. People also change their behavior substantially across situations. A colleague can prefer structure and still respond brilliantly to a crisis. Someone who generally likes independent work can be excellent with clients. A person who enjoys brainstorming can also run an extremely disciplined project.
The newest meta-analytic evidence is a useful reality check: personality composition by itself explains only a limited amount of team performance. 1
The patterns should help a team become curious about one another, not more certain about one another.
Difference becomes useful when teams know what to do with it
Harvard Business Review has been writing about this problem for decades. A recent 2026 article on team dynamics makes the point plainly: differences can create value, but leaders have to manage the friction that comes with different perspectives. 9
That is probably the most useful way to think about workstyle differences.
The coworker who slows down your decision may notice a risk you missed.
The colleague who wants to move faster may expose the fact that your team is studying a problem it could cheaply test.
The person who keeps asking how others will react may be protecting an implementation from failing socially.
The person who insists on quiet thinking time may come back tomorrow with the solution everyone missed in the meeting.
You do not have to work the same way to work well together.
You do need to understand enough about one another to recognize when a different approach is adding value — and when you need to adjust how the team works.
That can start with something as simple as comparing how each person prefers to think, plan, communicate, and respond when the work gets messy.
Try the Behaviture Workstyle Spectrum
Behaviture Workstyle Spectrum is a free workstyle assessment designed to help people understand how they tend to approach thinking, collaboration, planning, and problem-solving.
The assessment uses continuous workstyle dimensions rather than forcing everyone into rigid personality boxes. The pattern names make the results easy to discuss, while the underlying profile preserves the differences that make people more interesting than a four-letter code.
Individuals can compare results with a colleague, and teams can use the assessment to start a practical conversation about how they work together.
Workstyle Spectrum is a beta self-reflection and team-development tool. It is not designed to measure job performance, diagnose personality, or make hiring, promotion, compensation, or other employment decisions.
Sources and further reading
- Han, A., Krieger, F., Kim, S., Nixon, N., & Greiff, S. (2024). Revisiting the relationship between team members' personality and their team's performance: A meta-analysis. Journal of Research in Personality. https://doi.org/10.1016/j.jrp.2024.104526
- Bell, S. T. (2007). Deep-level composition variables as predictors of team performance: A meta-analysis. Journal of Applied Psychology, 92(3), 595–615. https://doi.org/10.1037/0021-9010.92.3.595
- Peeters, M. A. G., van Tuijl, H. F. J. M., Rutte, C. G., & Reymen, I. M. M. J. (2006). Personality and team performance: A meta-analysis. European Journal of Personality, 20(5), 377–396. https://doi.org/10.1002/per.588
- Polzer, J. T., Milton, L. P., & Swann, W. B. Jr. (2002). Capitalizing on diversity: Interpersonal congruence in small work groups. Administrative Science Quarterly, 47(2), 296–324. https://doi.org/10.2307/3094807
- Mesmer-Magnus, J. R., & DeChurch, L. A. (2009). Information sharing and team performance: A meta-analysis. Journal of Applied Psychology, 94(2), 535–546. https://doi.org/10.1037/a0013773
- Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999
- Google re:Work. Understand team effectiveness (Project Aristotle). https://rework.withgoogle.com/en/guides/understanding-team-effectiveness
- Booms, M. C., de Jong, B., & Schippers, M. C. (2024). A meta-analysis of team reflexivity: Antecedents, outcomes, and boundary conditions. Human Resource Management Review, 34(4), 101042. https://doi.org/10.1016/j.hrmr.2024.101042
- Brady, S. M., Kliman, S. D., & Smith, L. C. (2026). 4 Hidden Traps of Team Dynamics. Harvard Business Review, July 15, 2026. https://hbr.org/2026/07/4-hidden-traps-of-team-dynamics