New Psychosocial Risk Lead in 90 Days: What to Establish Before the First Survey

A new psychosocial risk lead is often asked to “run a survey” before anyone has agreed on the decision the survey should support. That sequence creates a familiar failure. Employees provide difficult information, leaders receive a dashboard, and nobody owns the change in workload, staffing, autonomy, conflict, or working time that the dashboard reveals.

The first 90 days should establish a management system before it produces a measurement. The lead needs to understand how work is designed, which groups are exposed to change, who can alter the conditions, and how employees can speak without being made responsible for fixing the system themselves. A survey then becomes one source of evidence rather than a substitute for leadership.

Andreza Araujo’s published professional profile records more than 25 years in multinational EHS leadership and work across 250+ cultural transformation projects. That experience supports a useful test for this role, which is whether the organization changes a decision after hearing the evidence.

What does a new psychosocial risk lead need to understand before starting?

Psychosocial risk sits in the relationship between people and the conditions of work. Workload, low control, unclear priorities, poor support, conflict, violence, harassment, isolation, and constant change can combine in ways that are not visible in a single incident report. The lead therefore needs to study work design, not only individual wellbeing.

ISO 45003:2021 provides a management-system lens for psychological health and safety, while the International Labour Organization’s guidance on psychosocial risks emphasizes organizational conditions and prevention. These references help define the scope, but they do not tell a company which manager must change a roster, remove a conflicting target, or redesign an escalation path.

Start by separating three responsibilities. The lead coordinates evidence and governance. Operational managers own the conditions they can change. Specialist services support people who need confidential help. When those roles are mixed together, employees may avoid speaking because they cannot tell whether their comment will trigger care, performance action, or a workforce-level investigation.

Andreza Araujo’s Safety Culture: From Theory to Practice is useful at this point because it treats culture as something revealed by repeated decisions. A completed questionnaire does not prove psychological health. The response to the information does.

First week: define the promise, scope, and decision rights

Use the first week to write a one-page operating brief. State which work groups are included, which risks are in scope, what the organization will do with the evidence, and what the process will not do. If the project includes workload and work design but excludes bullying, violence, or harassment, say so clearly and define the route for those concerns.

Then interview the people who can change the work. Speak with operations, HR, EHS, occupational health, employee representatives, and at least two frontline managers from different shifts or locations. Ask where priorities collide, where work is routinely extended, and which concerns are raised informally because the formal route feels slow or unsafe.

Write the decision rights beside each issue. A site manager may change staffing or sequencing. A regional leader may change a target or service-level agreement. HR may own a conduct investigation. The psychosocial risk lead may escalate a pattern, but should not become the permanent owner of every action.

Use the first week to explain confidentiality in plain language. Employees need to know which data will be aggregated, when a comment may require an immediate safeguarding response, and how support differs from organizational diagnosis. A vague promise of anonymity creates more distrust than a precise boundary.

Days 8 to 30: build a work-design evidence map

During the next three weeks, map the conditions that shape daily work. Review workload peaks, overtime, staffing gaps, roster changes, handoffs, conflicting measures, decision latitude, supervisor availability, and the time required to recover from a deviation. Compare the official process with the work people actually perform when demand rises.

Do not treat absence or turnover as a diagnosis. They can signal strain, but they can also reflect labor-market conditions, seasonal work, local transport, or a recent restructuring. Use them as prompts for questions, then test the interpretation through field conversations and work observation.

Link each exposure to an accountable owner and a verification method. For example, a recurring late shift may belong to operations, with roster data and worker interviews used to check whether the change reduced fatigue pressure. A conflict between output and safe staffing may belong to the plant manager, with weekly review of staffing decisions and stop-work escalations.

Two existing resources can sharpen this map. Role conflict explained helps separate competing demands from personal resilience, while the workload-handoffs review shows how pressure can transfer between teams without appearing in one department’s numbers.

Month 2: test one or two changes before the survey

A new lead should resist the urge to wait for a complete baseline. Choose one or two exposures that are visible, consequential, and within management control. The first test might clarify who can change a roster at short notice. Another might remove a duplicate approval that keeps supervisors available late into the shift.

Define the change in operational terms. Name the owner, the start date, the affected group, the expected benefit, and the evidence that will show whether the change worked. If the action is “improve communication,” it is not ready. If the action is “the shift manager reviews workload handoffs at the 15-minute daily meeting and escalates unresolved conflicts before the next roster is issued,” it can be tested.

Use worker representatives in the design, not only in the final presentation. They can identify where a proposed fix moves pressure to another group or creates a new reporting burden. Their input is especially important when the lead is new and has not yet learned which formal controls are routinely bypassed.

Keep the test small enough to learn from and serious enough to matter. The purpose is not to claim improvement from a short pilot. It is to demonstrate that evidence leads to a management decision, and that the decision is checked in the work.

Month 3: design the survey around decisions

By month three, the lead should know what the survey must clarify. Build questions around work conditions that managers can influence, such as workload predictability, staffing adequacy, control over sequencing, supervisor support, conflicting priorities, recovery time, and confidence in reporting concerns.

Keep the instrument short enough that employees can answer thoughtfully. A long questionnaire can create response fatigue while giving leaders more data than they can act on. Pilot the wording with people from different roles and shifts, then remove questions that are vague, judgmental, or impossible to connect to a decision owner.

Plan the reporting before collecting responses. Define the minimum group size for reporting, the route for urgent concerns, the way qualitative comments will be protected, and the meeting where leaders will decide actions. The survey should have a known destination before the first invitation is sent.

Include a field check after the results are shared. The roster-change screen offers a practical comparison point for testing whether a reported exposure reflects schedule design, staffing, recovery time, or a combination of conditions. The review of impossible deadlines also helps leaders distinguish a demanding target from a work system that makes safe completion structurally unlikely.

What should the lead do after the first survey closes?

Sort findings by decision level, not by the order in which they appear on the dashboard. Some issues require a local work-design change. Others require a regional policy decision, a specialist investigation, or an individual support route. A single priority list hides those differences and encourages the lead to chase the easiest action.

Give each action a named owner, due date, interim protection, and verification method. If a team reports impossible workload, the interim protection might be a temporary staffing adjustment or a pause on nonessential work. The permanent response may require target changes, recruitment, process redesign, or a clearer escalation rule.

Review the findings with employees before closing the cycle. The lead should explain what was heard, what will change, what cannot change yet, and why. Silence after a survey teaches people that disclosure is a one-way transfer of risk from the worker to the organization.

James Reason’s work on latent failures is relevant here because a psychosocial exposure can be prepared by decisions made far from the person who experiences the pressure. The post-survey review should therefore ask which management conditions produced the pattern, rather than assigning the burden to resilience training alone.

Common mistakes in the first 90 days

The first mistake is launching a survey before defining the response. The second is treating employee wellbeing as a personal matter when the reported condition is a staffing, workload, or leadership problem. A third is assigning every action to HR or EHS, which gives the organization a coordinator but leaves the work unchanged.

Watch for four additional traps. Do not promise absolute anonymity when the process cannot provide it. Do not publish small-group results that expose individual voices. Do not use absence data as proof of a psychosocial cause. Do not label a manager as the risk when the evidence points to an incentive, staffing model, or decision rule that the manager cannot change.

In more than 250 cultural transformation projects supported by Andreza Araujo, the practical distinction is between a program that collects concern and a management rhythm that responds to it. The new lead should measure the second one.

Resources to deepen the role

Andreza Araujo’s Safety Culture: From Theory to Practice provides the culture and leadership foundation for connecting repeated decisions with operating conditions. Her Safety Culture Diagnosis workbook is relevant when the organization needs to build a disciplined evidence process rather than rely on impressions. Andreza Araujo’s books and safety resources can help leaders continue that work.

A new psychosocial risk lead does not need to become the organization’s therapist, investigator, or data owner. The role is to make work conditions visible, connect evidence to decision rights, and keep actions alive until someone verifies the change. If the first 90 days achieve that, the survey becomes useful because it enters a system that is prepared to act.