How to Build a Role Conflict Map in 21 Days

Role conflict is not a personality issue. It is a work-design fault that appears when a person receives incompatible expectations without the authority, time, or support to resolve them. In psychosocial risk management, that fault matters because the worker becomes the buffer between priorities that leaders have not reconciled.

ISO 45003:2021 names role ambiguity and conflicting demands as psychosocial hazards linked to how work is organized. The HSE Management Standards also treat role clarity as one of the core conditions in work-related stress prevention. For EHS and HR, the practical question is no longer whether role conflict belongs in the risk system. The question is how to find it before it turns into burnout, silence, shortcuts, or unsafe improvisation.

Across 25+ years in executive EHS roles and more than 250 cultural transformation projects, Andreza Araujo has seen the same pattern repeat: organizations ask workers to own safety while rewarding them for absorbing contradictions. A role conflict map makes those contradictions visible enough for leaders to change the work.

What you need before starting

Begin with one function, shift, or department where tension is already visible. Good starting points include maintenance planning, production supervision, customer operations, project execution, logistics, and any team affected by recent reorganization. Do not begin with the whole company, because a map that is too wide becomes too vague for action.

You need a sponsor from operations, one EHS or HR facilitator, access to job descriptions, current procedures, escalation rules, recent incident or complaint themes, and 45 to 60 minutes with a small sample of workers and supervisors. If your organization already has a psychosocial risk register, use the register to select the area with the strongest signal.

Step 1: Define the work boundary

Choose the role or work group that will be mapped and write the boundary in plain language. For example, do not map “operations.” Map “night-shift packaging supervisors during weekend staffing gaps” or “maintenance planners who approve urgent work orders.” The narrower boundary keeps the discussion attached to decisions people actually face.

Record the main output of the role, the decisions the role is expected to make, and the risk exposures attached to those decisions. This first step prevents a common failure in which the map becomes a generic organization chart rather than a view of how pressure reaches the person doing the work.

Step 2: List formal duties and informal demands

Place formal duties in one column and informal demands in another. Formal duties come from job descriptions, procedures, permit systems, performance goals, and management routines. Informal demands come from urgent calls, production requests, peer expectations, client pressure, and inherited customs that are rarely written down.

The conflict usually hides between those two columns. A supervisor may be formally responsible for stopping unsafe work while informally expected to keep the line running. A planner may be formally responsible for job quality while informally judged by speed. This is where role conflict connects with workload risk planning, because competing demands often increase both volume and emotional load.

Step 3: Map decision authority

For each recurring demand, ask who can decide, who can advise, who must be consulted, and who only receives the consequence. Use names or role titles rather than departments. “Operations” does not decide anything. A plant manager, shift coordinator, maintenance manager, or HR business partner decides.

This step exposes the most dangerous gap: accountability without authority. When a worker is accountable for a result but cannot change the staffing, sequence, deadline, budget, access, or approval rule that shapes the result, the organization has created an unresolved psychosocial exposure. The employee may still perform well for a while, although performance is being purchased through strain.

Step 4: Identify collision points

Mark every place where two expectations cannot be met at the same time. Typical collision points include speed versus verification, customer response versus recovery time, attendance versus health restriction, production target versus stop-work expectation, and supervisor support versus disciplinary pressure.

Write each collision as a concrete sentence: “The supervisor is expected to release the batch by 6 p.m. and also repeat the pre-start check when a contractor arrives late.” This format matters because vague labels create vague actions. Concrete collision sentences show leaders exactly which work rule needs redesign.

Step 5: Test the map with workers

Take the first version to people who do the work and ask what is missing. The best question is not “Do you agree with this map?” Ask, “Where do you have to choose which instruction to ignore?” That question usually reveals the contradictions that formal interviews miss.

Protect the discussion from blame. James Reason's work on latent conditions is useful here because role conflict often sits upstream of visible error. Workers may be making the least bad choice inside a system whose priorities have not been reconciled. If the room turns the conversation into attitude, commitment, or resilience, bring it back to demands, authority, support, and escalation.

Step 6: Connect conflicts to risk signals

Role conflict becomes a management priority when it is connected to evidence. Link each collision point to near misses, quality deviations, overtime spikes, absenteeism, complaints, turnover, incident themes, delayed corrective actions, or repeated supervisor escalations. When data is weak, use employee testimony carefully and label it as qualitative evidence.

This is also where EHS and HR should compare the map with job demands that keep psychosocial risk invisible. A demand may look reasonable in isolation, but the map shows whether that demand is arriving alongside unclear authority, poor support, or incompatible performance pressure.

Step 7: Convert findings into work-design actions

Each finding needs a work-design action, an owner, and a verification method. Weak actions sound like “communicate better” or “train supervisors.” Strong actions change the conditions: remove duplicate approvals, clarify who can stop the work, change staffing assumptions, adjust planning windows, rewrite escalation rules, or split a role that has absorbed too many incompatible duties.

Andreza Araujo's book Safety Culture: From Theory to Practice is relevant because it treats culture as repeated management behavior, not declared values. Role conflict follows the same rule because leaders teach employees whether contradiction is a management problem or a private burden. If leaders keep repeating the same contradictory requests after the map is complete, the culture is teaching employees that conflict is theirs to carry.

Step 8: Verify that conflict has reduced

After 21 days, verify the changes with two forms of evidence. First, check whether the work-design action happened as intended. Second, ask the affected workers whether they still face the same collision point. A closed action does not prove reduced exposure if employees are still deciding which priority to sacrifice.

Use a small set of verification questions: Which decision is clearer now? Which escalation is faster now? Which demand was removed or sequenced differently? Where does conflict still remain? If the answer is mostly silence, the team may not trust the process yet, especially where previous surveys produced no change.

Step 9: Link the map to escalation and stop-work rules

Role conflict often becomes acute when a worker sees a risk but lacks confidence that the organization will support the slower or safer decision. That is why the map should connect to escalation rules and, where relevant, a stop-work authority protocol. Authority must be more than a slogan when production pressure rises.

Define which conflicts require immediate escalation, which ones can wait for weekly review, and which ones belong in management review. A repeated role conflict is not a minor frustration. It is evidence that the organization is asking people to solve a design problem with personal endurance.

Step 10: Add the map to the management review rhythm

A role conflict map should not live as a one-time workshop output. Add open conflicts, actions, overdue decisions, and worker verification results to the monthly EHS and HR review. For high-pressure functions, review the map after reorganizations, staffing changes, new technology, contract changes, and serious incidents.

The review should ask whether leaders removed conflict from the work or simply documented it, because documentation only proves that the organization noticed the hazard, while redesign proves that it accepted ownership.

The hidden cost of role conflict is not only stress, but decision corrosion that teaches employees to make private trade-offs the safety system never sees when every priority is mandatory and no authority is clear.

Final checklist

• The mapped role or group is narrow enough for concrete action.
• Formal duties and informal demands are listed separately.
• Decision authority is named by role, not by department.
• Collision points are written as concrete incompatible expectations.
• Workers have tested the map and added missing conflicts.
• Each finding has a work-design action, owner, and verification method.
• The map is linked to escalation, stop-work, and management review routines.