In 1970, three organizational researchers asked managers a set of strikingly ordinary questions. Did they know exactly what was expected of them? Were they certain how much authority they had? Were the goals of their jobs clear?
None of the questions asked who their manager was.
A person can know that perfectly and still have no idea who owns the customer complaint, the hiring decision, or the handoff that keeps missing Friday. The reporting line is clear. The work is not.
That is role ambiguity at work: uncertainty about responsibilities, authority, priorities, standards, or how a role is meant to contribute. It is not the same as solving a genuinely uncertain problem. A team can be exploring new ground and still know who decides, who does the work, and who raises a flag when the plan stops making sense.
The org chart is not defective. It is being asked to answer a question it was never designed to answer.
An org chart records formal relationships. Ownership is an operating agreement. Teams need both, and decades of research suggest the space between them is not harmless.
The answer is not necessarily a 73-row responsibility matrix. It is making the few consequential decisions, outcomes, and handoffs too clear to become communal fog.
What role ambiguity at work actually means
Role ambiguity at work is the absence of information someone needs to understand their role and perform it with reasonable confidence. The missing information may concern duties, priorities, authority, methods, standards, evaluation, or the relationship between one person's work and everyone else's.
John Rizzo, Robert House, and Sidney Lirtzman helped give the idea a durable measurement system in their 1970 study of role conflict and ambiguity. Their questions covered six practical areas: authority, goals, time allocation, responsibilities, expectations, and the clarity of instructions.
That list has aged rather well. The question about dividing time sounds especially current for a sentence written before Slack could place three red badges beside it.
The study also separated ambiguity from role conflict. Ambiguity means you do not know what the role requires. Conflict means you receive requirements that pull in incompatible directions.
A product lead who does not know whether they can approve a launch has ambiguity. A product lead told to launch Friday and not accept any unresolved risk has conflict. Many jobs provide both, as a bundle.
The original scales became enormously influential, but not untouchable. In 2017, Nathan Bowling and colleagues noted that researchers had long disputed parts of their validity, then developed and tested newer measures across five studies. That is how a healthy research field works. A useful early measure becomes a foundation, then later researchers inspect the foundation instead of polishing a plaque for it.
The practical definition is less fragile than any one questionnaire. If capable people repeatedly have to guess what matters, who decides, or how success will be judged, the organization has created ambiguity. Calling them insufficiently proactive does not supply the missing information.
Why org charts and role clarity answer different questions
An org chart answers questions about formal structure:
- Who reports to whom?
- Which roles sit in which team or function?
- Who manages this part of the organization?
- Where does an escalation travel next?
Those are not small questions. Safe Work Australia treats prolonged or severe lack of role clarity as a psychosocial hazard, and it recommends clear reporting lines and an organizational chart as part of the response.
But "part" is carrying the sentence. The same guidance also names overlapping responsibilities, conflicting standards, missing information, and unclear priorities. A clean line between two boxes cannot tell you who approves a refund, which team maintains the onboarding email, or what happens when Finance and Sales disagree about a contract exception.
Formal structure and operating ownership live at different resolutions:
| The org chart can show | The operating agreement must show |
|---|---|
| Formal manager | Owner of the outcome |
| Team and function | Contributors and handoffs |
| Position and title | Decision rights and limits |
| Escalation route | When escalation should happen |
| Stable reporting relationship | Current priorities and definition of done |
One is not the grown-up version of the other. They are two layers of the same organization.
This also explains a limitation in Google's Project Aristotle findings. Google named structure and clarity as one of five important team dynamics, alongside psychological safety and dependability. Its internal survey asked whether people understood job expectations, the process for fulfilling them, and the consequences of performance.
An org chart can support that clarity. It cannot finish the work alone. The boxes tell people where roles formally live; the team still has to agree what those roles are for.
What six decades of role-ambiguity research found
The strongest current summary is unusually large. A 2026 meta-analysis in the Journal of Vocational Behavior synthesized 515 studies, 588 samples, and 787,959 participants. It compared three related stressors: role ambiguity, role conflict, and role overload.
Role ambiguity was the most damaging overall. Across 14 employee and organizational outcomes, it explained the greatest share of variance in many of them.
That does not mean an unclear approval path caused every case of burnout, low engagement, or poor performance in nearly 800,000 people. Meta-analysis can combine a large body of evidence, but much of that evidence remains correlational and relies on people's reports of their work. The finding is broad and serious, not magical.
The more specific results point in the same direction. Travis Tubre and Judith Collins combined studies of role stress and performance in 2000. Their meta-analysis found a negative correlation of r = -.21 between role ambiguity and job performance. Role conflict showed a much smaller relationship with performance, r = -.07.
A correlation of -.21 is not a 21% loss in output, and it does not predict what will happen to one employee. It says that, across the evidence studied, greater ambiguity tended to travel with poorer performance. Job type and the source of the performance rating also changed the strength of the relationship.
The human cost is not confined to output. A meta-analysis of 33 studies and 19,926 participants found moderate positive relationships between depressive symptoms and both role ambiguity (r = .279) and role conflict (r = .318). The authors argued that clearly defined roles and job objectives can contribute to employee health.
Again, this is not a diagnostic tool. Depression has many causes, and no manager should turn one workplace correlation into amateur medicine. The evidence does justify treating chronic role confusion as a work-design problem, not a charming feature of a "fast-moving culture."
Ambiguity is not free. The invoice arrives through extra checking, duplicated work, slow decisions, avoidable conflict, and the private effort of trying to infer rules nobody has stated.
Ownership is not the same as blame
When managers hear "unclear ownership," the reflex is often to demand more accountability. This can help, provided everyone means the same thing by the word.
In everyday team language:
- Responsibility is the work a person agrees to perform.
- Authority is the permission to decide, approve, spend, or direct resources.
- Accountability is the obligation to answer for how an outcome was handled.
- Ownership is the practical bundle: keep the outcome moving, coordinate contributors, make or obtain decisions, surface risk, and close the loop.
These are working definitions, not laws of physics. Different organizations use the labels differently. The useful test is whether the team can answer the underlying questions without arguing about the glossary.
Accountability itself is not reliably good in every form. Angela Hall, Dwight Frink, and Ronald Buckley reviewed the empirical research on felt accountability and found both constructive and harmful consequences. Results depended on context, including how accountability was created and experienced.
That should not be surprising. Clear ownership with enough authority can focus attention and improve coordination. Accountability without control, resources, or fair evaluation is just pressure with a name tag.
This is where psychological safety and accountability belong together. An owner has to be able to report that an outcome is at risk before the deadline. If ownership means being the person blamed after other people withhold information or decisions, the rational response is to make bad news look green for longer.
A name in a box without authority is not accountability. It is a future scapegoat with formatting.
Is a RACI matrix useful or just another spreadsheet?
A RACI matrix maps work against four kinds of involvement:
- Responsible: does the work.
- Accountable: answers for the outcome and approves completion.
- Consulted: provides input before a decision or action.
- Informed: needs the result or progress communicated.
Official guidance from Microsoft and the U.S. Naval Facilities Engineering Systems Command recommends one accountable person or role for each assignment. The Navy guidance adds an essential condition: the accountable person needs the authority to execute the assignment.
That one-owner rule is sensible for most live decisions and outcomes. If two people can independently give the final answer, the team needs a rule for what happens when the answers differ. Sometimes governance is genuinely collective, as with a board vote or formal committee. In those cases, document the decision rule instead of pretending the collective body is one person.
RACI is useful because it forces an awkward conversation while changes are still cheap. It makes overlaps, blank spaces, and ceremonial consultation visible.
RACI is not evidence. It is notation.
There is little peer-reviewed evidence that filling in a RACI matrix, by itself, improves team performance. It can also become an impressive piece of administrative upholstery: hundreds of tasks, eight consulted stakeholders per row, and no living person willing to open the file after kickoff.
Use it for the work where confusion is expensive:
- recurring cross-team processes;
- decisions with regulatory, financial, or customer consequences;
- handoffs that repeatedly stall;
- outcomes with several contributors but no obvious coordinator;
- new work created by a reorganization or leadership change.
Do not build one for every calendar invitation and coffee order. The difference between clarity and bureaucracy is not the framework. It is whether the framework helps someone make a real decision.
How to reduce role ambiguity at work without building a bureaucracy
Start with outcomes, not job descriptions. Job descriptions describe the territory of a role. Ambiguity usually appears at the borders, where live work passes between roles.
Choose one meaningful outcome that has recently stalled, duplicated, or required a rescue. Ask the people involved to answer these questions separately:
- Who owns the outcome? Name one person for the live work, even if many people contribute.
- What can that owner decide without further approval? Write the boundary, including spending, scope, quality, or timing limits.
- What counts as done? Name the result and standard, not just the activity.
- Who is responsible for each material contribution? Keep this at the level of consequential work, not keystrokes.
- Which inputs or handoffs can stop progress? Name both the dependency and its owner.
- When must risk be raised, and to whom? "Use your judgment" is not an escalation path.
- When will this agreement be reviewed? Ownership drifts as work and people change.
Compare the answers. If three experienced people name three different owners, you have found the ambiguity before it becomes another meeting about alignment.
Write the final agreement somewhere people will look when the work is live. That may be a short RACI, a decision log, a project brief, a service-ownership page, or six lines in the tool the team already uses. The format is secondary. A beautifully governed document nobody consults is still nobody's operating model.
Then test authority against accountability. Can the owner obtain the information, decision, time, and resources the outcome requires? If not, either move the authority or move the ownership. Leaving them separated creates a role that is answerable for other people's optional cooperation.
Finally, watch what happens at the handoffs. Our article on team dependability argues that follow-through is a property of the team system, not only individual character. Clear ownership makes a promise visible. Clear handoffs make it possible to keep.
What belongs on the org chart, and what belongs beside it
The answer is not to cram every decision into the org chart. That produces a diagram nobody can read and a maintenance job nobody requested.
Keep the chart focused on the durable formal structure: people, roles, teams, managers, and reporting relationships. If the chart is wrong, fix the underlying organizational data first. An inaccurate hierarchy creates its own category of confusion.
Beside it, maintain a lightweight ownership layer for the work that crosses boxes. Use an outcome map, responsibility matrix, decision record, or service catalog. Pick the smallest artifact that can answer who owns the result, what they can decide, and where a blocked handoff goes next.
The two layers should disagree only on purpose. A cross-functional project owner may not manage every contributor. A service owner may sit several lines away from the people who operate it. That is normal, provided the difference is explicit.
Trouble begins when the formal chart is treated as proof that ownership must be obvious. The org chart says who manages the person. It does not silently appoint an owner for every piece of work near their box.
Frequently asked questions
What is role ambiguity at work?
Role ambiguity at work is uncertainty about what a role requires, including its responsibilities, priorities, authority, standards, methods, or expected contribution. It differs from ordinary uncertainty in complex work. A problem can have an unknown answer while the team remains clear about who decides, who contributes, and how progress will be judged.
What is the difference between role ambiguity and role conflict?
Role ambiguity means the expectations or boundaries of a role are unclear. Role conflict means the expectations are known but incompatible. Someone who does not know whether they can approve a purchase faces ambiguity. Someone ordered to reduce cost and buy the premium option without a priority rule faces conflict.
Can an org chart improve role clarity?
Yes. An accurate org chart clarifies reporting relationships, team membership, formal management, and escalation paths. It cannot, by itself, specify every outcome owner, decision right, handoff, priority, or quality standard. Treat the chart as the structural layer and keep a lightweight ownership layer beside it.
Should every task have one accountable owner?
Every consequential live outcome or decision usually benefits from one clearly accountable person or role. Not every tiny task needs a RACI row, and some formal governance decisions are genuinely collective. When accountability is collective, document how the group reaches a final decision and who coordinates the process.
Does a RACI matrix solve role ambiguity?
Not by itself. A RACI matrix can expose missing or duplicated ownership and clarify who does, approves, advises, and receives information. It works only when the assignments reflect reality, the accountable owner has enough authority, and the team uses the matrix during live work. Otherwise, it is a spreadsheet confirming that a workshop occurred.
The 1970 researchers asked whether people knew what was expected, understood their authority, and had clear goals. More than half a century later, those remain better tests of role clarity than a tidy reporting line.
Draw the structure accurately. Then name who owns the work between the boxes.