Being asked to take ownership of a client rollout can sound like a clear assignment. A manager and employee discuss the deadline, agree on the main tasks, and leave the meeting satisfied that the work is in good hands. Two weeks later, a decision is still waiting for approval. The employee thought it was too significant to make alone. The manager thought making it was precisely what taking ownership meant.
It would be easy to describe this as a lack of initiative. From the employee's perspective, though, waiting was a reasonable response to an unclear boundary. Both people believed they understood the assignment, but they were working from different expectations about the authority that came with it. The disagreement became visible only when the work required them to act on those expectations.
How Role Ambiguity Develops
Role ambiguity is uncertainty about what a person is expected to achieve, which responsibilities belong to them, or how much authority they have to make decisions. It can exist even when the tasks themselves seem straightforward. Someone may know exactly what needs doing while remaining unsure whose approval is required or which deadline takes priority.
It also concerns how the work will be judged. An employee may understand the assignment without knowing what counts as a good result, which information or support they can rely on, or where their responsibility ends and a colleague's begins. Ambiguity is experienced by the person doing the work; a manager's confidence that the role has been explained does not establish that the employee has enough information to carry it out.
Job descriptions provide a starting point, but much of the role gets defined through everyday interactions. Employees learn when to escalate, which stakeholders expect consultation, and how much independence a manager actually welcomes. A change of manager or a move to another project can disrupt those informal agreements without anyone recognising that they need to be explained again. The written role stays the same while the practical rules change around it.
Weak onboarding can leave those gaps in place from the beginning. Elsewhere, they develop as an organisation grows, reporting lines overlap, or a restructure redistributes work without settling who now owns it. Vague instructions and inconsistent feedback make the uncertainty harder to resolve, particularly when different managers each assume their expectations take precedence.
Ambiguity, Conflict, and Overload
Role ambiguity concerns missing or unclear expectations. Role conflict occurs when the expectations are understood but incompatible. An employee who does not know whether speed or thoroughness matters most faces ambiguity. An employee explicitly required to complete every check and meet a deadline that leaves no time for those checks faces conflicting demands. Explaining both demands again will not resolve the trade-off.
Role overload is a further possibility: the responsibilities may be clear and compatible, but there is more work than the available time or resources allow. These problems can occur together, which makes it important to establish what needs correcting. Clarification helps with ambiguity, a decision about priorities can resolve conflict, and excessive workload requires a change to scope, capacity, or timing. Role clarity gives people a shared understanding of their responsibilities; it does not, by itself, make every demand achievable.
Why More Communication Can Leave Expectations Unclear
Teams can spend considerable time discussing work without checking whether they understand it in the same way. A detailed briefing may explain the background of a project while leaving the most consequential question unanswered: who can decide what happens when the plan needs to change?
Phrases such as taking ownership or keeping people informed are particularly open to interpretation. One manager expects an update after a decision; another expects consultation beforehand. An employee can follow either convention conscientiously and still disappoint someone who assumed the other was obvious.
Asking whether everything makes sense rarely exposes this difference. Comparing specific interpretations is more useful. Discussing which decisions the employee will make independently, and what would prompt them to come back for approval, turns a general expectation into something both people can examine.
For the client rollout, that could mean agreeing that the employee can change the sequence of tasks but must discuss changes to the launch date. Working through one likely decision often reveals more than repeating a broad instruction to be proactive. It also gives the employee something concrete to refer back to when the work gets complicated.
The Personal Cost of Guessing
Repeated uncertainty can become a source of stress. The UK's Health and Safety Executive includes understanding responsibilities and avoiding conflicting roles in its Management Standards for work-related stress. That places role clarity among the conditions an organisation should address, rather than leaving each employee to cope with confusion alone.
Unclear expectations can make feedback difficult to use. An employee might deliver careful work and discover that speed mattered more, or act quickly and learn that a stakeholder expected to be consulted. If the standard only becomes visible afterwards, it is difficult to know what to repeat and what to change.
One response is to seek approval for increasingly small decisions. Another is to avoid taking on work that crosses uncertain boundaries. These behaviours can look like a loss of confidence or motivation, even when they are attempts to avoid another unexpected correction.
Over time, the experience can become frustrating and draining. Someone may feel less satisfied with a job when good work repeatedly attracts criticism based on an unstated expectation. Persistent ambiguity can contribute to exhaustion and disengagement, especially alongside excessive demands or weak support, although those outcomes can have several causes. It also gives colleagues more opportunities to disappoint one another without understanding why.
The cost extends beyond the individual. Managers spend more time approving routine work, colleagues duplicate effort, and decisions wait while people establish who is entitled to make them. An organisation can gradually become slower without any single task becoming more difficult.
When Overlapping Roles Become Conflict
A product launch might involve product, sales, marketing, and customer support, with each team responsible for a different part of the outcome. Sales presses for delivery because a customer commitment has been made, while product presses for more time because a defect remains unresolved. Both have reasons for their position. Their shared responsibility for a successful launch does not establish who can decide which concern takes priority.
Another meeting may settle the immediate disagreement, but the same tension can return at the next decision. The more lasting question is whether the organisation has made responsibility and authority clear enough for the teams to resolve competing demands without renegotiating their roles each time.
Making Clarity Part of the Work
Useful role clarity gives people enough structure to make decisions while leaving room for judgement. It does not require instructions for every possible situation. A short, shared agreement can establish the boundaries that matter most:
- The outcome being sought and the priorities that guide trade-offs
- What good performance looks like and how it will be reviewed
- Who owns the decision, who contributes, and whose approval is required
- When a problem should be escalated and who resolves conflicting demands
These agreements need to reflect how work actually happens. Giving someone responsibility for delivery while withholding the authority to resolve routine obstacles leaves the central ambiguity in place. Likewise, naming an owner achieves little if several senior stakeholders can override that person's priorities independently.
The agreement should be somewhere the people doing the work can find it. A few lines in the project brief may be enough, provided they record the decisions that were actually made. If a disagreement returns, the team can check whether the agreement was unclear, whether circumstances changed, or whether someone acted outside it.
Clarity also needs maintenance. When scope, staffing, or deadlines change, the people involved should revisit what they expect from one another. A brief comparison of assumptions at that point can prevent a much longer disagreement after the work is complete.
Regular feedback gives employees a way to check their interpretation before the final result is judged. Managers can use onboarding, one-to-ones, and project reviews to work through real decisions, explain reporting relationships, and make room for questions about conflicting instructions. The response to those questions matters: treating a request for clarification as evidence of incompetence makes it harder to discover the next gap.
Treating Repeated Confusion as Organisational Feedback
An isolated misunderstanding may be resolved through a better explanation. Repeated confusion across several people deserves a wider look at how work is organised. Overlapping ownership, competing instructions, or inconsistent expectations about approval can create problems that no amount of individual attentiveness will fully resolve.
People do not need to know every future decision in advance, but they do need a reliable way to establish what matters and who can decide when circumstances change. Before asking employees to show more initiative, check whether they have the authority and shared expectations needed to exercise it. Those are also the expectations against which their decisions should eventually be judged.