A business has more than one operating system. There is the visible one: the stock sheets, sales reports, hiring steps, meeting rhythms, customer policies, handover notes, escalation paths and performance reviews. Then there is the human operating system.
That is the quieter one.
It decides whether people tell the truth in the room or later in the car. It decides whether feedback becomes learning or injury. It decides whether a new employee is welcomed properly or left to decode the culture through side-eye and survival instinct. It decides whether conflict gets repaired or simply packed into the cupboard with the broken printer cable nobody wants to discuss.
This article is about that system.
Because Amazon’s Leadership Principle of Have Backbone; Disagree and Commit asks for respectful challenge before a decision and proper commitment afterwards. It is not asking for rudeness with a calendar invite. It is not asking for soft silence wrapped in politeness. It asks for the harder thing: courage with discipline.
In South African teams, that word “respectful” matters. A lot.
Use this article when a team needs honest disagreement, but the room also needs dignity, repair and enough trust for people to keep working together afterwards.
Disagreement does not land in an empty room. It lands in a room with hierarchy, language, age, race, job level, personality, pay pressure, family history, social memory and the very human need to leave the meeting with one’s dignity still attached.
So yes, people need backbone. But backbone without dignity becomes ego. Dignity without backbone becomes silence. And silence, as most businesses eventually learn, can invoice you later with interest. This is where Ubuntu leadership gives us a useful South African lens.
Forget the soft-focus poster with everyone holding hands around the braai. It is not a polite blanket thrown over poor behaviour. And it is most certainly not an excuse to avoid hard conversations because “we are all family here”, which is often workplace code for “please swallow this discomfort so nobody important feels awkward”.
Ubuntu leadership is more demanding than that. At its strongest, Ubuntu asks leaders to hold five things together: human dignity, interdependence, mutual responsibility, community and repair.
Human dignity means people are not reduced to their mistake, job title, accent, seniority or the fact that they have a different opinion or viewpoint.
Interdependence means the team understands that one person’s silence, hesitation or withheld concern can become everyone’s problem.
Mutual responsibility means care is not avoidance, silence or the quiet decision to let something slide because it feels uncomfortable to address. It is not choosing short-term peace over long-term health. We owe each other honesty as well as kindness.
Community means the leader is not only managing tasks. They are stewarding how people work together. The health of the group is part of the work, not a soft extra for when targets are quiet.
Repair means conflict should not leave permanent shrapnel in the carpet. The point is not humiliation. The point is learning, accountability and a stronger working relationship afterwards.
That is much richer than “be nice”. It asks people to bring their values into the room without using those values as a shield against accountability or a weapon against others. Real respect is not about avoiding discomfort. It is about navigating discomfort in a way that strengthens relationships rather than weakening them.
It also sits beautifully next to Have Backbone; Disagree and Commit. Have Backbone asks: will you say the difficult thing when it matters?
Ubuntu leadership asks: can you say it in a way that preserves the humanity of the people who still need to work together tomorrow?
That is the human operating system.
If it works, the right signals can move. If it breaks, people may still attend the meeting, update the spreadsheet and smile at the right moments, but the real information will travel elsewhere. Kitchen. Parking lot. Private WhatsApp group. Quiet resignation. Slow resentment. The business will think it has alignment while the actual operating system is coughing behind the curtain and quietly losing trust.
This is where we can borrow from process thinking. In Lean Six Sigma, CTQ means Critical to Quality. It asks what matters most to the customer. What must be true for a product, service or experience to meet the real need?
For this article, we are turning CTQ inward. The “customer” is not the buyer. The “customer” is the internal process that carries the work: how the business hires, disagrees, gives feedback, handles tension, builds cohesion and commits after discomfort.
Ubuntu gives us the leadership ethic. CTQ gives us the operating check. So the question becomes: “What is critical to quality for the human operating system?”
This gives us a Team Trust CTQ Map. Not a personality test. Not a culture stereotype machine. Not a values exercise where everyone writes “respect” on a sticky note and then goes back to interrupting the same person before they finish their sentence.
A practical map. A way to ask: what must be true in this team for people to challenge the work without breaking trust, dignity or commitment?
The first internal CTQ is communication.
Not communication as in “send more updates”. That is where many businesses go wrong. They hear “communication problem” and immediately create another newsletter or internal memo, because apparently the first seventeen were just the warm-up act.
Backbone without dignity becomes ego. Dignity without backbone becomes silence.
This is about whether the team knows how to raise a concern clearly.
In one business, a direct sentence like “This hiring panel is missing an important perspective” may be heard as useful challenge. In another, the same sentence lands like someone kicked open the door with a clipboard. Neither reaction makes the team good or bad. It means the human operating system has not defined what respectful challenge sounds like.
A useful CTQ question is: “How clear does a concern need to be before we treat it as decision-ready information?”
This matters in recruitment. Someone on an interview panel may feel that a candidate interviews beautifully but avoids accountability when asked about conflict. Another person may notice that the panel is being charmed by polish rather than testing for the realities of the role. The concern is whether the candidate is being considered fully, and whether the panel’s communication style is shaping how the candidate is interpreted. If those styles are mismatched or unexamined, important signals can be missed or misread, and the discussion can shift away from understanding the candidate and towards reacting to how the message is delivered.
A stronger team designs the hiring process itself to be inclusive, so that different perspectives can surface without relying on individuals to force their way in.
The second CTQ is disagreement.
Not whether people are “allowed” to disagree. Most leaders will say they welcome disagreement. Cool, I believe you. Many also say they enjoy feedback, then react to it like someone served them rooibos with salt.
The real question is: where does disagreement belong?
Some teams can challenge openly in a meeting. Others need a smaller conversation first, especially where hierarchy, embarrassment or status is involved. Some people need time to process before they can name the concern properly. Others think while speaking and only find the actual point halfway through the sentence, usually while everyone else is blinking.
A useful CTQ question is: “Where can people safely challenge a decision before it becomes final?”
This matters in workplace conflict. Imagine two team members keep clashing over handovers. One is direct and fast. The other is careful and detail-heavy. The leader treats the tension as a personality issue and says, “You two must just communicate better.”
That is not leadership. That is sprinkling parsley on a cracked plate. The better move is to create a clean place for disagreement. What part of the handover is failing? What does each person need to do good work? What behaviour is creating friction? What agreement will we test next week?
Disagreement needs a proper room, not a gossip corridor.
The third CTQ is authority.
Every business has power dynamics. The owner has power. The leader has power. The long-serving employee has power. The person who knows where every file is saved has a special kind of magical power and should be treated carefully.
Authority is not the enemy. Businesses need decision owners. Someone must eventually make the call, especially when time, cash flow and customer commitments are all standing at the door tapping their watches.
The question is whether authority creates clarity.
A useful CTQ question is: “Do people know when they are being consulted, when they are deciding, and when they are expected to commit?”
This matters in performance conversations and team conflict. If a leader says, “Let us discuss this,” the employee may think they are co-creating a path forward. The leader may already have decided the outcome and is merely explaining it before confirming it in writing. That mismatch breeds resentment.
Clarity would sound different. “I am making the final call, but I want your view before I decide.” “We are deciding this together, so I need honest disagreement now.” “This direction is set. We are not reopening preference, but we will monitor whether new evidence changes the risk.”
That kind of clarity is not cold. It is respect with the lights on.
The fourth CTQ is trust.
Trust is not only whether people like each other. Liking each other is an absolute plus in any working environment, but it does not always reflect reality or guarantee that anyone will raise the real issue when the room gets tense.
Trust is built by what happens after honesty. If someone raises a concern and gets punished with blame, silence grows. If someone flags a risk and immediately inherits the entire problem with no authority, no time and no support, silence grows. If someone admits a mistake and the story returns three months later as a weapon, silence grows teeth.
A useful CTQ question is: “What builds enough trust here for someone to risk honesty?”
This matters in onboarding and team cohesion. A new employee is not only learning the job. They are learning the unwritten rules. Who can be challenged? Which mistakes are survivable? Which of their values are accepted in the group? When does “we value openness” mean actual openness, and when does it mean “please speak freely inside the invisible fence”?
If leaders want trust, they need to make the invisible fence visible. They need to show how concerns are handled. They need to separate the person from the issue. They need to make it clear that raising a flag does not automatically make you someone with attitude, a problem with authority, or not a team player.
Trust is not built by announcing that the room is safe. It is built when the first uncomfortable truth is handled well.
The fifth CTQ is dignity.
This is where Ubuntu leadership becomes more than a nice phrase. Dignity asks whether people can be corrected, challenged or disagreed with without being stripped of standing in front of others.
A useful CTQ question is: “How do we challenge the work without humiliating the person?”
This matters in conflict handling. A supervisor may have mishandled a shift handover. A recruiter may have missed a red flag in an interview. A team lead may have allowed one person’s behaviour to damage the group mood for too long. Those issues must be addressed. But there is a difference between accountability and public bruising.
Dignity-preserving challenge says, “This part of the process is exposed,” not “You clearly did not think.” It says, “Let us look at the impact of that decision,” not “This was obviously a bad call.” It says, “We need to repair the working agreement between these two roles,” not “They are being difficult again.”
The difference is not softness. The difference is whether the room can still think. Attack the person, and the room defends identity. Challenge the work, and the room can examine reality. That is useful.
The sixth CTQ is repair.
This is the part that often gets skipped. Businesses talk about feedback. They talk about accountability. They talk about performance. But after conflict, many teams simply pretend the bruise is gone because nobody is actively bleeding in the meeting.
That is not repair. That is emotional load-shedding. The lights are off, everyone is pretending to cope, and the freezer is quietly defrosting.
A useful CTQ question is: “After disagreement or conflict, how do we repair enough trust to keep working well?”
Repair does not mean everyone hugs and writes a poem. It means the team knows what was agreed, what will change, what behaviour must stop, what support is needed and when the issue will be reviewed. It means the person who raised the concern is not isolated. It means the person who received the feedback is not written off forever. It means the team learns, not just survives.
This matters for cohesion. A team can survive one tense conversation. It may not survive a culture where every tension becomes a private archive. People remember unresolved moments. They remember who was protected, who was blamed, who was believed, who was mocked, who was promoted anyway, and who quietly stopped trying.
The human operating system stores everything. That is why Ubuntu leadership and Have Backbone belong together. Ubuntu without backbone can become avoidance dressed as harmony. Backbone without Ubuntu can become honesty that leaves dents in people. Together, they ask for a stronger standard: tell the truth, preserve dignity, share responsibility, repair the relationship and commit to the work.
That is not fluffy. That is operational maturity.
For South African entrepreneurs, this matters because many businesses are built on close working relationships. Family members become colleagues. Friends become co-founders. Long-serving staff become part of the furniture, then the foundations. New hires walk into cultures that were never written down but are somehow enforced with the precision of a tax deadline.
That relational strength can be powerful. It can also make challenge harder. Nobody wants to embarrass the founder. Nobody wants to make the supervisor look bad. Nobody wants to be the new person who asks why the interview process feels inconsistent, why the same conflict keeps repeating, or why the team keeps calling itself “family” while avoiding the conversations families usually need most.
So the room chooses comfort. But comfort is not the same as care. Sometimes care is admitting, “The team is polite, but it is not cohesive.” That is not disloyalty. That is stewardship. The Team Trust CTQ Map helps leaders look at the playing field before demanding backbone from everyone standing on it.
Do we know how concerns should be raised? Do we know where disagreement belongs? Do we know who decides? Do we know what builds trust? Do we know how to protect dignity? Do we know how to repair after conflict?
Those questions shape whether people speak early, whether hiring improves, whether conflict gets addressed, whether feedback becomes usable, and whether commitment is real.
A strong business is not one where everyone speaks bluntly and leaves bruised. A strong business is also not one where everyone smiles while the warning lights blink quietly under the table. A strong business knows how to tell the truth in a way the work can use and the people can survive.
That is the work. Not softer truth. Not louder truth. Usable truth. Truth with enough backbone to matter, and enough dignity to be heard.
Practical take-away
Before your next important internal decision, build a simple Team Trust CTQ Map.
Ask what is critical to quality for the human operating system in your business. Look at communication, disagreement, authority, trust, dignity and repair.
Do not start with a grand culture programme. Start with one internal process. You might start with recruitment, if hiring conversations miss important signals. You might start with conflict handling, if tension keeps moving into side conversations. You might start with team cohesion, if people are polite but guarded.
Then choose one improvement and start there. Maybe you clarify decision roles before meetings. Maybe you add a structured conflict repair step. Maybe interview panels test for coachability and respectful challenge. Maybe managers learn not to punish people for raising concerns. Maybe the team agrees on language for blockers, risks and things to monitor.
Because if you want people to Have Backbone, you have to build a human operating system where truth can stand up without being punished for having legs.
So, pressure test your own room: what is critical to quality for honest disagreement in your team? And what would need to change so people can challenge the work without breaking trust, dignity or commitment?
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. It does not discuss or rely on confidential company information.