Community

translate Automatic translation · View original

What does your team know about itself that it never says out loud?

Canal Agile Coaching

1 September 2026
What does your team know about itself that it never says out loud?
Every team has shared knowledge that never makes it into words. That a certain person isn't performing but nobody addresses it. That the process we follow makes no sense but we respect it anyway. That the metric we report means nothing. That the underlying problem is the boss, or the client, or a decision made years ago that nobody questions anymore. These are truths everyone knows and no one states: what Chris Argyris called the "undiscussables."

The knowledge that exists but doesn't circulate

There are two very different kinds of things a team knows about itself and doesn't say. It's worth separating them because they have different causes and different remedies.

The first is tacit knowledge: real know-how that the team possesses but can't articulate, not because it hides it, but because it's hard to put into words. Michael Polanyi summed it up in a famous phrase: "we can know more than we can tell" (The Tacit Dimension, 1966). An experienced team knows who is good at what, which parts of the code are fragile, how things are actually done beyond the documented process. That knowledge lives in practice, not in documents, and it is lost when someone leaves.

The second is very different: the undiscussables. These aren't knowledge that is hard to articulate, but truths everyone could state perfectly well, yet there is an implicit agreement not to mention them. They aren't silenced because they are ineffable, but because talking about them is socially dangerous. This article is mainly about these.

The anatomy of the undiscussables

Chris Argyris devoted much of his work to studying why organizations fail to learn from things they know perfectly well. In Overcoming Organizational Defenses (1990) he described a mechanism with an almost perverse logic.

Undiscussable topics exist. But, in addition, the fact that they are undiscussable is itself undiscussable. We not only avoid the problem; we also avoid talking about the fact that we avoid it. Argyris called these "organizational defensive routines": patterns that protect people from threat or embarrassment, and that precisely for that reason prevent the causes of that threat from being detected and corrected.

The result is a closed loop. The problem isn't addressed because it is undiscussable. It can't be pointed out that it is undiscussable, because that is undiscussable too. And so the team invests considerable energy in sustaining a silence that everyone keeps and no one acknowledges. Argyris observed something devastating: the most intelligent and competent people tend to be the most skilled at building and sustaining these defenses, because they have more to protect.

Why we stay quiet about what we know

The reasons for organized silence are several, and they reinforce one another.

The most basic is self-protection. Naming the problem can have consequences: damaging a relationship, being seen as difficult, falling out with someone who holds power, taking on a responsibility we would rather avoid. Silence is, individually, the lowest-risk option.

There is also the misunderstood norm of politeness, which confuses respect with avoidance. In many teams there is a tacit agreement not to make anyone uncomfortable, to keep the atmosphere pleasant, which ends up turning any difficult truth into rudeness. Being candid comes to be perceived as being inconsiderate.

And there is learned resignation: the team tried to talk about certain things in the past, nothing happened, or something bad happened, and it learned that saying it is pointless. Silence isn't always fear; sometimes it is the reasonable conclusion that speaking is useless. What organizational research has studied as "organizational silence" is especially corrosive because it disguises itself as pragmatism.

The cost of what goes unsaid

Maintaining the undiscussables isn't free, even though its cost is invisible, like that of so many systemic dysfunctions.

The most obvious is that problems don't get solved because they aren't named. An absurd process that nobody questions persists. A person who isn't performing and whom nobody addresses keeps not performing, and the rest of the team carries the burden while resentment builds. A wrong decision that nobody discusses anymore shapes everything that comes after.

But there is a deeper cost: the wear of sustaining the silence. Keeping up a collective fiction consumes emotional energy. People know they are taking part in an agreement not to say things, and that dissonance, between what they see and what they are allowed to acknowledge, erodes trust and commitment. A team full of undiscussables is, in a sense, a team that cannot look itself in the face.

And there is the cost to learning. Argyris directly linked defensive routines with organizations' inability to achieve "double-loop learning": learning that not only corrects errors but also questions the assumptions that generate them. A team that cannot name its undiscussables is condemned to improve within frameworks it never examines.

The AI context: new undiscussables

The arrival of artificial intelligence is generating a new generation of especially charged undiscussables, because they touch something deeply personal: fear for one's own role.

In many teams today there is shared knowledge that is rarely said out loud: uncertainty about how AI will affect jobs, skills, and the value of each person's work. Some people use these tools far more than they admit, for fear that acknowledging it would undermine the merit of their work. Others feel threatened and don't say so, to avoid seeming obsolete or resistant to change. And whole teams sense that certain tasks they perform could be automated, but don't mention it, because doing so would amount to pointing out their own dispensability.

This new undiscussable is particularly toxic because it mixes existential fear with the pressure to appear enthusiastic. The dominant narrative celebrates AI as an opportunity, and dissenting from that enthusiasm, expressing fear, doubt, or loss, is perceived as being on the wrong side of history. Thus the most legitimate concerns become undiscussable precisely when it would be most necessary to voice them.

A team that cannot honestly talk about how AI changes its work won't manage that transformation well; it will suffer it in silence. Making this topic discussable, creating spaces where people can talk about fear without it being a confession of incompetence, is one of the most important facilitation tasks of the moment. It is precisely the kind of conversation that a framework like ScrumIA seeks to open: integrating AI not as a silent imposition, but as an explicit topic for the team.

How to make the undiscussable discussable

Bringing to light what the team keeps quiet about is one of the most delicate jobs in facilitation, because by definition you are intervening on something the group is actively protecting. There are no recipes, but there are approaches that help.

Start by making it safe to speak, not by demanding that people speak. Asking for candor in an environment that has historically punished it is either naive or cruel. Before inviting people to name the difficult, you have to show, through repeated actions, that doing so won't be retaliated against. Edmondson's psychological safety is not declared; it is built reaction by reaction.

Use inquiry before assertion. Edgar Schein, in Humble Inquiry (2013), proposes that difficult truths emerge better when they are asked about with genuine curiosity than when they are asserted. "I've noticed there's a topic we seem to avoid, do you see it too?" opens more doors than "the problem here is that nobody tells the truth."

Externalize the problem. Sometimes it helps to talk about undiscussables in the abstract before the concrete: asking the team "what do you think we can't say here?" rather than pointing directly at a specific topic. Naming the category is less threatening than naming the case, and it often opens the door for someone to take the first step.

The facilitator must model vulnerability. The facilitator or leader who wants the team to name the difficult has to be willing to name something uncomfortable about themselves or the process first. Asking others for an exposure that one doesn't take on oneself rarely works.

Accept that not everything can be said, and that it's fine to start small. Making a single undiscussable, the least threatening one, discussable can set a precedent that the team extends over time. Change is gradual; trying to uncover everything at once usually provokes defensive closure.

And one final honesty is needed: sometimes the undiscussables are that way because organizational reality makes them genuinely dangerous to name. In environments where speaking has real and serious consequences, silence is not a dysfunction to correct but an understandable survival strategy. In those cases, the job is not to pressure the team to speak, but to honestly recognize the conditions that silence it and, if it is within our power, to change them.


What a team knows about itself and does not say is, in a sense, its most faithful portrait. The truths that circulate freely say little; it is the ones kept silent that reveal where the fears, the powers, and the unresolved wounds are.

Making the undiscussable discussable doesn't mean forcing confessions or breaking politeness as a rule. It means patiently and demonstrably building the conditions for telling the truth to stop being an act of risk. And it almost always begins with someone willing to name what everyone knows, accepting the small price of being the first to do so.

Bibliography

Argyris, C. (1990). Overcoming Organizational Defenses: Facilitating Organizational Learning. Allyn & Bacon. ISBN: 978-0205123384

Polanyi, M. (1966). The Tacit Dimension. University of Chicago Press (reprint 2009). ISBN: 978-0226672984

Schein, E. H. (2013). Humble Inquiry: The Gentle Art of Asking Instead of Telling. Berrett-Koehler Publishers. ISBN: 978-1609949815

Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley. ISBN: 978-1119477242

Nonaka, I., & Takeuchi, H. (1995). The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation. Oxford University Press. ISBN: 978-0195092691

Senge, P. M. (1990). The Fifth Discipline: The Art & Practice of The Learning Organization. Doubleday. ISBN: 978-0385517256

Patterson, K., Grenny, J., McMillan, R., & Switzler, A. (2011). Crucial Conversations: Tools for Talking When Stakes Are High (2nd ed.). McGraw-Hill. ISBN: 978-0071771320

Morrison, E. W., & Milliken, F. J. (2000). Organizational Silence: A Barrier to Change and Development in a Pluralistic World. Academy of Management Review, 25(4), 706-725. https://doi.org/10.5465/amr.2000.3707697

Agile Club: talking about what isn't talked about is hard, but doing it with other agilists who recognize the same dynamics helps. Share your reflection in Agile Club.

Take part in the poll

This article includes an active poll in the Scrum Manager community.

poll View the poll in the community