Most teams don't fail because someone did their job badly. They fail because a job sat in the gap between two people who each assumed it belonged to the other. Role and expectation clarity is the deliberate work of closing those gaps, naming who decides, who delivers, and what "done" actually means, before the ambiguity turns into a missed deadline and a tense retro.

The quick version

  • Role clarity is knowing who owns what, the decision, the delivery, the sign-off. Expectation clarity is knowing what good looks like and by when. They are different problems and both have to be solved.
  • The fog has a name in the research: role ambiguity, when you're unsure what's expected of you. A meta-analysis of dozens of studies found it has a real, negative link to job performance.
  • The fastest fixes are concrete: assign decision rights (who has the final call), use a RACI or similar to split responsible from accountable, and write down a standard of "done."
  • The honest caveat: clarity can curdle into rigidity. Over-specify and you get box-tickers who won't step outside their square. The aim is fewer collisions, not a job description for every breath.

The idea in depth

The discomfort of not knowing what's expected of you isn't a personality quirk; it's a measurable organisational condition with a fifty-year research trail. The foundational work is Robert Kahn and colleagues' Organizational Stress: Studies in Role Conflict and Ambiguity (Wiley, 1964), which framed the workplace as a set of overlapping roles defined less by a job title than by the expectations other people send you. When those expectations are missing, vague, or contradictory, you get two distinct failures: role ambiguity (you don't know what's expected) and role conflict (you're getting incompatible demands). Kahn's team didn't treat this gently, sustained role conflict, they wrote, is in its extreme form "identity destroying," not merely irritating. Which is why confusion is worth reading as a signal rather than a weakness. When someone on your team keeps asking "wait, is that mine?", that's not them being needy. That's an unsent expectation you owe them.

A few years later, John Rizzo, Robert House and Sidney Lirtzman turned the concept into something you could measure. Their paper "Role Conflict and Ambiguity in Complex Organizations" (Administrative Science Quarterly, 1970) built a questionnaire, a six-item role-ambiguity scale and an eight-item role-conflict scale, that proved the two were statistically separable, not the same fog under different names. That distinction matters in practice. Ambiguity is fixed by information (here's what's expected, here's what good looks like). Conflict is fixed by arbitration (these two demands can't both win, which one yields?). Diagnose before you prescribe, then: is the person missing the expectation, or drowning in two that contradict? Push more clarity at a conflict problem and all you've done is make the trap better-lit.

flowchart TB
  S(["Symptom:
work stalls, rework, finger-pointing"]) --> Q(["Which failure is it?"])
  Q --> A(["Role ambiguity
(unsure what's expected)"])
  Q --> C(["Role conflict
(incompatible demands)"])
  A --> AF(["Fix with information:
decision rights · RACI · standard of done"])
  C --> CF(["Fix with arbitration:
name the priority · who yields · escalate"])
Two different problems wearing the same symptom, and the different move each one needs. Leaders Loop

Does any of this actually move performance, or is it just comfort? Here the evidence is more honest than the management-poster version. Travis Tubré and Judith Collins ran a meta-analysis pooling dozens of studies (Journal of Management, 2000) and found role ambiguity had a modest but real negative relationship with job performance, a corrected correlation of about r = −0.21, stronger for some job types than others. Notably, they found role conflict's link to performance was close to zero (around r = −0.07). The lesson is not "all role stress kills output." It's narrower and more useful: not knowing what's expected reliably drags on performance; being pulled in two directions hurts your wellbeing more than your output. So if you only have time to fix one thing, fix the ambiguity. For each person, make one sentence answerable, "what does a great month look like in this role, and who decides it's great?" If they can't answer it, you've found your work.

Most "underperformance" is just an expectation that was never actually sent.

What does "sending the expectation" look like concretely? This is where role theory meets the best-evidenced idea in work motivation: goal-setting. Across more than four decades of studies, Edwin Locke and Gary Latham showed that specific, challenging goals beat vague "do your best" goals in the large majority of cases, because a specific goal directs attention and effort, while "do your best" gives the mind nowhere to aim ("New Directions in Goal-Setting Theory," Current Directions in Psychological Science, 2006). The catch they're equally clear about: the effect only holds when the person has the skill and genuinely commits to the goal. The practical version is to replace adjectives with a standard, not "own the launch well" but "launch is live by the 30th, zero P1 bugs, and you've personally signed off the comms." A standard of done is just an expectation made specific enough to be checkable.

The structural tool for splitting all this across people is the RACI matrix, Responsible, Accountable, Consulted, Informed. Be honest about its provenance: RACI has no single famous inventor and no underlying study; it grew out of project-management and consulting practice and has been in everyday use since at least the 1970s–80s (responsibility-assignment matrices, overview). Its value is one disciplined distinction: Responsible (does the work) is not the same as Accountable (carries the consequences and has the final yes/no), and there should be exactly one Accountable per decision. When everyone's accountable, no one is. A more rigorous cousin for high-stakes calls is Bain's RAPID model, set out in Paul Rogers and Marcia Blenko's "Who Has the D?" (Harvard Business Review, 2006), which separates the right to recommend, to agree (veto), to give input, to decide, and to perform, and insists on a single Decider. Both point at the same small habit: for your next contested piece of work, write one line, "X decides, Y delivers, Z is consulted", and read it aloud to all three. The disagreement you surface in ninety seconds is the disagreement you'd otherwise discover in week six.

An honest limitation. Clarity has a failure mode, and it's the opposite of fog. Over-specify roles and you breed the box-ticker, the person who lets a fire burn because putting it out "wasn't in my RACI." The research backs the caution: clarity helps performance, but the same role literature documents how rigid, narrow roles suppress the discretionary effort and helping behaviour that good teams run on. A RACI is a starting contract, not a fence. The best leaders pair a clear "this is yours" with an explicit "and when something falls in the gap, I'd rather you grabbed it than guarded your edge." Clarity tells people where the lines are; culture tells them it's safe to cross one when the work needs it.

A worked example

Take a marketing lead, call him Tom, whose quarterly campaign keeps slipping. (Illustrative throughout; this is a teaching example, not a real company.) In the retro, the design team says they were waiting on final copy; the copywriter says she was waiting on the brief to be signed off; the product manager assumed Tom owned the brief; Tom assumed the PM did. Four capable people, one campaign, and a hole in the middle where the ownership should have been. This is textbook role ambiguity, no individual failure, just unsent expectations colliding.

Tom doesn't reorganise anything. He spends twenty minutes drawing a RACI for "campaign launch." It forces the awkward questions out loud: who is Accountable for the launch date, one name, not a team? (Him.) Who is Responsible for the brief, and by when must it be signed? (The PM, by the Monday of week one.) Who must be Consulted before copy is final, and who just needs to be Informed? Writing it down surfaces the real fight in five minutes: the PM thought "sign-off" meant a quick Slack thumbs-up; Tom meant a reviewed, locked brief. That gap, invisible for three quarters, was the actual cause.

Then he adds the expectation layer the RACI doesn't carry: a one-paragraph standard of done for the launch ("live by the 30th, brief locked by week one, zero P1 issues, comms signed by Tom"). Specific, challenging, checkable, the goal-setting move. The next campaign ships on time, not because anyone worked harder, but because the work stopped falling into a gap nobody owned. The fix cost half an hour and changed no one's job title.

Frequently asked questions

Isn't this just bureaucracy, more documents, more process?

It's the opposite, when done lightly. Bureaucracy is process for its own sake; a one-line decision rule or a single RACI for a genuinely contested piece of work is a few minutes that prevents weeks of rework. The test is proportionality: map the calls that actually get stuck or duplicated, not every task. If you're drawing a RACI for "send the weekly email," you've overshot.

What's the difference between role clarity and expectation clarity?

Role clarity answers who, who decides, who delivers, who signs off. Expectation clarity answers what good looks like and by when. You can have one without the other: a person can know a task is theirs (clear role) yet have no idea what "done well" means (fuzzy expectation), or know exactly the standard but not whether it's their call to make it. Real clarity needs both, which is why a RACI plus a written standard of done beats either alone.

My team is small, do we really need this?

Small teams have fewer roles but not less ambiguity; if anything the lines blur faster because everyone touches everything. You don't need a matrix. You need one habit: at the start of any non-trivial piece of work, say out loud "you own this, here's what done looks like, and I'm the one to escalate to." Thirty seconds of naming beats a month of polite assuming.

How is this different from just micromanaging?

Micromanaging controls how the work is done; expectation clarity defines what the outcome is and then gets out of the way. Goal-setting research is explicit that specific goals work alongside autonomy on method, not instead of it. "Launch is live by the 30th with zero P1 bugs" is an expectation. "Use this exact checklist and CC me on every email" is a leash. Set the standard; leave the route to them.

What if the ambiguity comes from above me?

Then you're managing up, and the move is the same in reverse: make the implicit explicit. Reflect your own understanding back, "so I'm accountable for X by Y, and Z is yours; have I got that right?", and put it in writing. Most senior ambiguity isn't withheld on purpose; it's just an expectation the leader hasn't troubled to send. You asking is you doing their clarity work for them, which they'll usually thank you for.

Related in the Toolkit

Where to go next