The Most Common Root Cause in a Stuck Product Team Is Someone Avoiding a Conversation

When I'm diagnosing a struggling product team and I can't find the systems cause, I ask one question: who isn't saying the thing that everyone half-knows needs to be said?

It's a strange question to lead with, because it isn't about process, tooling, architecture or headcount. But it's the one that most often gets me to the bottom of things. The most common root cause I find in a stuck product team is conflict avoidance – someone, somewhere, declining to have an uncomfortable conversation with a colleague, with a boss, or with the hard work itself.

That's a stance from the teams I've worked with. Nobody has measured "the most common root cause of stuck product teams," and I'm not going to put a percentage on it. What the research does show is that avoided conversations are close to universal, that they cluster on exactly the topics that stall product teams, and that they keep bad news away from the people with the authority to act on it.

What avoidance looks like on a product team

Conflict avoidance rarely looks like someone hiding under their desk. It looks like reasonable behavior, and it shows up in a lot of costumes.

It's the product manager who won't do the hard, lonely work of deciding what to build, and instead pulls engineers into "collaborating" on the problem so no single person owns a decision that might turn out to be wrong. It's the manager who won't tell a struggling employee the truth, so the problem festers for a year. It's the team lead who knows the CEO's pet project is a bad idea and builds it anyway, because saying so feels dangerous. And it's all of us, at one time or another, doing five easy things to put off the one hard thing that matters, and calling ourselves busy.

That last one is the version people don't recognize as conflict. The work is hard – understanding the user deeply, deciding whether a problem is big enough to be worth solving, admitting that we don't actually know yet – and it's very human to route around hard work the same way we route around a hard conversation.

The research on employee silence lines up with this closely. In an interview study of 40 employees by Milliken, Morrison and Hewlin, 34 said they had at least once felt unable to raise an important issue with their boss, and only about half said they generally felt comfortable speaking up. The most common topic people held back on was the performance or competence of a colleague or boss, which 37.5% mentioned. The most common reason was fear of being labeled negatively and damaging relationships they valued.

On a product team, that's the conversation about whether the plan is any good and whether the person who owns it is getting it right.

Decision ownership is another hot spot. In a 2021 survey by Crucial Learning, which sells training on difficult conversations, 53% of respondents said they avoid the conversation when there's confusion about who owns a decision. I once found ten well-written tickets for a decision nobody had made, which is what that avoidance looks like once it reaches the backlog.

It's a property of the system, not a flaw in a person

I've argued before that what looks like a people problem is usually the system, and I don't think this contradicts it. Avoided conversations are something the system produces.

Morrison and Milliken describe organizational silence as a collective phenomenon: forces inside an organization that produce "widespread withholding of information about potential problems," and a shared perception that speaking up is unwise. Detert and Edmondson found that people carry taken-for-granted rules about when speaking up is risky, and those rules suppress even suggestions that would help the organization.

There are kind and skillful ways to have every one of these conversations. Most people were simply never taught them, so they route around the discomfort, and the routing-around becomes the dysfunction. Nobody needs to be blamed for that. But somebody does need to find it, because it's where a diagnosis can actually take hold.

I'd also call it a recurring contributing cause rather than the single root that explains everything. Real problems usually have several causes tangled together. The avoided conversation is just the one I find most often, and the one that keeps the other causes from being addressed.

Why the founder is often the last to hear it

This part matters most for anyone running the company.

Research on troubled IT projects has a name for the reluctance to report bad news upward: the MUM effect. Keil and colleagues wrote that when large projects go wrong, "it often takes weeks, months, and sometimes even years, before senior management becomes fully aware of what has happened." The bad news is there the whole time. It's softened, delayed or left unsaid on its way up.

Put that next to the silence research and a pattern emerges. The conversations people avoid most are about the competence of a boss and the quality of a plan, and in a founder-led company the boss is often the founder and the plan is often theirs. That means the founder is frequently one of the people being avoided, which makes them structurally the last to know. That has nothing to do with whether they're paying attention. The information is being routed around them by people who care about their jobs and their relationships.

I've seen this from the other side, too. I once wrote down eight risks to a product and watched all eight happen while the room acknowledged them and moved on. Seeing a problem and getting it acted on are two very different things.

Psychological safety is the weather, not the diagnosis

If you search for this topic, most of what you'll find is about psychological safety, and it's a real and important idea. Amy Edmondson's 1999 study of 51 work teams found that a team's shared belief that it's safe to take interpersonal risks was associated with learning behavior, which in turn was associated with performance. When Google studied 180 of its teams in Project Aristotle, psychological safety came out first among the dynamics that mattered.

But psychological safety describes the climate. It tells you whether conversations are likely to happen in general. It doesn't tell you which specific conversation isn't happening on your team right now, between whom, about what – and that's the thing you need to know to get a stuck team moving again. Launching a program to build safety is a fine long-term goal. It won't find the PM who's been avoiding a decision for months.

The one diagnostic question

So here's the question again, and it works whether you're an outsider diagnosing a team or a leader looking at your own: who isn't saying the thing that everyone half-knows needs to be said?

Usually there's an answer, and usually several people already know it. Someone suspects the roadmap is built on a guess. Someone knows a colleague is out of their depth and has been covering for them. Someone thinks the pet project is a mistake and hasn't found a safe way to say so. Someone has been doing everything except the one hard piece of work that would unblock the rest.

When the team is yours, it's worth asking one more question alongside it: is the conversation being avoided one that's supposed to happen with me? If the answer is yes, the fix starts with you making that conversation cheap enough for someone to have.

A stuck team is often one conversation away from moving again, and somebody in the room already knows which one.