How 250+ Projects Turned Role Ambiguity Into Psychosocial Risk Control

Role ambiguity rarely enters a leadership meeting with that name. It arrives as duplicated work, irritated emails, late escalation, exhausted supervisors, unresolved complaints, repeated handoff errors, or workers who keep asking whether a safety decision belongs to HR, operations, EHS, maintenance, or the contractor manager.

Across more than 250 cultural transformation projects supported by Andreza Araujo, the pattern has been consistent enough to deserve a case-study lens. Role ambiguity becomes a psychosocial risk when people carry demand without the authority, support, or decision rights needed to control it. The worker feels pressure, the supervisor absorbs conflict, and the organization calls it communication until a safety decision arrives late.

On the Headline Podcast, Andreza Araujo and Dr. Megan Tranter often press leaders to connect care, culture, and operational control. This case sits exactly there. A company can offer wellbeing resources and still leave people in a work design where nobody knows who can change the demand, pause the task, or resolve the conflict before it becomes harm.

Key takeaways

• Role ambiguity is controllable only when leaders turn vague complaints into named decisions.
• The strongest signal is repeated uncertainty at interfaces, not confusion inside one job description.
• HR, EHS, and operations must share the control because ambiguity crosses functional boundaries.
• Field evidence matters more than a revised organization chart.
• The 30-day test is whether one recurring decision now has an owner, a threshold, and proof of closure.

Initial scenario

The starting point in many projects was not a formal psychosocial risk assessment. It was a repeated complaint that sounded ordinary: nobody knows who decides, the supervisor is stuck between 2 departments, HR says it is operational, operations says it is people-related, and EHS gets involved only after the conflict affects safety performance.

That ordinary language hides a serious work-design problem. When a maintenance planner does not know whether production can override a fatigue concern, when a supervisor does not know who can reassign a distressed worker from a safety-critical task, or when HR receives workload complaints without a route to change staffing or sequencing, the role gap becomes a live exposure.

The first market trap is treating role ambiguity as a workshop topic. A team can define values, improve tone, and still leave the hard decision untouched. Andreza Araujo's book Safety Culture: From Theory to Practice gives a stricter test because culture appears in repeated decisions. If the same decision keeps returning without an owner, the culture is not unclear by accident. It is teaching ambiguity.

Decision

The decision across these projects was to stop asking whether people understood their roles in general and start asking which specific decision was failing. That shift matters because job descriptions usually look clear on paper while the real confusion appears at the edge of the role, where pressure, conflict, or safety exposure requires fast judgment.

Instead of asking a broad question such as whether supervisors had enough clarity, leaders had to name the ambiguous decision. Who decides when overtime moves from acceptable pressure to psychosocial risk? Who can change staffing after 3 repeated workload complaints? Who pauses work when conflict between 2 functions creates unsafe hurry? Who owns the follow-up after a worker reports harassment, fatigue, or role conflict that affects safety-critical work?

The companion Headline guide on the role clarity matrix for psychosocial risk explains the tool version of this logic. The case-study lesson is narrower and more demanding. A matrix only works when leaders are willing to move authority, not only words.

Execution

Execution began with a small evidence map. Each recurring complaint was translated into 4 fields: the decision that kept returning, the person who currently absorbed the pressure, the person with authority to change the condition, and the evidence that would prove the condition had changed.

This is where many organizations resist the work. They prefer a cleaner answer, such as training managers to communicate better. Training helps when the problem is skill. It fails when the supervisor already communicates well but has no authority to change staffing, production pace, contractor support, task sequence, or escalation criteria.

James Reason's work on latent failures is useful here because the visible mistake often appears far downstream from the design weakness. In role ambiguity cases, the visible mistake may be a late handoff, a missed escalation, or a hostile conflict. The latent failure is the leadership design that left 2 functions sharing concern while neither owned the decision.

Measured result

The verified scale behind this case is Andreza Araujo's experience in more than 250 cultural transformation projects across multinational environments. This article does not claim a universal percentage reduction from role clarity work because that would be false precision. The defensible result is the repeated conversion of ambiguous psychosocial risk into named ownership, decision thresholds, and field evidence.

That distinction matters for YMYL safety content. A weak case study would promise that a role clarity workshop reduces stress by a fixed number. A stronger case preserves what can be verified: across a large body of transformation work, role ambiguity became manageable only when leaders converted complaint language into operating decisions.

The practical result was visible before any annual survey could prove it. Supervisors knew when to escalate. HR knew when a complaint required work redesign instead of coaching alone. EHS knew when psychosocial pressure had become a safety exposure. Operations knew which demand, deadline, staffing gap, or handoff rule had to change.

Before and after comparison

Generalizable lessons

The first lesson is that role ambiguity is usually an interface problem. It appears between HR and operations, between line management and EHS, between client and contractor, between day shift and night shift, or between supervisor authority and senior leadership approval. Because the risk lives between functions, a single-function fix rarely holds.

The second lesson is that ambiguity grows when leaders confuse accountability with blame. Naming an owner does not mean blaming that person for every problem. It means giving the organization a place where the decision can land, because a decision that lands nowhere becomes pressure carried by the least powerful person in the chain.

The third lesson is that psychosocial risk controls need field verification. A revised RACI table is not proof. Proof appears when a supervisor can explain the new escalation threshold, a worker knows who can change the demand, HR can show which role boundary changed, and EHS can show whether safety-critical exposure was reduced.

What HR, EHS, and operations should apply in 30 days

Start with one recurring role conflict, not the whole organization. The best candidate is a complaint that has appeared at least 3 times, involves more than one function, and affects workload, conflict, delay, safety-critical judgment, or escalation. If it appears in a workload trigger matrix, a complaint log, a near-miss review, or a supervisor debrief, it is ready for a 30-day test.

In week 1, write the failed decision in plain language. In week 2, name the person who owns the decision, the person who supports it, and the threshold for escalation. In week 3, test the new rule with supervisors and workers who face the situation. In week 4, verify whether the same complaint still appears in normal work.

The HR business partner psychosocial risk guide is useful for the people-process side, while the reorganization psychosocial risk review helps when ambiguity comes from structural change. The case-study point is that both guides should end in the same place: a real decision owner and evidence that the work changed.

How leaders should avoid the next trap

The next trap is launching a role clarity campaign. Campaigns are attractive because they are visible, quick to communicate, and politically comfortable. They also let leaders avoid the harder question of whether the organization has assigned responsibility without authority, demand without support, or accountability without resources.

A better leadership review asks 5 questions. Which decision keeps returning? Who currently absorbs the pressure? Who has authority to change the condition? What threshold forces escalation? What evidence will prove the ambiguity is gone from the field? None of those questions requires clinical diagnosis, and none asks a supervisor to become a therapist. They ask leaders to design work that people can actually carry.

Andreza Araujo's broader safety-culture work keeps returning to this standard: prevention depends on the quality of decisions made before harm becomes visible. Role ambiguity is one of those decisions. If leaders leave it unresolved, the organization may call the result stress, conflict, disengagement, or poor communication, although the deeper problem is that the work has no clear owner when pressure rises.

Conclusion

Role ambiguity becomes controllable when leaders stop treating it as a vague human problem and start treating it as a psychosocial risk control with an owner, a threshold, and field evidence.

Headline Podcast exists for leadership conversations at the intersection of safety, culture, and work design. If your team is reviewing psychosocial risk this month, use one recurring role conflict as the test case and listen to Headline Podcast at headlinepodcast.us.