Silence Is Not Alignment

What do you prefer? Lively debate, or a room where everyone quietly falls in line? Because that second option often looks far more professional than it really is.

The owner presents the plan. The team listens. Someone asks a polite question. Someone else says, “Makes sense.” There are careful smiles, quiet notebooks, and the decision leaves the room looking neat, polished and completely untested, like a bakkie with a fresh wash and a warning light still glowing on the dashboard.

Then the meeting ends. In the kitchen, Thandi says, “This is not going to work.” In the parking lot, Pieter says, “We tried this last year.” On WhatsApp, Aisha says, “Did nobody mention the supplier delay?” And somewhere in the business, the truth finally arrives, late, barefoot and carrying a plastic Checkers packet full of consequences.

That is not alignment. That is silence with meeting minutes.

This is where Amazon’s Leadership Principle of Have Backbone; Disagree and Commit becomes useful. Not as a permission slip for being difficult. And definitely not as a licence to become that person who turns every discussion into a courtroom drama with snacks.

Have Backbone asks for something harder. It asks people to respectfully challenge decisions when they disagree, even when doing so is uncomfortable. Then, once a decision has been made, it asks them to commit properly.

That second part is essential. This principle is not “disagree forever”. It is not “keep reopening the decision every time the wind changes direction”. It is not “quietly wait for the plan to fail so you can rise from the smoke and whisper, I told you so.” It is challenge before the decision, then commitment after the decision.

Simple. Also, wildly difficult. Because in real life working with teams, disagreement is never just disagreement. It arrives carrying hierarchy, history and the memory of what happened the last time someone raised a concern.

In a small South African business, this can get even more complicated. The owner may be kind, but still intimidating because they sign off salaries. The supervisor may say, “Please be honest,” but the team remembers what happened to the last honest person. The junior employee may spot the risk first, but not know whether it is their place to say so.

So the business gets politeness instead of truth. And politeness can be very expensive. This is where team dysfunction walks in quietly and puts its keys on the table.

Patrick Lencioni’s Five Dysfunctions of a Team is useful here because it names a pattern many teams know instinctively. When there is no real trust, people avoid vulnerability. When teams avoid vulnerability, they fear conflict. When teams fear conflict, they struggle to commit. For this article, those first three dysfunctions are the fire starters.

Absence of trust.

Fear of conflict.

Lack of commitment.

They fit Have Backbone; Disagree and Commit almost too neatly. If people do not trust the room, they will not say the real thing. If the group cannot handle healthy conflict, disagreement goes underground. If disagreement goes underground, commitment becomes theatre. Everyone nods. Everyone leaves. Everyone starts making private adjustments to survive a public decision they never truly supported. That is not execution. That is a slow leak.

Psychological safety helps explain why. A psychologically safe team is one where people believe they can take interpersonal risks without being punished or humiliated. In plain business language, it means people can ask the awkward question, raise the uncomfortable concern, or say, “I think we are missing something,” without immediately needing a side quest in self-preservation, or being shut down, gaslit by a toxic manager, and then having the conversation twisted into a catalogue of their past mistakes while the original concern quietly disappears.

Psychological safety does not mean every opinion carries equal weight. It does not mean weak thinking should be accepted simply because it was expressed confidently or with emotion. And it does not mean leaders must turn every meeting into a space where feelings replace clear thinking and accountability.

Psychological safety is not softness. It is working conditions for truth. And without truth, Have Backbone becomes laminated office wisdom. Very neat. Very framed. Absolutely useless when the stockroom is on fire.

A leader cannot demand backbone from a team that has been trained to protect itself through silence. This is the part many businesses miss. They think the problem is that people are not brave enough. Sometimes that is true. But often the deeper issue is that the system has taught people not to speak. Concerns get dismissed too quickly. Questions are treated as resistance. The loudest person always wins. The team learns.

Teams always learn.

They learn what is safe to say, who is safe to challenge, which topics are sacred cows, and when the smartest move is to nod politely and discuss the real issue later with someone who will not weaponise it.

That is why we need a different kind of root cause analysis.

Root Cause Analysis is usually aimed at defects in the work. A late order. A wrong item. A repeated customer complaint. We ask why the failure happened, where the process broke, and what allowed the defect to pass through. But sometimes the defect sits in the room before the work even begins.

The team saw the risk. The concern existed. The warning signs were there. The problem was that the truth did not travel. So for Have Backbone; Disagree and Commit, the tool is not a normal RCA. Let us run a Team Silence RCA together.

“Why did the truth not surface before the decision was made?”

A Team Silence RCA does not hunt for a scapegoat. It does not ask, “Who should have said something?” with the energy of a manager sharpening a pencil into a tiny spear. It asks what made silence more likely than honesty. The possible root causes are trust, conflict, clarity, power, consequence and commitment. But do not start with a form. Start with the room.

Did people feel safe enough to say the real thing?

Did they understand that challenge was being invited, not merely tolerated?

Did power make honesty expensive?

Those three questions will already tell you plenty.

Trust asks whether people believe the room can handle the truth. If someone raises a concern, will it be heard, tested and used, or will it be met with irritation, sarcasm or a polite little funeral? Past behaviour matters here. Teams do not respond to what leaders say once. They respond to what leaders have repeatedly rewarded, ignored or punished.

Clarity asks whether people knew what kind of input was needed. There is a big difference between “Here is the decision” and “Here is the decision we are considering, please help me find the risk before we commit.” If the leader wants challenge but the team hears announcement, silence is not surprising.

Power asks who had permission to shape the conversation. Who spoke first? Who had the most authority, confidence or status? Did the decision owner accidentally close the discussion by landing their preferred answer too early? Did the person closest to the work have the best information and the least room to say it?

Power does not need to shout to silence a room. Sometimes it only needs to arrive first. This is where Have Backbone matures. The goal is usable challenge before commitment.

A healthy team needs a moment where someone can say, “I disagree because I think this creates a customer risk.” Someone else can say, “I can commit, but we need to name the operational constraint.” And someone closest to the work can say, “This plan can work, but not at this timeline.” That is not rebellion. That is responsibility.

For South African entrepreneurs, this matters because small businesses often run on speed, instinct and relationships. You cannot hold a full strategy offsite every time someone wants to change a courier, launch a promotion or update a return process. There is work to do, customers to answer, stock to move, cash flow to protect, and at least one spreadsheet held together by hope, colour coding and somebody named Janine who left in 2021.

But speed without challenge can become expensive.

A promotion launches, but fulfilment cannot cope. A supplier is changed, but quality checks are unclear. A new system is bought, but nobody maps the broken process before automation arrives wearing shiny shoes and false confidence.

The issue is not that nobody knew. The issue is that nobody said it in the room where the decision was still soft enough to change. That is why leaders have to design for challenge. Not hope for it. Not announce it once and assume everyone suddenly becomes fearless. Design for it.

Before a decision, ask for disagreement on purpose. Not, “Any thoughts?” That question is too soft. It floats into the room, bumps against the ceiling, and dies quietly. Ask better questions.

“What could make this fail?”

“What customer impact are we underestimating?”

“What would the frontline notice before leadership does?”

Those questions create a doorway. Then wait. Silence after a real question is not failure. It is often the room deciding whether the invitation is safe. Do not rescue the silence too quickly. Do not answer your own question like a magician pulling a rabbit out of an insecurity hat. Give people a moment to think. Some of the most useful truth arrives after the loudest people have finished warming up.

And when someone does raise a concern, do not crush the first green shoot. You may not agree with the warning. You may not act on it. But how you respond teaches the team whether the next risk will surface or go straight to the parking lot.

And this is where leaders need to be careful. Do not accidentally punish the person who raises the flag by making the whole problem theirs. There is a difference between asking someone to help clarify a concern and handing them a surprise side quest with no time, no authority and no support. Sometimes an employee is not volunteering to own the issue. They are simply saying, “I am seeing smoke over there.”

The leader still owns the decision about what happens next: whether to investigate, assign support, park the issue, or monitor the signal.

That matters. If every warning becomes extra work for the person brave enough to speak, the room will learn a very practical lesson; keep quiet unless you have the bandwidth to become the task team. That is not psychological safety. That is a trap with meeting etiquette.

A simple response can change the room:

“Thank you. Let us test that without making it your burden alone.”

“What evidence would help us understand that risk, and who is best placed to gather it?”

“Is this a blocker, a risk, or something to monitor?”

That is backbone with discipline. It turns disagreement from emotional weather into operational intelligence, without turning the person who noticed the smoke into the entire fire department.

The commit part also needs care. Once the team has raised concerns, tested the risks and made the call, commitment cannot mean “I still disagree, so I will drag my feet in a way that looks like workload.” That is not backbone. That is a go-slow with a calendar invite.

Commitment means the team leaves knowing what was decided, why it was decided, what risks were accepted, what signals will be monitored, and when new evidence should reopen the discussion.

Disagree and Commit does not mean new evidence gets ignored because the decision has already been made. It means the team does not keep relitigating preference. But if reality changes, the business must be awake enough to respond.

That is the difference between commitment and stubbornness. Stubbornness says, “We decided, so we continue.” Commitment says, “We decided, we execute properly, and we monitor whether the decision is working.” That is much healthier. It also protects trust.

When people know their concerns were heard, even if not all concerns were accepted, they are more likely to commit honestly. They may still disagree, but they understand the reasoning. They can support the decision without feeling erased.

That is the real power of this Leadership Principle. Have Backbone protects the business from false harmony. Disagree and Commit protects the business from endless drift. Together, they create a rhythm: challenge clearly, decide properly, execute honestly.

Without that rhythm, teams perform alignment while disagreement leaks into side conversations, quiet resistance and delayed execution. And then leaders get confused. They say, “But everyone agreed.” No. Everyone was quiet. That is not the same thing.

So where in your business are people nodding in the meeting, but telling the truth somewhere else? And what would need to change for the truth to arrive while the decision is still useful?

This is a personal thought piece, written in my private capacity from my own customer experience and process improvement perspective. It draws on publicly available information and reflects my own views, not the views of my employer.