The Culture Paradox: Why Hidden Patterns Keep Organizations Stuck and Good Conflict Sets Them Free, with Jamie Notter

Jamie Notter is a speaker, author, consultant and culture scientist. He started in conflict resolution, took a master's in conflict analysis and resolution from George Mason, worked internationally for six years, then spent twenty-five years running his own consulting firm. He also holds a certificate in organization development from Georgetown, where he served as adjunct faculty.

The turn to culture came from frustration. He kept hearing that culture was vague, squishy, too complex to understand and slow to shift. One CEO told him it takes a minimum of eight years to change a culture. He disagreed, built a definition he could actually manage against, and in 2016 co-created a culture assessment with his partner Maddie that has since gathered more than a million data points.

What that data shows is the premise of this episode. Culture work stalls for a reason most leaders never see, because it is invisible from inside the organisation. And the fix is not more collaboration or better values. It is conflict, done properly.

Competing commitments, and why culture work stalls

Every organisation Jamie visits wants collaboration and believes it is essential. What they also have, and do not name, is a competing commitment to the autonomy of subgroups. Marketing should get to make marketing decisions. That is reasonable, and pushed hard enough it produces exactly the silos everyone says they do not want.

He offers a personal version of the same shape: you are committed to a full life and you are committed to doing well at work. Both are fine. Push too hard on the second and things quietly fall on the first. The organisational version is no different, and the consequence is that leaders misread the symptom as a person. Jamie is bad at collaborating. Those two departments do not like each other. As he puts it, if you misdiagnose the source, all of your solutions fail.

The big four patterns

The assessment measures eight things, and there is a pattern for each. Four come up most often, and they are the ones where clients look at the data and say that is us.

Collaboration. Organisations genuinely value collaborative individuals. Helping each other one to one is present and real. Collaborative groups are much less present, and that imbalance is invisible because you can see people collaborating everywhere.

Incomplete innovation. Cultures value the concept of innovation more than the practice. Creativity and thinking about the future are fully there. Running an experiment that might fail is not, because the competing commitment is appearing competent. You cannot have the right answer all the time and also innovate.

Heavy agility. Valuing moving forward and valuing quality, but never stopping to fix or retire what no longer adds value, so everything gets dragged along.

Lagging transparency. Reactive sharing is valued, proactive sharing is not. Ask and you will be told. Nobody puts the information out before you need it, so it arrives too little and too late.

Gridlock, and the AI experiments nobody mentions

The gridlock metaphor is a driver edging into a junction on a yellow light. Every individual decision felt logical and in your own interest. Together they produce an outcome nobody can move through.

Jamie's current example is AI. Every department is running its own experiments and telling nobody, because admitting an experiment failed reads as a risk while repeating what you already knew how to do gets a well done. He has watched three departments separately build AI prototypes on the same data, then arrive at IT one by one to have it built properly, at which point IT points out it is one tool, not three, and they should have been talking six months earlier. Six months, as he puts it, is a long time in AI years.

Good conflict and bad conflict

Conflict is not the failure state. There is no relationship on the planet that does not have conflict in it, and conflict is how creativity, new ideas and growth happen. Adults only develop by hitting the gap between how they see the world and how it is, and resolving it.

The data backs the link. Across sixty-four things measured in the culture dataset, the two with the strongest correlation are managing conflict and embracing change. You do not do change if you do not do conflict.

Good conflict is the right issues dealt with by the right people at the right time, resolved well. Bad conflict is not shouting. It is a senior team spending an hour debating email wording, which is an hour spent avoiding the strategic conflict underneath it. It is also a senior team resolving something that will be implemented by a department that was never in the room.

Building a conflict system

Every organisation already has a conflict system, in the same way every organisation already has a culture, whether anyone designed it or not. There is an inherited set of processes and unwritten rules deciding which conflicts get aired, by whom, and when.

Jamie's design has four layers, and he is clear about where the effort belongs.

Capacity is the floor. Skills and training, and the easy answer most people reach for first. Do not raise a conflict you have no capacity to hold.

Processes are where the work is. Build a step into product development that forces a conversation with sales before it is too late to solve. Put a standing item on every team agenda: what is the conflict we are not talking about.

Governance rules decide routing. Write down that a conflict with a ten million dollar impact goes to the management team, or that if ninety percent of implementation sits with another department, that department is in the room. Write down that the senior team handles conflicts with strategic impact, so somebody can flag the hour being spent on email wording.

Accountability comes last, once the system exists, to check that resolutions are fair and no department is quietly favoured.

The clearest example is borrowed from a friend who works with nonprofit boards. Boards use a consent agenda to move the routine items in one block. His friend's response was to add a dissent agenda as the very next item: name the biggest conflict we need to have, second on the agenda, so if it takes the whole meeting there is a whole meeting left.

The one action for the next 90 days

Convene the senior team, and do not have a high-level conversation about culture. Facilitate one where they identify the behaviours they are engaging in that are the opposite of what they say they want.

That is where culture dies, in the contradictions. A team commits to a culture where conflict is welcome, and one of them has a star salesperson who steamrolls everyone, who nobody will challenge, and who keeps getting rewarded. Jamie's view is that culture belongs on the senior team's agenda once a quarter, with the people leader facilitating, because the senior team will not do the work of culture change but nothing survives without them behind it.

What listening platforms should be measuring

Start with what is, not with the ideal. Plenty of organisations define their ideal culture and set off towards it without establishing where they are standing, and you cannot move towards something if you do not know your position.

His advice on the data itself is specific. Satisfaction data asks whether people are happy. What he wants is where people felt thwarted, where they could have done better and did not. The core message of his engagement book is that engagement is not driven by happiness, it is driven by success, so the useful question is where success is breaking down.

He tells one story about a company that got red scores on agility and responded with an agility task force, which produced a slide deck whose last slide read do not just say you are agile, be agile. The score told them where to look. It did not tell them what to do, and nobody went and found out.