The Comfort of Agreement

“Agreement should close a decision, not close inquiry.”

Agreement is a strange thing. It gives us a sense of safety, of belonging, but it can also usher in a moment where we suspend critical thinking and, unknowingly, we subdue our inquisitiveness. Consensus feels like progress. It feels like it has brought closure. But it can also mark the point where curiosity ends. And without curiosity, progress doesn’t last for long.

Many advances have depended on people willing to question prevailing assumptions.

In business and consulting, as in life, courage alone is not enough. It takes the courage to question what others hold as truth, and the finesse to do it without triggering defensiveness. True influence lies in helping others stay open, even to ideas that challenge their own, and guiding them gently towards reflection rather than retreating into the comfort of majority consensus.

The problem is not consensus itself. Teams need shared decisions in order to act, and good consensus can emerge from serious challenge. The danger is unexamined consensus: agreement that arrives before important assumptions have been examined, or that becomes too socially valuable to reopen. Thoughtful dissent is not the opposite of collaboration. It is one of the ways collaboration tests whether its confidence is deserved.

When Consensus Becomes a Cage

“A shared view remains useful only while it can still be questioned.”

Even science, a discipline built on questioning, can become too confident about the limits of what is possible. During much of the twentieth century, influential models in neuroscience and medicine placed strict limits on plasticity in the mature brain, often treating significant change as something largely confined to early development. Evidence of adult neural and cortical change existed, but it had to contend with deeply established assumptions about the fixed adult brain. As reproducible evidence accumulated across different studies and forms of plasticity, the accepted view changed. That is not a failure of science. It is a reminder that even evidence-based consensus must remain open to revision.

Consider the telecommunications industry’s embrace of TM Forum Open APIs. The reasons for alignment were compelling: shared interfaces promised simpler integration, lower technical debt, greater interoperability, and less dependence on proprietary systems. As operators began requiring the APIs in procurement processes, ‘TMF compliant’ became an increasingly powerful signal that a product belonged in a modern architecture.

But a useful standard can also acquire a confidence that exceeds what any standard can guarantee. A conformance result applies to a particular scope, while a real deployment may still contain legacy systems, optional capabilities, vendor extensions, and customer-specific integration. Those realities do not invalidate the standard. They do mean that the label should begin a more detailed conversation rather than end one.

The danger appears when the industry’s shared enthusiasm makes those qualifications difficult to voice. A practical tool then becomes a reassuring story: the standard promises interoperability, the product carries the expected label, and the difficult questions are treated as implementation detail. Consensus has not necessarily produced a bad standard. It has reduced the space in which people feel able to discuss what the standard does not solve.

Yet, this is where the lesson lies. Even the most well-intentioned alignment can drift into rigidity when compliance begins to overshadow curiosity. The challenge isn’t to reject consensus, but to preserve within it the space for questioning, the kind of thoughtful dissent that keeps progress alive.

A Moment That Stayed With Me

“Progress can be real without being complete.”

At a TM Forum gathering in Copenhagen, I watched the industry proudly showcase its achievements and innovations. The buzz was all about, of course, AI, but also about the TM Forum Open APIs. Presentation after presentation described them as the cornerstone of modern telecom architecture. At one stand, a major operator was showcasing the architecture of a large-scale transformation project built around these APIs, celebrating them as the key to interoperability and agility.

I listened carefully, and when the presentation ended, I asked something simple, but very real:
“How do you handle integration with systems that don’t conform to these APIs, or those that only partially implement them? Because in the real world, that happens quite often.”

The later answer was more qualified. Where systems did not fully conform, the team still needed custom integration. That did not mean the standard had failed; no standard removes every exception. But it revealed how much complexity had disappeared from the confident public version of the story. ‘Compliant’ and ‘plug-and-play’ sounded complete, while the reality still depended on context, extensions, and implementation choices.

That conversation stayed with me because the important moment was not the admission itself. It was the pause created by a respectful question. The aim was not to embarrass anyone or dismiss the work. It was to make room for a truth that enthusiasm had compressed: progress can be real without being complete. Even a good standard becomes constraining when people stop feeling able to discuss its limits.

The Courage to Question

“Dissent is not a refusal to move. It is a way of checking the direction.”

Dissent is often mistaken for defiance. In truth, it is an act of courage, and one of the most valuable soft skills a consultant or leader can possess.

Challenging the majority requires more than technical insight. It demands empathy to understand why people hold on to certain beliefs, communication to raise difficult points without alienating others, and influence to guide a group towards reflection rather than resistance.

These are not “nice-to-have” traits. They are what separate the consultant who adds real value from the one who simply echoes the client’s assumptions, or parrots back the majority view without a moment of critical thought.

The responsibility does not rest only with the person who speaks. Leaders and colleagues need the skill to receive dissent without immediately defending their judgement or questioning someone’s loyalty. An invitation to challenge means little if the first difficult question is dismissed. How we respond to an objection helps determine whether the next concern will be voiced or quietly withheld.

The Hidden Cost of Silence

“When people cannot qualify the story, confidence becomes conformity.”

“Compliance engineering” is a phrase I’ve come to associate with this dynamic, when teams spend more time aligning with standards than solving real problems. When people stay silent out of fear of being different, organisations lose creativity, authenticity, and truth.

Unexamined consensus can look safe on the surface, but it hides a deeper risk: innovation stagnation. Innovation can stall not only because weak ideas prevail, but because better ones are never voiced.

The Soft Skills Of Dissent

“The aim is not to win the argument, but to improve the decision.”

Thoughtful dissent is defined by its purpose and substance, not its volume. It’s grounded, thoughtful, and human. It’s knowing how to challenge, not just what to challenge. It means listening deeply before you speak, asking questions instead of making declarations, and building bridges even as you question the direction of travel.

In consulting, this is one of the hardest soft skills to master. It requires:

  • Listening for silence. When a room agrees unusually quickly, treat it as a signal to check what may be missing.
  • Framing curiosity, not confrontation. “Can we explore this?” goes further than “This won’t work.”
  • Balancing evidence with empathy. Facts matter, and how you deliver them often determines whether they can be heard.

Dissent carries its own responsibility. A concern is a contribution to inquiry, not proof that the group is wrong. The person challenging a decision must be willing to explain the concern, listen to the reasoning already considered, and revise their own position. Curiosity stops being curiosity when it demands that only other people change their minds.

Keeping inquiry open does not mean reopening every decision indefinitely. Teams can act while being explicit about what remains uncertain and what new evidence would justify reconsideration. A decision can be settled for now without becoming beyond question.

Mastering dissent is not about being right, it’s about helping the collective arrive at what’s right.

A Lifelong Practice

“Courage becomes culture through repetition.”

Courage and dissent aren’t one-off acts. They’re habits, disciplines that, like any soft skill, must be practised. Each time we choose to voice a well-founded concern, we strengthen not just our own integrity, but the culture around us.

In consulting, leadership, and everyday collaboration, progress benefits from people willing to pause amid the comfort of agreement and ask:
Is this truly adding value, or have we stopped testing the shared view?

Consensus can help us move together, but thoughtful dissent keeps that agreement open to correction.