You're in a meeting where everyone agrees on the goal, but no one can agree on how to get there. One person wants to move fast and test ideas. Another needs certainty before committing resources. A third cares most about whether the solution will be fair to everyone involved. The conversation stalls. You leave thinking the team isn't aligned, but alignment isn't really the problem.
What Everyone Gets Wrong About Collaboration
Most people believe that good collaboration means everyone shares the same values, or at least that everyone can learn to prioritize the same things if they just communicate better. This belief runs deep. We talk about "getting on the same page," finding "common ground," and building teams where people "want the same things." It makes intuitive sense: if everyone valued speed and efficiency equally, disagreements would evaporate. If everyone cared most about fairness, conflicts would resolve themselves.
This myth persists because collaboration does require some shared ground. You can't work together on something you disagree about fundamentally. But the mistake is thinking that shared values means identical values or that value differences are problems to solve rather than tensions to manage. Psychologist Shalom Schwartz, whose cross-cultural research on human values has been replicated across 80+ countries since 1992, showed something more precise: values don't exist in isolation. They form a system where some values naturally support each other and others naturally oppose each other. In Schwartz's circumplex model, adjacent values are compatible, but opposite values pull in different directions. This isn't a design flaw. It's how values actually work.
A Team Where Everyone Agrees on the Goal
A product team at a growing company is tasked with building a new feature. The deadline is tight. Four people are involved. The lead designer values innovation and autonomy—she wants to explore new approaches and make decisions without layers of approval. The operations person values security and stability—he needs clear processes, documented decisions, and ways to mitigate risk. The junior developer values achievement and competence—she wants to build something that works well and that she can point to as her own contribution. The manager values benevolence and belonging—she's focused on making sure everyone feels heard and that the team stays cohesive.
They all want the feature shipped and they all want it to be good. But within a week, the designer and operations person are frustrated with each other. The designer sees the operations person as bureaucratic and slow. The operations person sees the designer as reckless. Meanwhile, the junior developer is quiet in meetings, hesitant to push back on either side. The manager tries to make everyone happy and ends up satisfying no one. The team isn't misaligned on the goal. They're experiencing value tension—the natural friction that occurs when people are organized around different priorities.
The common response is to treat this as a communication problem. "Let's have a values workshop." "Let's do a personality assessment so we understand each other better." These help, but they miss the core issue. The operations person will never value innovation as much as security. The designer will never be as comfortable with process as the operations person is. That's not a failure of communication. That's the structure of their values, and it's probably permanent.
What Is Actually Going On
Schwartz's research shows that values exist in a dynamic relationship. Some values are adjacent and mutually reinforcing—competence and achievement support each other, for instance. But other values sit opposite each other in the circumplex. Stimulation and tradition are opposed. Power and universalism are opposed. Innovation and security are opposed. This opposition isn't arbitrary. It reflects a genuine trade-off: to move toward one, you must move away from the other. You cannot simultaneously maximize experimentation and control. You cannot prioritize both individual autonomy and group harmony without making a real choice about which one comes first in a given situation.
Effective collaboration doesn't require erasing this structure. It requires understanding it and working within it. The team that succeeds isn't the one where everyone has the same values. It's the one where people understand which values are in tension and have explicit agreements about how to make trade-offs. The designer's need for innovation and the operations person's need for security aren't opponents. They're constraints that need to be honored separately, not resolved into a single approach.
This reframe changes what you're actually trying to do. Instead of seeking perfect alignment or trying to persuade people that your values matter more, you're mapping the value landscape and creating decision rules for when each value gets priority. The designer might lead on the user experience but accept structured code reviews. The operations person might accept some exploratory work if it's time-boxed and documented. These aren't compromises that leave everyone half-satisfied. They're genuine acknowledgments that different things matter and different people are right to care about them.
What Changes When You See It Clearly
Once you see the value structure, you stop wasting energy on false solutions. You don't try to convince the security-minded person that speed matters more—you accept that it doesn't to them and work around it. You don't wait for everyone to want the same thing before moving forward. You make explicit decisions: "On this decision, we're prioritizing innovation. On that one, we're prioritizing stability." This doesn't eliminate friction, but it makes friction productive instead of exhausting. People stop feeling unheard because their values are acknowledged even when they don't win the particular decision.
The other shift is that you start picking team composition more strategically. A team full of people who all value speed and autonomy will move fast and miss risks. A team full of people who value stability and harmony will move slowly and miss opportunities. Tension isn't a sign of bad team fit. It's a sign that the team has the diversity it needs to make good decisions. The conflict between innovation and security isn't something to eliminate. It's something to structure.
The My Values assessment surfaces your core values, ranks them, and shows you where you're living them and where you're not—which helps you understand your own value structure before trying to map it across a team.
How do I know if value differences are a real problem or just a difference in style?
Real problems show up as repeated conflicts over the same type of decision, with the same people on different sides each time. If one person always wants to move faster and another always wants more process, that's value tension. If it's situational or rare, it's likely a style difference. Value tension is consistent because values are stable—they don't change because you've had one good conversation.
Can people with opposite values actually collaborate effectively?
Yes, but it requires explicit agreement about how to make trade-offs. Schwartz's research across cultures shows that value opposites exist everywhere—all teams have them. The teams that work are the ones that treat opposite values as constraints to honor separately, not problems to solve. You acknowledge both matter, then decide which one gets priority for each decision.
What if someone's values are completely incompatible with the team's mission?
That's different from value tension. If someone prioritizes power and hierarchy on a team built around autonomy and collaboration, or if someone prioritizes tradition on a team built to innovate, there's a genuine misalignment. Value tension is normal. Mission misalignment is a real hiring or team composition problem. The distinction matters because you can manage tension; you can't manage misalignment.
How do I talk to my team about value differences without it becoming a conflict?
Name the values, not the people. Instead of "You're too cautious," try "Security is clearly important to you in this decision." Acknowledge that the value is legitimate. Then make the trade-off visible: "For this project, we're prioritizing speed. That means we're accepting some risk. Here's what we're monitoring." This frames it as a structural choice, not a judgment about who's right.