Everyone nodded
Easy agreement tests no one's judgement. Events will.
Everyone Nodded
Two of them told you last week. One to one, door closed, in the way people tell the people leader things: not asking you to do anything with it, just needing someone to know.
So you walk into the meeting already knowing the tension is in the room. The initiative is on the agenda. The question underneath it: whether that team can actually deliver the change, whether the right people, skills, energy and the will are there. These are the questions two people have already answered privately, and neither these questions nor the answers are in the proposal on the table.
The proposal lands. The energy shifts. You watch.
One of them leans forward slightly, as if to speak, while someone else is talking. Waits to see if anyone will say it. Nobody does. They sit back. The other goes quiet, shoulders down, head down. The chief executive plays back the position, and the perspective you heard last week is not in it. The challenge is not in it.
You watch the eye-lines. Almost no one is looking around the room at each other. They are looking at the leader, whoever is speaking, or into space, with the occasional glance to the one person they know agrees with them. Two people wondering why the question is not being raised, and still not raising it.
Then, one by one, the heads nod. Including the two.
Two nods that look the same
Before anything else, the distinction this article makes, because from across the table the two are seemingly indistinguishable.
There is the nod that comes after a judgement has been argued: in this room, in other rooms, one to one, tested until the person holding it reaches the point where letting go is what membership requires. That nod is a duty discharged. It is what a leader owes the collective once the collective has genuinely heard them.
And there is the nod that comes instead of the argument. The judgement was never brought, the tension never surfaced, and the head goes down because the room's desire for alignment is stronger than any one person's willingness to be the friction. That nod is a performance of agreement, and it is the subject here.
This is the lens: performed agreement. And the uncertainty in it needs calling out. Agreement that arrives without friction has not tested anyone's uncertainty. The nodding is certainty performed, not certainty reached, and a decision built on it is carrying doubts nobody examined, into implementation, where they will be examined by events instead.
Easy agreement tests no one's judgement. Events will.
I have felt the reluctant nod from the inside. It was more of a head hanging, a tiny movement I almost did not want to happen, after I had challenged in other rooms and watched the proposal gather support anyway. Tacit acceptance that this was the direction. I told myself I did not know all the answers, and hoped the collective wisdom, or someone's particular expertise, would carry us to the right path. Sometimes that was humility. Sometimes it was the confusion between allowing the majority and enabling it, which is a sign the tensions were never integrated at all. Occasionally it was pure fatigue. Only I knew which, and some days I did not want to look too closely.
Looking as, and looking at
You hold a position in that room that the chair and the chief executive do not. You are a member of the team, and you are watching the team. Looking as, and looking at. It is an advantage, and it is a responsibility, and some weeks it is a burden.
You are holding knowledge that was shared with you in confidence and is not yours to put on the table. You may know of other tensions that are not for this forum either. You can work to create the space for them to come out. The awkward truth about that space: you can build the environment, you can open the door, and you still need people to walk through it. If they do not, the space was necessary and it was not sufficient.
You also hold your own view, and here the seat has a trap in it. In some teams the people leader's voice is treated as their area of expertise and nothing more. In the most mature teams, every leader's perspective is valued beyond their function, and the whole includes the expertise rather than being limited to it. Which kind of team you are in decides how much of what you see you can actually say and what will be heard.
And, more than most in that room, you are watching the dynamics: how people are showing up, who has stopped speaking, where the eyes go. For some people leaders this is an unconscious ability. For those who work on it consciously, it becomes a powerful scaling capability, because a team that can see itself deciding can change how it decides.
What it costs you is frustration, and energy. Seeing points not raised. Seeing issues ignored that needed facing into. Feeling it both as a member and as a watcher, and holding, on top of that, the question of whether and how to intervene: in the room, outside it, one to one, a quiet word in the leader's ear, judged by context and topic and what the relationships can carry.
What the nodding costs
Performed agreement carries a hard invoice, and it arrives at four principal areas.
1. The initiative itself: time, money, an implementation that fails or drifts, results delayed, the questions that follow from investors.
2. The market: competitors who were already ahead pull further ahead while the business absorbs its own drift, and market share, sales, and customer experience take the hit a quarter or two later.
3. The organisation: the people below could see the tension from where they sat, they were waiting for the leadership team to make the move, and when the move does not come, belief in the strategy drains, and energy goes with it. Later so do your best people.
4. And the leadership: the support of the board and the investors, and eventually the leader's own position.
A single nodded decision is survivable. A pattern of them is a different thing: strategic drift that carries on for months or years, and in the worst cases becomes an existential threat to the business. Cultures of nodding rarely fail loudly. They fall behind slowly, and by the time it is undeniable, the competitors who faced into their problems are out of sight.
The symptom and the cause
The nodding is the symptom. It is almost never the problem.
Often the tension in the room, whether a team or a leader can deliver the change, is itself a stand-in for something the leadership team has not faced into: the resource priority decision, the people decision, the adviser or the technology that is not working. The resistance you are watching is the leadership team's own resistance to the problem that is actually in the way, disguised as a delivery question.
And the cause can sit in any of four places.
In the system around them: do the structures help or hinder? How much pressure is loaded onto this team, and where is it coming from?
In the people: how well can each of them carry that pressure? Do they understand how differently each of them sees the world, and what matters most to each of them, and why?
Between them: is there a sense of us, together, finding the challenge, or of me against you, fighting for the solution? Did we ever actually align on the direction, or is this nodding the echo of a disagreement nobody voiced then either? Do they trust each other enough to dissent without threatening the relationship? Do they even really know each other deeply enough?
In how the meeting runs: does every view get out, get differentiated, get integrated, or does the strongest voice close the item?
Which is the first job to work on? It takes a little time and effort to work out and work on, and the team that does it becomes a team that can decide more wisely.
What this asks of you
1. Read the room as symptom, not as verdict. Facial expressions against votes. The lean forward and the sit back. The energy and feeling behind the eye-lines that never meet. When the nodding is easy and the item was hard, treat the ease itself as a potential insight.
2. Look as, and look at, and name to yourself where the cause may sit. In the people, between them, in how the meeting runs, or in the system. You will not be sure, and you do not need to be; you need a first hypothesis good enough to test.
3. Make challenge welcome, not brave, both before and in the meeting. The one-to-ones where dissent costs less. The quiet word that lets the leader share or hear the tension before the room performs its absence. The question given to the chair so that it is asked from the front, not from the side. Role model welcoming challenge to your perspective. Build the space to listen and hear, and remember it is never sufficient on its own.
4. Feed the pattern back, never the confidences. The leader needs to know that the room nods past its hardest questions, and roughly why; the leader does not necessarily need to know who told you what. System information, offered as a member of the team, is a very valuable thing your seat can provide.
A leadership reality
Easy agreement tests no one's judgement. Events will.
A chief executive can rarely see a room performing agreement while they are the one being agreed with. The seat that sees it is yours, and the capability to do something useful with what you see, without spending a confidence or a relationship, is developable at many levels, and its impact travels further than you may imagine.
One question worth carrying
In our last easy agreement, what did we never uncover or examine, and what was my part in that?
Ask it of yourself and the team, and do not dodge the last part.
It is a wise leadership move to treat easy agreement on a hard question as information, because a team that never disagrees is telling you something, and it is not that they agree.
May you always find wise judgement when certainty is unfindable.