Unclear Roles and Burnout

By BurnoutInfo · Updated October 17, 2026 · 8 min read

Source-linked education. Read our editorial process and review limits.

Look for conflicting instructions

Common examples include two managers assigning incompatible priorities, a project with no decision owner or an employee covering a vacant role without agreed limits. These are work-design problems even when everyone is trying to help.

Ask each person involved to describe the expected output, deadline and owner. Differences in those answers reveal where clarification is needed.

Write a short working agreement

• Purpose: what result is this role or task meant to achieve?
• Ownership: who decides, who contributes and who needs to be informed?
• Priority: which existing work moves when something urgent arrives?
• Standard: what counts as complete, and who approves it?

Use a real recurring task as the example. A one-page agreement that people use is more helpful than a long role document that leaves everyday conflicts unresolved.

Revisit the agreement after change

Reorganizations, new software and staff departures can invalidate earlier assumptions. Set a review date rather than expecting workers to absorb the uncertainty indefinitely. See decision fatigue for approval bottlenecks and workload when clarification reveals that the role is simply too large for its available capacity.

Uncertainty can become an extra job

When a role is unclear, the worker must do more than complete the assigned task. They also have to infer what matters, predict whose instructions will prevail and negotiate the boundaries of responsibility. That effort is rarely visible in workload reports. A task that appears simple may require several conversations just to discover who can approve it. If the answer changes afterward, the person may repeat the work without knowing how to avoid the same problem next time.

The HSE role standard concerns understanding responsibilities and avoiding conflicting roles. It is a useful starting point for examining these conditions. The practical goal is not a document that anticipates every possible event. It is enough clarity for people to act, plus a dependable way to resolve questions when circumstances do not fit the usual pattern.

Distinguish ambiguity, conflict and excessive scope

Ambiguity means an important expectation is uncertain: nobody knows who approves the final version. Conflict means expectations are incompatible: one manager requires speed while another rejects any reduction in detail. Excessive scope means the expectations may be clear but cannot fit available capacity. These problems can coexist. Naming the type of difficulty helps prevent the wrong solution, such as providing a clearer job description when the real issue is two full workloads assigned to one person.

Choose a recent example and ask what prevented progress. Was the output unclear? Were two instructions inconsistent? Was authority missing? Or was there simply too much to do? Our workload guide addresses capacity, while low control considers usable decision authority. A role-clarity discussion should be willing to discover that the problem lies partly elsewhere.

Map one recurring piece of work from request to completion

Pick something that repeatedly causes rework, such as a client proposal, incident report or monthly forecast. Identify who requests it, who supplies information, who creates the output, who checks it and who decides it is complete. Ask each person separately if necessary. Differences often reveal assumptions that have never been discussed. A task may have several contributors but still need one clearly identified owner for the final decision.

Then examine handovers. What information must accompany the task? How does the receiving person know it is ready? What happens if essential information is missing? Unclear handovers can cause a task to move repeatedly between teams while everyone believes it belongs elsewhere. Agree the minimum information and an escalation route. Avoid solving the problem by requiring excessive documentation that takes longer than the original task.

Define “done” before the work begins

A deliverable needs a purpose and an acceptable standard. Ask who will use it, what decision it supports and how much detail is necessary. Without that agreement, workers may keep refining a product because they cannot tell when further effort stops adding value. Others may complete a reasonable version only to discover an unstated requirement. Both patterns can create avoidable frustration and make performance feedback feel arbitrary.

For an illustrative internal briefing, the agreement might specify the audience, the questions to answer, an approximate length and who approves publication. It might also state what is outside scope. These are working boundaries, not an excuse to ignore important new information. If requirements change, acknowledge the change and its effect on time. Do not retrospectively treat a newly introduced expectation as something the employee should always have known.

Resolve competing managers before assigning the worker the conflict

In matrix structures, project leaders and line managers may each control part of the work. The employee needs to know who resolves priority collisions. A request to “manage stakeholders” can otherwise become an instruction to persuade more powerful people to accept a trade-off nobody wants to own. Establish an escalation point and a response expectation. The worker should be able to present the conflict without having to decide privately whose instruction to disregard.

A practical statement is: “The client revision and internal audit are both due tomorrow, and the available time covers one. Please agree which takes priority and who will notify the other sponsor.” This describes the decision required. Once resolved, communicate it to everyone affected. The leadership-accountability guide helps assign responsibility for those choices so that clarity does not depend on the least powerful person negotiating repeatedly.

Put boundaries around temporary cover

Covering a vacancy, absence or project can quietly turn into a permanent expansion of duties. Write down what has been added, what has been removed and when the arrangement will be reviewed. Include authority and access: the covering person may be expected to perform duties without the permissions or information the original post holder had. That mismatch should be resolved explicitly rather than being treated as a test of initiative.

Specify what happens if recruitment takes longer than expected. A review date is useful only if someone will reconsider the demands, not merely renew the same arrangement. Ask whether urgent cover has created dependencies on one individual that now need addressing. Training a replacement, documenting essential processes and transferring relationships all take time. Include that work in the plan rather than assuming it can be completed alongside the expanded role without consequence.

Revisit responsibilities when systems or structures change

A new tool can alter who enters data, checks quality or handles exceptions. A reorganisation can leave old reporting lines active even after new ones are announced. The HSE change standard emphasizes communication and consultation around organizational change. For role clarity, a practical question is which decisions or handovers will work differently on the first day of the new arrangement.

Walk through a real scenario with those affected. If a customer reports a problem, who receives it, who acts and who tells the customer what happened? Identify gaps before declaring the transition complete. Keep a short record of unresolved questions, their owners and intended resolution dates. Workers should not have to maintain competing old and new processes indefinitely because leaders have not agreed which system now governs the work.

Make clarification safe and normal

People may avoid asking questions when uncertainty is treated as incompetence. Managers can make clarification ordinary by checking shared understanding and acknowledging where their own instructions were incomplete. Ask an employee to explain the intended output in their own words, then resolve differences collaboratively. This is different from testing whether they can repeat a vague instruction. The purpose is a common understanding that supports action.

New starters, temporary workers and people returning after absence may need particular attention because informal rules are harder to see from outside. Experienced staff may also carry assumptions that no longer fit. The psychological-safety guide discusses the conditions for raising these questions. An open-door statement is insufficient if the response to a genuine ambiguity is consistently irritation or blame.

Keep the agreement short and connected to daily decisions

A useful role note can identify the main outcomes, decision rights, priority route, key interfaces and review date. Use the language people actually use for the work. Store it where those affected can find it, and make changes visible. A lengthy policy that nobody consults may leave the same uncertainty intact. The test is whether someone encountering a familiar problem can use the agreement to know what happens next.

At review, ask whether rework, waiting or duplicated effort has changed. Check for work that still has no owner and tasks with too many competing owners. Invite examples of where the agreement did not fit reality. The decision-fatigue article can help identify recurring choices that should be resolved once at the appropriate level rather than recreated by every worker.

Frequently asked questions

Does clarity make a role rigid?

It need not. An agreement can explain how priorities change and who authorizes a departure from the usual approach. Clear boundaries can make flexibility easier because people know which choices they can make and when they need help.

What if my manager says the role requires initiative?

Ask which decisions you are authorized to make and what outcomes matter most. Initiative works better when there is usable authority and access to support. It should not mean guessing unstated requirements while remaining accountable for every interpretation.

Can I start the clarification myself?

Yes. Draft a short account of your current understanding and ask the relevant people to correct it. Frame it around a recurring task or conflict rather than attempting to redesign the entire organization. Responsibility for resolving structural contradictions still belongs with those who have authority to change them.

What if clearer expectations reveal that the role is impossible?

That is useful information. Return to capacity, priorities and resources. A well-written description cannot make incompatible obligations achievable, so the next step is a decision about what changes.

Related guides

• Low Control and Burnout
• Manager Guide to Burnout Prevention