Managing psychosocial risk during organisational change

Change is one of the most consistently identified sources of psychosocial hazard in Australian workplaces, but the controls that work in steady-state operations are not necessarily the ones that work during change. This article focuses specifically on managing psychosocial risk while an organisational change program is in flight. The broader review of what employers should have in place outside change is covered in psychosocial risk management: what employers should be reviewing now, and the operational communication discipline that supports any change is covered in employee communication during restructures and workplace change.

The mechanisms by which change generates psychosocial hazard are well understood: uncertainty about role and security, increased workload, disrupted social structures, reduced sense of control, and the cumulative weight of repeated change. A change program that ignores these factors creates risk regardless of how strong its operational case is. Treating change as a psychosocial hazard does not slow it down — it means designing the program with the human dynamics in view from the start.

Consultation is one of the most effective psychosocial controls during change, but only when it is genuine. Consultation that begins after the operational decision is settled is treated as performative; consultation that begins so early there is nothing concrete to discuss frustrates participants. The workable middle is consultation that begins when the proposal is sufficiently developed to be discussed meaningfully but before it is sufficiently developed to be unchangeable.

Consultation records should show what was put, who was consulted, what feedback was received and how it was considered. Where feedback did not change the outcome, the reasoning for that should be recorded as well; silent dismissal of feedback is one of the most reliable ways to damage trust in current and future change programs.

Role ambiguity is a common change-related hazard. Where reporting lines shift, where new roles are created or where responsibilities are redistributed, employees should be able to describe — at any point in the process — what is being asked of them. Where that clarity is not yet available, it should be acknowledged rather than papered over.

Where new roles are still being designed, an interim role description with stated limits is more useful than a final-looking description that will change again. Honesty about what is and is not yet decided is itself a control.

Communication cadence matters as much as content. Long silences invite speculation; ad-hoc updates undermine confidence. A planned cadence — what will be shared, when, through which channel and by whom — gives employees a basis on which to manage their own expectations. The cadence should hold even when there is nothing new to report; a regular update that confirms the position has not changed is more reassuring than no update at all.

Transparency about what is not yet decided is as important as transparency about what is. Trying to hold the position that everything is fine until the announcement is ready almost always backfires; people know change is coming and the silence increases rather than reduces uncertainty.

Change programs almost always create workload pressure on the people delivering the change and on the teams absorbing it. Monitoring workload and resourcing through the program — not just at the start — is part of the control environment. Where workload has crept beyond what is sustainable, the response should be to adjust the program rather than to ask people to absorb the gap.

Change fatigue from prior programs should be considered explicitly. Where the workforce has recently absorbed a series of changes, planning should account for the reduced capacity to absorb another one. Pretending that prior change has been digested when it has not is one of the most consistent contributors to elevated psychosocial risk during the next program.

How leaders behave during change has an outsized effect on how employees experience it. Visible engagement, consistency of message across audiences, acknowledgement of difficulty and willingness to engage with hard questions all act as controls. Leaders who delegate communication entirely, or who switch messaging between forums, materially elevate the psychosocial risk profile of the program.

Manager support is part of the same control. Most line managers will be navigating the change themselves while also being asked to support their teams through it. Scripts, FAQs, escalation pathways and access to workplace advisory input when conversations become difficult all increase the chance that managers handle the conversations in a way that supports rather than damages the program. Capability development covered under psychosocial safety is often a sensible parallel investment.

Monitoring during change should include sentiment and feedback as well as operational metrics. Pulse surveys, manager check-in summaries, EAP utilisation trends and incident data each add a different lens. Where the data shows elevated risk in a particular area, the program should be capable of responding rather than continuing on its original timetable.

Risk assessments, consultation records, communication plans, manager support materials, training delivery and post-change reviews should be retained as a coherent set. This evidence supports both regulatory expectations and the organisation's own learning for the next change cycle — most programs reuse a remarkable amount of material from the previous one, and the better the record, the better the next cycle.

AWS supports employers through change-related psychosocial risk assessment, communication planning, consultation design, manager capability work and post-change review. The work integrates with existing project, HR and WHS systems rather than running alongside them.