How to Run a Reorganization Psychosocial Risk Review in 30 Days
Use this 30-day reorganization psychosocial risk review to test demand, control, role clarity, support and change fatigue before harm appears.

Key takeaways
- 01A reorganization is not complete when the org chart is approved, because psychosocial risk appears in workload, control, support and role clarity.
- 02Start the review by defining what changed in the work, since teams experience restructuring through decisions, priorities, meetings and recovery time.
- 03Use aggregated work evidence rather than private health details, because the review should test exposure without turning people into case files.
- 04Close findings only when the affected team can describe what changed in daily work, not when leaders finish another transition document.
- 05Headline Podcast frames reorganization risk as a leadership and safety issue because work design shapes health, trust and decision quality.
A reorganization can create psychosocial risk long before anyone reports burnout, conflict, absence, or performance collapse. The risk begins when people lose role clarity, decision control, recovery time, supervisor access, team identity, or a safe path to question new demands.
This 30-day review is written for EHS, HR, operations leaders, and senior managers who need a practical method after restructuring, mergers, layoffs, site consolidation, new reporting lines, or digital operating model changes. The thesis is direct. A reorganization is not complete when the org chart is approved. It is complete only when the new work system has been tested for demand, control, support, role clarity, relationships, and change load.
ISO 45003:2021 places psychosocial hazards inside occupational health and safety management, while the HSE Management Standards point leaders toward demands, control, support, relationships, role, and change. Across 25+ years leading EHS in multinational environments, Andreza Araujo has seen that reorganizations often fail in the space between executive design and daily work. The new structure may look rational at the top, although the team may experience it as overload, ambiguity, and silence.
What you need before starting
Before starting, define the reorganization boundary. Name the teams affected, the decision that changed, the date of the change, the managers accountable, and the work processes most likely to feel the pressure. Without this boundary, the review becomes a general listening exercise, and general listening rarely changes controls.
The review also needs privacy rules. Leaders should use aggregated patterns, role-based interviews, and work-design evidence rather than private health details. The purpose is not to diagnose individuals. The purpose is to test whether the reorganized work creates preventable exposure.
Use the first day to set a narrow scope. One business unit, plant area, shared service team, or technical function is enough. A focused review that changes work within 30 days is stronger than a corporate survey that returns beautiful charts after the damage has already settled into routine.
Step 1: Define the work that changed
Start by writing one plain-language sentence describing what changed in the work, not only what changed in the structure. A weak sentence says that finance, operations, and EHS were integrated. A useful sentence says that one manager now approves maintenance priority, contractor access, and production recovery for three sites instead of one.
This step matters because psychosocial risk lives in work conditions. People feel the reorganization through new reporting lines, more approvals, missing peers, unclear escalation, extra meetings, revised targets, changed tools, and fewer chances to recover between demands.
Ask each affected manager to list the top 5 work changes created by the reorganization. Include workload, authority, decision rights, shift pattern, role clarity, communication rhythm, customer or production pressure, and emotional demand. If managers can only describe the org chart, they are not ready to assess risk.
Step 2: Map demand before measuring mood
Many reorganization reviews begin with engagement or morale. Those measures may help, but they are too broad if leaders have not mapped demand. Demand means the amount, pace, difficulty, emotional load, interruption pattern, and time pressure the new work system creates.
Collect operational evidence for the first two weeks after the change. Review overtime, meeting load, backlog, urgent requests, skipped breaks, after-hours messages, queue size, customer escalations, rework, and safety-critical decisions made late in the shift. These signals are not a diagnosis by themselves, but together they show whether the new model is asking people to absorb more work than the design admits.
Andreza Araujo's Portuguese title A Ilusao da Conformidade, often explained in English as The Illusion of Compliance, is useful here because a clean transition plan can hide a field reality where the same people carry two jobs under one title. The review should expose that gap before leaders praise the transition.
Step 3: Test whether people still have control over priorities
Control is the worker's real ability to influence how work is sequenced, paused, escalated, or adjusted. A reorganization often reduces control accidentally because approval moves upward, managers become remote, or a shared service model separates decision makers from the work they changed.
Interview a small sample across roles and shifts. Ask which priorities conflict, who can remove work, who can delay nonessential demand, who approves overtime, and what happens when two senior leaders ask for incompatible outputs. The answers will usually show whether people have control or only responsibility.
The trap is mistaking empowerment language for actual decision rights. A team can be told to own the result while having no authority to change deadline, staffing, sequence, tool access, or customer promise. That is not ownership. It is transferred pressure.
Step 4: Rebuild role clarity with decision rules
Role clarity after reorganization cannot rely on job titles. People need to know which decision they own, which decision they influence, which decision they escalate, and which decision no longer belongs to them.
Build a simple decision table for recurring conflicts. Include operational safety, workload priority, customer escalation, staffing shortage, overtime, stop-work calls, and mental-health support boundaries. For each situation, name the first decision owner, the backup owner, and the escalation point when the answer affects risk.
This is where many reorganizations create hidden strain. The company removes a layer to simplify leadership, then leaves frontline managers with more ambiguity and fewer peers. In Make The Difference: Be a Leader in Health & Safety, Andreza Araujo connects leadership with practical conditions. After a reorganization, practical leadership means making authority visible enough that people do not have to guess under pressure.
Step 5: Check supervisor span and support quality
Supervisor span changes quickly during restructuring. A manager may gain more direct reports, more sites, more shifts, or more technical diversity. The org chart may call that efficiency, but the worker may experience it as less access, slower answers, weaker coaching, and delayed escalation.
Check span with evidence. How many people does each supervisor support? How many shifts, contractors, languages, or technical areas are included? How many one-to-one conversations were missed in the first month? How long does it take to get a decision on workload, conflict, safety concern, or role confusion?
In more than 250 cultural transformation projects supported by Andreza Araujo's work, weak supervision rarely appears only as a personality issue. It often appears when the organization gives managers more people than they can support with attention, courage, and timely decisions.
Step 6: Review relationship risk without turning it into gossip
Reorganizations disturb relationships. Teams merge, peers become competitors, former managers lose authority, new leaders inherit distrust, and informal support networks may disappear overnight. These changes matter because relationships affect voice, conflict, cooperation, and willingness to raise weak signals.
Review relationship risk through work evidence, not personal rumor. Look for unresolved conflict, increased grievances, silent meetings, lower reporting quality, repeated handoff failures, and groups that now avoid each other. Ask what work interface is breaking, not who is difficult.
Amy Edmondson's research on psychological safety helps frame this step because people need enough interpersonal safety to speak honestly about risk and uncertainty. In a reorganization, that condition can fall exactly when leaders need more truth, not less.
Step 7: Separate change fatigue from resistance
Change fatigue is not the same as resistance. Resistance may reject a change because people disagree with it. Change fatigue appears when people have absorbed so much uncertainty, rework, communication noise, and priority switching that their attention and trust begin to degrade.
Look for patterns rather than labels. Are people missing details they used to catch? Are meetings producing fewer questions? Are managers repeating decisions because messages do not stick? Are safety conversations shorter because everyone is trying to survive the next deadline?
The market often minimizes this risk because tired teams may stay polite and productive for a while. That politeness can fool leadership. A team may keep delivering while its capacity for dissent, recovery, and careful judgment is already being spent.
Step 8: Convert findings into controls within 30 days
The review should end with controls, not only insights. For each finding, decide whether the exposure comes from demand, low control, weak support, role ambiguity, relationship friction, or unmanaged change. Then assign a control that changes the work.
Controls can include removing low-value meetings, freezing noncritical projects for 30 days, clarifying decision rights, reducing supervisor span, adding temporary coordination support, changing handover rhythm, protecting recovery time, or creating a safe escalation path for overload. Support resources may still matter, but they should not become the only answer when the job itself is the exposure.
Use one rule for closure. A finding closes only when the affected team can describe what changed in their work. If workers cannot feel the control, the organization may have closed the action while leaving the risk intact.
30-day review timetable
| Window | What to test | Evidence to collect |
|---|---|---|
| Days 1 to 5 | Work change and role clarity | Org change map, decision rights, affected processes, manager interviews |
| Days 6 to 12 | Demand and control | Overtime, backlog, urgent requests, skipped breaks, priority conflicts |
| Days 13 to 20 | Support and relationships | Supervisor span, response time, conflict signals, handoff failures |
| Days 21 to 25 | Change fatigue and weak signals | Meeting silence, reporting quality, rework, missed details, safety concerns |
| Days 26 to 30 | Controls and governance | Work changes assigned, owners named, review rhythm set, field feedback returned |
Each month after a reorganization without psychosocial risk review allows overload, ambiguity, and silence to become the new normal while the dashboard may still show stable performance.
Conclusion
A reorganization psychosocial risk review protects people by testing how the new work system changes demand, control, support, role clarity, relationships, and change load. The review is not a morale exercise. It is a control process for work conditions that can damage health, attention, trust, and safety decisions.
Headline Podcast exists for real conversations where leadership and safety come together to shape better workplaces and better lives. If your organization has just changed its structure, use the next 30 days to prove that the new design can protect people as well as performance.
Frequently asked questions
What is a reorganization psychosocial risk review?
When should leaders run this review?
Is this review an HR process or an EHS process?
What evidence should be reviewed without violating privacy?
What controls can reduce psychosocial risk after reorganization?
About the author
Andreza Araújo
Safety Culture Expert | Senior EHS Executive
Andreza Araújo is a safety culture expert and senior EHS executive with more than 25 years of experience in environment, health and safety. She is a Civil Engineer and Occupational Safety Engineer from Unicamp, holds a Master's degree in Environmental Diplomacy from the University of Geneva, and completed sustainability studies at IMD Switzerland. Andreza has served in Global Head of EHS roles in Fortune 500 environments, leading cultural transformation programs across multinational operations. She has represented Brazil as a speaker at the United Nations in Paris and has spoken at the International Labour Organization in Turin. She is the author of more than 16 books on safety culture in Portuguese, Spanish, English and German. Her work has earned more than 10 EHS awards, including two recognitions from Indra Nooyi, former PepsiCo CEO.
- Civil & Safety Engineer (Unicamp)
- M.A. Environmental Diplomacy (University of Geneva)
- Sustainability Cert (IMD Switzerland)
- People Management & Coaching (Ohio University)
- UN Paris speaker representative for Brazil
- ILO Turin speaker
- LinkedIn Top Voice
- Indra Nooyi PepsiCo CEO recognition (2x)
Documentaries
Watch Andreza's documentaries
Three productions on safety culture, organizational failure and the human lessons behind major disasters.
Podcasts
Listen to Andreza's podcasts
She hosts three shows on safety leadership, EHS and organizational culture, in English and Portuguese.