A useful organizational-clarity question sits underneath many pilot, partnership, and delivery discussions: when work slows down, repeats, or stalls, is the core issue the workflow, or is it unclear ownership across roles, decisions, and handoffs? That question is practical because it moves attention away from broad complaints and toward operating reality.
Several field briefs point in the same direction. Buyers ask how to compare leadership expectations with frontline experience, how to map responsibilities across subteams, how to identify where senior people are doing junior work, and how to show clients which findings are reliable enough to guide a decision. Those are important observations, but they are still observations from business-development and delivery conversations, not representative evidence. To make the question stronger, it helps to anchor it in external research.
Research on team diagnostics has found that clear roles are not a side issue. In one applied team framework, example items used to assess team effectiveness included whether roles, responsibilities, reporting structure, and decision-making authority were clearly defined, and whether communication was clear, accurate, timely, and unique (https://www.frontiersin.org/journals/communication/articles/10.3389/fcomm.2021.606445/full). The same study used a mixed-method sequence: aggregated diagnostic results first, then interviews and debriefs to interpret the weak spots in context (https://www.frontiersin.org/journals/communication/articles/10.3389/fcomm.2021.606445/full). That matters for organizational work because a good interview program should not stop at collecting stories. It should help separate signal from noise by connecting perceptions to specific roles, decisions, and moments of transfer.
The research also points to a common failure mode: teams often experience poor process fairness not only because they dislike an outcome, but because they do not understand how a decision is being made or what influence they actually have. In the same Frontiers article, the authors argue that clarity about decision roles, the status of the decision process, and what is and is not included in the decision affects perceptions of justice and teamwork. They describe a simple meeting-level prompt: is this conversation for an update, for input, or for a decision (https://www.frontiersin.org/journals/communication/articles/10.3389/fcomm.2021.606445/full). That is a modest intervention, but it reveals an important truth. Many recurring coordination problems are not caused by bad intent or weak talent. They come from unresolved ambiguity about authority and expected contribution.
A second pattern in the literature is the difference between leadership and frontline experience during change. A qualitative study of care-team dynamics found that disconnects between frontline providers and management damaged trust and team functioning, while active senior leadership that kept people informed and connected improved communication across groups (https://pmc.ncbi.nlm.nih.gov/articles/PMC9719119/). Another qualitative health-services study found that managers and frontline staff were both under pressure, but in different ways: managers emphasized restructuring and accountability, while frontline staff focused on keeping work moving and serving users despite constant change (https://www.pure.ed.ac.uk/ws/portalfiles/portal/30876559/HSRPEGIFinaledit.pdf). OWI would interpret this carefully: when leaders describe a new model as rational and coherent while teams describe it as confusing and overloaded, the gap may be less about resistance than about different vantage points on the same operating system.
That interpretation is also consistent with broader change research. Studies using the job demands-resources lens suggest that employee responses to change are shaped not only by the formal design of the initiative, but by whether people have the resources, support, control, and clarity needed to handle it (https://cris.maastrichtuniversity.nl/en/publications/explaining-employees-evaluations-of-organizational-change-with-th/; https://pmc.ncbi.nlm.nih.gov/articles/PMC3924440/; https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2020.531944/pdf). The implication is practical: before declaring that a team is resistant, an organization should ask whether people know what they own, what they can decide, where they must escalate, and what a good handoff looks like.
A practical diagnostic method
A lightweight but disciplined review can start with five questions:
- What is the unit of work? Name one recurring process, not an abstract problem. For example, onboarding a client, staffing a project, approving an exception, or updating role data.
- Who touches it? List the actual roles involved, not just departments. Include who starts the work, who modifies it, who approves it, and who inherits the consequences.
- What kind of involvement does each role have? Distinguish between doing, advising, approving, informing, and deciding. If two roles both believe they decide, or neither does, that is already a finding.
- Where are the handoffs? Mark each transfer of information, accountability, or waiting time. Handoffs are often where context is lost, duplicate checking appears, or senior staff step in to rescue the flow.
- Where do leadership and frontline accounts diverge? Compare the official version of the process with how the work is described by the people closest to it.
From there, score each step on three dimensions:
- Role clarity: is ownership explicit?
- Decision clarity: is it clear who decides, who gives input, and when?
- Handoff clarity: is it clear what must be transferred, in what form, to whom, and with what standard?
This is intentionally simple. Its value is not elegance. Its value is that it produces comparable evidence across interviews and turns vague complaints into inspectable operating questions.
What this question helps reveal
In practice, this diagnostic question often uncovers one of four conditions.
First, process problems that are really authority problems. Meetings repeat because participants are asked for input after a decision is already fixed, or because nobody knows the decision boundary.
Second, role problems that are really handoff problems. People say responsibilities are unclear, but the deeper issue is that outputs from one role are incomplete or unusable for the next.
Third, capability concerns that are really design concerns. Senior people appear to be doing junior work because controls, documentation, or transfer standards are weak.
Fourth, adoption problems that are really trust problems. Teams resist a tool or new workflow because they cannot see how decisions will be made, how their input will be used, or what remains negotiable.
None of this means every organization needs a large transformation program. Often the first useful move is smaller: clarify decision types, define ownership at each handoff, and compare leadership assumptions with frontline experience before changing tooling or structure.
That is where OWI can be useful. Not by claiming that interviews alone can predict outcomes, but by helping organizations examine how people, process, and systems meet in the actual flow of work. If this question feels familiar in your own context, it may be worth exploring one workflow, one team, or one pilot first.