Dear courageous leaders,
I have been thinking lately about the difference between a team that is quiet and a team that is safe. They can look identical from the head of the table.
In the quiet team, the meeting runs smoothly. People nod. Decisions get made without much friction. The leader leaves feeling aligned. However, the Analysis person has stopped raising the medium and longer-term strategic questions no one wants to hear, the Connection person has stopped naming what team morale looks like, and the Structure person has quietly decided it is not worth being the one who slows things down again by surfacing structural blind spots and risks. The smoothness is not agreement. It is disengagement.
In the safe, trusting team, there is more friction, not less. People disagree out loud. The conversation takes longer. The decisions that come out the other side actually hold, because every value in the room got to shape them before they were made.
This is the last edition in this arc, and it is the one I most wanted to write, because it is where the work actually pays off. We started with self-awareness, noticing when one of your own strengths gets loud enough to distort your leadership. We moved to relational awareness, reading the values driving the people across the table so you can meet them where they are. This edition is about the room itself. What it takes to build a team where all four codes can speak, and why that, more than any single decision, is the thing that compounds.
The Lens
If you have followed this arc, you know I think of our influence code as an operating system, and you know the four codes by now: Structure, Connection, Momentum, and Analysis. Each holds a different focal point, each protects a different set of values, and all four are necessary.
Here is the hard truth about teams. Conflict between codes is rarely about personality. It is about values meeting at cross-purposes, where each code's value can be read as a threat to another's. Structure wants a plan before moving; Momentum wants to move before the plan is finished. Analysis wants to understand fully before committing; Momentum wants to act and adjust. None of these is wrong. The Structure-and-Momentum tension is really a legitimate question: what level of certainty is sufficient for the risk we are taking? The friction is not the problem. It is the team thinking out loud, sharing perspectives, and seeing different aspects of the situation. It is value sets at work and in tension.
The problem is what happens when the friction goes underground when the team disengages. That is the distinction that matters most. Disagreement is healthy. Disengagement is the risk. The moment a person decides it is safer to stay quiet than to hold their value in the room, the team loses exactly the perspective it needed, and the leader never even sees the loss. The decision looks clean. It is just missing a voice.
So the leader's real work is not to resolve every tension. It is to keep every code in the conversation. Each code needs something different to stay in a hard conversation rather than withdrawing. Structure needs the disagreement to feel orderly, with a named process for resolving it. Momentum needs the debate to move toward a decision rather than circle and delay for weeks. Connection needs to feel the relationship can hold the tension, that conflict over substance is not a rupture. Analysis needs its reasoning genuinely heard, not overridden by whoever speaks with the most confidence.
This is where the influence-code work creates something deeper. What you are really building, when you keep every code in the room, is psychological safety. The shared sense that people can speak up, name uncertainty, offer a dissenting view, and engage honestly without fear of being punished or dismissed. As Susan David teaches in her work on emotional agility, a leader who cannot stay with their own difficult emotions will unconsciously signal to the team that those emotions are dangerous. A leader who can stay open creates a culture where others can too. The room you create is downstream of the room you keep inside yourself.
When you can do this, you stop being the leader who has to be right and become the leader who makes the room work. The codes balance each other instead of competing. The quiet voices come back. The decisions hold, because they were built with the whole room rather than imposed on it.
Clear Eyes. Full Hearts Practices
The practice: Keep every code in the room
Think of a recurring conversation with a team you lead, a standing meeting, a decision you keep revisiting, a tension that never quite resolves. Bring it clearly to mind.
First, scan for the withdrawal. Who has gone quiet? Not who disagrees, but who has stopped engaging. Disengagement is the signal that a code has left the room. Often it is the person whose value is least like your own, the code that sits lowest in your own stack and that you find most frustrating. That frustration is usually a sign they are leading from a value you rank low, not a sign that they are wrong.
Then ask, for each person who has gone quiet, what would they need to come back in?
The one protecting Structure needs to know there is an orderly process for the disagreement, that it will not be chaos.
The one protecting Momentum needs to know the conversation is going somewhere, that it will reach a decision rather than circle week to week without resolve.
The one protecting Connection needs to know the relationship can hold the disagreement, that challenging the idea is not rejecting the person or harming the relationship.
The one protecting Analysis needs to know their reasoning will be heard on its merits, not drowned out by whoever is loudest.
You are not managing personalities. You are making the room safe enough that every set of values gets to add perspective and shape the decision before it is made.
Journal prompts
- In my most important recurring meeting, who has gone quiet? What sets of values and core perspectives left the room when their voices did?
- Which code do I find most frustrating in others? Where does that code sit in my own stack, and what might it be protecting that I tend to miss?
- When my team disagrees, do I experience it as the team working, or as something to smooth over quickly? What does my reaction teach them about whether it is safe to disagree?
- Can I stay with my own discomfort in a hard conversation without rushing to resolve it? What does my team learn from watching me do that, or fail to?
Leadership translation
One of my strengths is that I can move a room toward a decision. I can hear where things are heading and name it clearly.
This gift can become a challenge. A room that moves quickly toward a decision can create an environment where the slower codes, the ones that need to analyze, to gauge employee morale and buy in, to know the structure will hold, can quietly decide it is not worth the friction to slow things down. I can mistake the resulting smoothness for alignment when it is actually a disengaged team of peers.
The work for me is not to stop moving rooms forward. It is to notice who goes quiet when I do, and to treat that quiet as information rather than consent. To build enough safety that the dissenting voice stays in, because the decision I make with the whole room is stronger than the one I make with only the voices that move at my speed.
Self-awareness keeps my strength from distorting my leadership. Relational awareness lets me meet people in their code. And the work of keeping every code in the room is what turns a group of capable people into a team that can make well discerned and durable decisions.
Invitation
This is the close of the arc, and I want to leave you with the through-line. Self-awareness lets you disrupt going into auto-pilot where your strengths become major blind spots. Relational awareness lets you expand your influence by understanding the value sets that motivate others. When you keep every code in the room engaged, you build something that lasts. You cultivate a culture where people can be fully human, disagree honestly, and trust that the work is better for it.
I would love to hear what landed for you across these editions. You can reply and tell me which code tends to go quiet in your rooms, and what it might take to bring it back.
If you want to practice this work live, I am hosting a free Influence and Impact workshop this Wednesday, July 8 at 12:00 PM CT.
It is sixty minutes on recognizing your own influence code, learning to read the codes of the people you lead, and building the kind of room where everyone stays in the conversation. It is the natural next step from everything in this arc, and there is still time to join.
Register for the July 8 Influence & Impact Workshop here!
And if you would like a more personal space to look at the patterns in your own leadership and the rooms you create, the button below will take you to a complimentary Clarity and Alignment Conversation. It is simply a place to think out loud and find your next values-aligned step.
You can book a time here.
Clear eyes. Full hearts.
Paula
Influence-code language in this edition draws on the BANK framework developed by Cheri Tree and Codebreaker Technologies. The teaching on psychological safety and staying present to difficult emotions draws on the work of Susan David, PhD, on emotional agility, and on Amy Edmondson's research on psychological safety.
If you are interested in what coaching with me looks and feels like, read more by clicking the button below.
And please, spread the word to your trusted colleagues and friends by sharing this edition and inviting them to subscribe.
