When Role Sheets Go Missing: How Ambiguity Rewires Team Communication, Trust, and Output

I have spent the better part of seven years watching teams fall apart. Not in the dramatic, shouting-match sense—those are actually easier to fix. I mean the quiet kind of disintegration: the weekly check-in where nobody quite knows who owns the next step, the Slack thread where three people duplicate work while one person sits idle, the post-mortem where everyone agrees the problem was “communication” without anyone specifying what that means.
 

This is the signature pathology of role ambiguity. And if you have spent any time in cross-departmental projects, virtual teams, or matrix organizations, you have lived it. The data backs this up: a 2025 study of 280 hospital employees across nine hospitals found that role ambiguity was the most important variable affecting team performance—not task conflict, not relationship conflict, but the sheer absence of clarity about who does what. Another study of 198 respondents in intergenerational workplaces showed that role clarity has a significant positive effect on performance (β = 0.227, p < 0.05), with team cohesion mediating that relationship (β = 0.381, p < 0.001). When people understand their roles, they perform better. When they do not, everything else breaks.
 

But here is what the simple correlation obscures. Role ambiguity does not just lower performance in a straight line. It rewires the entire social architecture of a team through three interconnected channels: role definition itself, communication frequency, and intermember trust. Understanding these channels—and how they interact—is the difference between diagnosing a team as “dysfunctional” and actually knowing what to do about it.
 

Channel One: Role Definition as Cognitive Anchor
 

Let us start with the most obvious channel because it is also the most misunderstood. Role clarity is not about having a job description. Job descriptions are static documents that sit in HR folders and get updated once a year during performance reviews. Role clarity is about real-time understanding: in this specific project, with these specific people, facing these specific constraints, what am I accountable for?
 

Adora Svitak, in her 2010 TED talk, made a deceptively simple observation: adults dismiss “childish” thinking as naive, but children’s willingness to ask “why” and imagine alternatives is precisely what adults lose as they become socialized into organizational life. Svitak argued for reciprocal learning—adults have experience, but children have imagination, and both are necessary. I would extend that argument to teams. Role ambiguity thrives in environments where nobody asks the childish question: “Why are we doing it this way? Who decided that this is my job?”
 

When role definitions are unclear, team members default to one of two coping strategies. The first is role retreat: pulling back, doing only what is explicitly asked, and waiting for instructions. This looks like low engagement, but it is actually rational behavior under uncertainty. The second is role expansion: stepping into ambiguous space and claiming it, which can be productive but just as often creates overlap, duplication, and resentment.
 

A 2025 study on distributed teams found that autonomy has a curvilinear relationship with manager effectiveness—too little autonomy is bad, but too much is also bad, and the sweet spot depends critically on the manager’s own role clarity. In other words, you cannot delegate authority to people who do not know what authority they have. That is not empowerment; that is abandonment.
 

Channel Two: Communication Frequency as Diagnostic Signal
 

Here is where the research gets interesting. Role ambiguity does not just reduce communication; it changes the kind of communication that happens. When roles are clear, team conversations are about task execution: “Here is what I am doing, here is what I need from you, here is the timeline.” When roles are ambiguous, conversations become about role negotiation: “Wait, are you handling that? I thought I was handling that. Who is supposed to approve this?”
 

This shift is costly. A study examining the mediating effects of task conflict and relationship conflict found that role ambiguity operates through both direct and indirect pathways. The direct effect is straightforward: unclear roles mean wasted effort. The indirect effect is more insidious: unclear roles generate task conflict (disagreements about what to do), which then escalates into relationship conflict (disagreements about who people are).
 

I have seen this play out in cross-functional teams more times than I can count. A product manager, a designer, and an engineer walk into a room—this is not a joke, it is every Monday morning. Nobody has explicitly defined who owns the final decision on feature scope. The product manager assumes they do because they wrote the requirements. The designer assumes they do because they own the user experience. The engineer assumes they do because they know what is technically feasible. Three reasonable people, three conflicting assumptions, zero explicit conversation.
 

The result is not just inefficiency. It is a steady erosion of psychological safety. When people do not know who is accountable, they stop speaking up. They hedge their commitments. They document everything in CYA emails. Communication frequency might actually increase under role ambiguity—but it becomes defensive, not productive.
 

Channel Three: Intermember Trust as the Canary in the Coal Mine
 

This brings us to the third channel, which is where the real damage accumulates. Trust is not a warm fuzzy feeling; it is a cognitive shortcut. When I trust you, I do not have to verify every decision you make. I can assume good intent and focus on my own work. When trust erodes, I spend mental energy monitoring, second-guessing, and protecting myself.
 

Role ambiguity is a trust killer. A 2025 study on team cohesion explicitly modeled this pathway: job-adequate skills and participative leadership had positive effects on team trust, but role ambiguity had a negative effect on team trust. The mechanism is straightforward. When roles are unclear, I cannot predict what you are going to do. If I cannot predict your behavior, I cannot rely on you. If I cannot rely on you, I do not trust you. And if I do not trust you, I do not collaborate—I compete.
 

The 2023 virtual team performance literature reinforces this. Role clarity acts as a mediator between external leadership roles and conflict, while communication quality mediates the relationship between leadership and trust. These are not separate problems; they are the same problem manifesting at different levels. Role ambiguity → poor communication → low trust → more role ambiguity. It is a vicious cycle, and it is self-reinforcing.
 

What makes this particularly challenging is that trust, once damaged by role ambiguity, is hard to rebuild. A 2025 study on human-AI teaming found that information omissions significantly reduce team trust, which in turn hinders communication efficiency and overall performance. The same logic applies to human teams. When people cannot count on each other to fulfill predictable roles, they stop sharing information. They hoard it. Because information is power, and when you do not know where you stand, power is all you have left.
 

The Output Logic: From Ambiguity to Underperformance
 

So here is the full chain. Role ambiguity does not cause low performance directly. It causes low performance through a sequence:

1. Unclear role definitions → people do not know what to do or who owns what

2. This generates task conflict → time and energy spent on negotiation instead of execution

3. Task conflict escalates into relationship conflict → people take disagreements personally

4. Trust erodes → communication becomes defensive and information hoarding increases

5. Coordination breaks down → output suffers

The hospital employee study I mentioned earlier found that role ambiguity had both direct and indirect effects on team performance, making it the most important variable in their model. That is not a trivial finding. It means role ambiguity is not just one problem among many; it is the problem that makes other problems worse.
 

This is why I reject the simple “cohesion → performance” correlation that dominates practitioner literature. Cohesion without clarity is just groupthink. A team that gets along but does not know what it is doing is not a high-performing team; it is a support group. The data from the intergenerational workplace study makes this clear: team cohesion mediates the relationship between role clarity and performance, but role clarity comes first. You cannot cohesion your way out of ambiguity.
 

What This Means for Practice
 

If you are leading a team, here is what the research tells you to do.
 

First, stop assuming that roles are clear just because you think they are. A 2025 study found that role clarity deficiencies can wreck agile teams, leading to high employee turnover. Run a simple audit: ask every team member to write down their top three responsibilities and their top three decision rights. Compare the answers. If they do not match, you have a problem.
 

Second, treat role clarity as an ongoing process, not a one-time exercise. Distributed teams, in particular, need frequent recalibration because the context shifts faster than the documentation. A diary study of 150 distributed workers found that daily communication patterns moderated the impact of autonomy on team coordination. That means you cannot set roles in January and expect them to work in July. You have to talk about them. Constantly.
 

Third, watch for the warning signs. Francesca Gino, who studies organizational behavior, notes that “drama usually grows out of ambiguity, not tension”. Common signs of role ambiguity include phrases like “I didn’t want to step on their toes” or “I’m not trying to throw anyone under the bus, but...”. These are not statements of humility; they are statements of confusion. When you hear them, intervene.
 

Fourth, and this is where Svitak’s argument becomes relevant, create space for the “childish” question. Why are we doing it this way? Who decided? What if we tried something different? Adults in organizations are socialized to accept ambiguity as normal. Children are not. The best teams I have studied maintain a kind of productive naivete—they refuse to accept “that’s just how we do things” as an answer. They clarify roles not because they are bureaucratic, but because they want to get things done.
 

The Bottom Line
 

Role ambiguity is not a soft HR issue. It is a hard performance issue with measurable effects on communication, trust, and output. The research is consistent across contexts—hospitals, distributed teams, intergenerational workplaces, sports teams. When people do not know what they are supposed to do, they do not do it well. More importantly, they stop trusting each other, and once trust is gone, performance collapses.
 

The fix is not complicated, but it is uncomfortable. It requires leaders to stop assuming and start asking. It requires teams to have awkward conversations about who owns what. It requires the willingness to sound childish—to ask the basic questions that everyone else is avoiding.
 

Svitak ended her talk with a challenge: adults need to start learning from kids, not just teaching them. In the context of team performance, that means learning to ask the simple questions again. What are we doing? Who is doing it? How will we know if we succeed? These are not naive questions. They are the only questions that matter.

Source Reference Link: https://www.ted.com/talks/adora_svitak_what_adults_can_learn_from_kids

Link Brief: Child prodigy Adora Svitak challenges the one-way stereotype that only adults hold wisdom. She argues the word “childish” is unfairly used as an insult, while children possess boundless imagination, bold optimism and unrestrained creative thinking that adults gradually lose with age. She advocates reciprocal learning between children and grownups: adults must listen to kids’ wild ideas to build a more innovative, hopeful world.