The Problem Your Team Won't Name Is Eating Every Other Meeting

The weekly leadership meeting runs forty minutes on a date that is slipping. Six smart people talk about staffing, a vendor that is late, and whether the Q3 plan needs another pass. Every one of them knows the actual problem: the platform rewrite the CEO championed a year ago is not going to work. It will not come up today, and it did not come up last week, because on this team it has become undiscussable.

You can watch the conversation run into it. Someone mentions that the vendor is late because the new platform keeps changing its API. Someone else says the staffing gap is really on the rewrite team. Each time, the room swerves and goes back to the vendor, and the meeting ends with three action items that treat symptoms of the thing nobody named.

I have sat in that meeting at a lot of companies, and the person running it is usually the last to see what is happening. The problem a team will not name does not stay put. It takes over the meetings around it, and then the team agrees never to mention that it is happening.

What Makes a Problem Undiscussable

The organizational researcher Chris Argyris called this an undiscussable. It is different from a secret, because nothing is hidden. Everyone knows. The team has agreed, without ever agreeing out loud, that this one subject does not get raised.

Most teams carry one of three kinds. The first is a strategy that is failing, usually one the boss picked. Then there is the leader nobody trusts, who might be the boss, or a peer the boss is protecting. The third is the person everyone works around: the brilliant engineer who wrecks every review, or the VP who has been struggling for a year.

Some things belong out of a group meeting. A colleague’s medical leave, a legal matter, or a layoff that cannot be announced yet are all fair to keep private. The test is what the silence protects. Keeping quiet to protect a person or a process that deserves it is discretion, and keeping quiet to spare the team a decision it needs to make is how an undiscussable starts.

The cost grows because everything that touches an undiscussable has to bend around it. If you cannot say the rewrite is failing, you cannot talk honestly about the roadmap, the hiring plan, or the budget, because the rewrite sits under all three. So the team argues about the parts it is allowed to discuss. Those arguments go nowhere, because the cause sits outside the conversation. People get tired. Meetings get longer. The topics that were fine to discuss a year ago start to feel risky, because they sit too close to the one that is not.

Argyris spent years watching smart executives do this, and he wrote about it in Harvard Business Review in 1986 under a sharp title, “Skilled Incompetence.” His point was that people get very good at avoiding embarrassment, and that skill is exactly what keeps the organization from learning. He described the way teams handle mixed messages as four rules nobody writes down. You send a message that contradicts itself. You act as if it does not. You make the contradiction, and the acting, undiscussable. Then you make the undiscussability undiscussable.

The fourth rule is the one that locks the door. Plenty of teams have a hard topic. The ones in trouble cannot even say, “There is something we don’t talk about.” Nobody is allowed to point at the hole, so the hole gets bigger.

The Greek word for truth is aletheia. It is built from a- (not) and lethe (forgetting or concealment), so it means something like un-forgetting. Lethe was also the river of forgetting. At the end of Plato’s Republic, in the Myth of Er, every soul about to be reborn has to drink from that river. Each one must drink a measure. The ones without wisdom drink more than the measure, and they forget everything.

A team with an undiscussable is doing that every week. Some discretion is the measure every team has to drink. The undiscussable is the extra, the part the team drinks to get out of a decision, and each person drinks a little of it on purpose to get through the meeting. Nobody notices how much the team as a whole has forgotten until someone new joins and asks the obvious question.

The Avoidance Patterns

Teams avoid the undiscussable in a few common ways. Each one feels responsible at the time.

1. The Side Door

The team talks about the symptoms because the cause is off limits. The date slips, so you add a status meeting. When two engineers ask to leave the rewrite team, you open a req, and when the vendor misses again, you escalate.

All of that is real work, and all of it is aimed at the wrong target. What the team is avoiding is the one sentence that would make half the agenda unnecessary: this plan is not working and we need to decide what to do about it.

2. The Hallway Version

The real meeting happens after the meeting. Two directors walk to the parking lot and say what they think. Someone sends a DM that starts with “Am I crazy, or…” The chief of staff hears the truth in four separate one-on-ones and carries none of it back to the room.

Leaders often take the hallway version as proof that the problem is handled. People are talking about it, after all. They are talking about it in every place where it cannot change a decision. The hallway lets everyone feel honest while the official record stays clean, and the official record is what the company acts on.

3. Waiting for Data

Someone asks for one more analysis. Let’s get the numbers on the rewrite before we decide anything, or wait for the engagement survey, or give the new VP one more quarter.

Sometimes you really do need the data. More often, the room already answered the question privately, and the request for data buys time without anyone having to say what they believe. You can test this. If every person in the room would bet their own money on the same answer, the data is not what you are missing.

4. The Kind Exception

Sometimes the undiscussable is a person, and the team protects them. It might be the star engineer who makes juniors cry in code review, or the VP who is having a hard year and has stopped doing the job. The founder’s favorite product gets the same protection.

It feels kind, and it costs the team every week in rework and in people who stop raising their hands. Meanwhile the person being protected is the last one to find out what everyone thinks of their work. The kind move is to tell them directly and privately, early, before the team has paid for a year of silence. I wrote recently that soft feedback is kind to you and expensive to them. An undiscussable person is that same trade, made by a whole team at once.

What Works

The leader is usually either the topic or the reason it cannot be raised. Most teams learned what is off limits by watching what happened to the last person who brought it up. That means the leader has to go first, and then has to make it safe for the second person, because the second person is the one taking the real risk. None of that excuses anyone else at the table. The leader going first makes it easier to speak, and every person who stays quiet in the meantime is still choosing to.

In my experience, the meeting where someone finally names the thing gets shorter. Half the agenda was symptoms, and the symptoms stop needing their own slots.

Name it as a topic, not as an accusation. Say it in the meeting, plainly: “There’s something we keep going around. I think it’s that the rewrite isn’t working. Tell me if I’m wrong.” Nobody has to agree with you. The point is to get the subject on the table, where people can disagree out loud instead of in the hallway.

Say the fourth rule out loud. Add one more sentence: “We’ve also never talked about why we don’t talk about this.” That sentence breaks the lock Argyris described. If the reason is you, say that too: “I think some of it is that this was my call, and I’ve reacted badly when it came up.”

Thank the first person who joins you, in public, the same day. Whoever adds the second honest sentence is watching what happens to them. If they get a thank-you in front of the team, the next person speaks sooner. If they get a long silence and a tense one-on-one, you have taught the team the same lesson again. The Blue Angels debrief works because declaring the miss is expected and praised.

Run the left-hand column on your last hard meeting. This is Argyris’s exercise, made popular by Peter Senge. Take a sheet of paper and draw a line down the middle. On the right, write what was said in a recent tough conversation. On the left, write what you thought and did not say. Most leaders find their undiscussable on the left side within ten minutes.

You can get a second read from a model. Paste the notes from your last ten leadership meetings or retros into Claude and ask one question: what problem keeps coming up from the side without ever being named? The model has no idea what your team agreed not to say. It reads the notes and tells you which subject they keep circling. That is a cheap way to find what you have stopped seeing.

Put it on the agenda by name, with a date. “Rewrite: keep, change, or stop. Decision by the 20th.” Writing it down moves the subject out of the hallway and into the record. It also tells the team the leader expects to talk about it, which is the opposite of the lesson they learned.

None of this works if the meeting itself is built to protect the boss’s view. If that is your problem, start with how meetings are designed so nobody changes their mind. And if you are not the leader, the cost of staying quiet still lands on you. You can still be the second person, and that is often the harder seat. What you control is saying it plainly and fairly, in the room where the decision gets made. You do not control how the room or the boss reacts, and a bad reaction does not make saying it wrong.

The Test

Answer these about your own team this week.

What is the one topic that would change the tone of your next leadership meeting if someone raised it?

Where did you last hear the honest version of it: in the meeting, or in the hallway afterward?

Which of your current action items exist only because the real cause is off limits?

What happened to the last person who brought it up? Did you thank them, or did you make them pay for it?

If a new hire asked about it in their first week, what would you say?

FAQ

What is an undiscussable in a team?

An undiscussable is a problem the whole team knows about and has stopped raising, such as a strategy that is failing, a leader nobody trusts, or a person everyone works around. The organizational researcher Chris Argyris used the term. It is different from a secret, because nothing is hidden. The team has simply agreed, without ever saying so, not to talk about it.

Why do undiscussables spread?

Every topic that touches the forbidden one has to be bent around it. If the team cannot say the platform rewrite is failing, it ends up arguing about headcount, vendors, and dates, which are all symptoms of the rewrite. Argyris also noticed that teams make the undiscussability itself undiscussable, so nobody can even point out that a topic is off limits.

How does a leader bring up an undiscussable?

Name it as a topic, not an accusation, and go first. Say what you think the team keeps going around, ask to be told if you are wrong, and say out loud that the team has also never talked about why it avoids the subject. Then thank the first person who adds to it, in public, the same day. Put the topic on the agenda by name with a date.

What does aletheia mean?

aletheia is the ancient Greek word for truth. It is built from a- (not) and lethe (forgetting or concealment), so it means something close to un-forgetting or un-hiding. Lethe is also the river of forgetting in Greek myth. In Plato’s Republic, every soul drinks from it before rebirth, and those without wisdom drink more than they need.

Final Thoughts

Every team has at least one problem it has agreed not to name, and that problem shapes every meeting near it. Argyris showed how the silence locks itself in: first the topic becomes undiscussable, then the silence about it does. The leader is usually part of why it is off limits, so the leader has to say it first, say why nobody says it, and thank the second person in front of everyone. Naming it gives the team back something it already knew and had agreed to forget. Then put it on the agenda with a date, and the meetings around it can get back to their real work.

Learning to say the hard thing first, and to make it safe for the person who says it second, is part of the work of leading with excellence. That is what MasteryLab is for.