How to Run a Workload Check-In in 12 Minutes Without Diagnosing Mental Health

A line manager notices that a reliable employee has started working late, missing small details, and answering every question with “I’m fine.” The manager can either treat those signals as a private problem or examine the work conditions that may be producing them.

A workload check-in gives the manager a disciplined middle path. It does not diagnose mental health, and it does not turn a supervisor into a therapist. It asks whether the demands, priorities, control, and recovery conditions are still workable, then converts the conversation into one owned management action.

Andreza Araujo’s work across more than 250 cultural transformation projects supports a practical principle. Leaders cannot ask people to make safer decisions while leaving workload pressure invisible. The first responsibility is to make the operating condition discussable.

What to prepare before the 12-minute conversation

Choose a private setting, protect the time from interruptions, and bring the employee’s current priorities rather than a generic well-being script. The purpose is to understand the work system well enough to decide what can change today, what needs a deeper review, and what belongs with a qualified support function.

Do not begin after a performance warning or only when someone looks distressed. A predictable check-in is safer because it normalizes discussion before pressure becomes a crisis. The method below works best when managers use it across the team with the same basic sequence.

Step 1: State the purpose without labeling the person

Start by naming the management purpose in plain language. Explain that you are reviewing workload conditions, competing priorities, and the support needed to perform safely. Do not say that the employee looks depressed, unstable, burned out, or unable to cope.

Verify the opening by asking the employee to confirm that the conversation is about the work rather than a judgment about character or health. The common error is to make concern sound like an informal diagnosis, which can close the conversation before useful evidence appears.

Step 2: Map the work that is actually due

Ask the employee to list the tasks, deadlines, interruptions, and responsibilities that are active now. Separate work that is legally or operationally critical from work that is merely urgent because someone requested it loudly.

Verify the map against the team’s work plan, staffing, and known changes. A common error is accepting the job description as proof of the workload. The job description describes a role, while the check-in must examine the work that has accumulated this week.

Step 3: Find the pressure point

Ask which part of the workload is creating the greatest pressure and why. The answer may involve volume, ambiguity, conflicting instructions, repeated rework, customer aggression, shift coverage, or the fear that a delayed task will create consequences for other people.

Verify by asking for one recent example, including when the pressure appeared and what decision it affected. The common error is collecting a broad complaint without identifying the condition that a manager can actually change.

Step 4: Test priority conflict

Many workload problems are not caused by the number of tasks alone. They appear when the employee receives two priorities that cannot both be completed with the available time, attention, or competence. Ask which instruction should win when production, service, quality, and safety demands collide.

Verify the answer with the responsible owner, because a manager should not ask an employee to solve a priority conflict that belongs to leadership. The common error is telling the employee to “manage time better” when the organization has not made the decision rule clear.

Step 5: Check control over the work

Ask what the employee can change without seeking permission and where approval delays create avoidable pressure. Control includes the ability to sequence work, pause a task, request help, clarify a requirement, and escalate a concern before the deadline becomes unsafe.

Verify one decision that the employee can make independently and one decision that requires escalation. The common error is confusing autonomy with abandonment. People need room to act, but they also need a clear route when the decision exceeds their authority.

Step 6: Examine recovery between demands

Ask whether the current pattern leaves enough time to recover attention between demanding tasks, shifts, customer interactions, or incidents. Keep the question tied to work design. You are not asking for private medical information or trying to measure a diagnosis.

Verify the operational pattern by checking breaks, overtime, shift changes, on-call expectations, and after-hours contact. The common error is treating recovery as an individual discipline problem when the schedule repeatedly removes the opportunity to recover.

Step 7: Agree on one immediate work-design change

Choose one change that can reduce pressure without creating a new exposure elsewhere. Examples include removing a conflicting deadline, reallocating a task, protecting a break, clarifying an approval route, pausing low-value work, or adding competent coverage for a critical activity.

Verify the change by stating who owns it, when it starts, and what condition will show whether it helped. The common error is ending with encouragement instead of an operational commitment. Support becomes credible when the work changes in a visible way.

Step 8: Define the support route

Explain which support options exist and let the employee choose the route that fits the concern. Depending on the organization, that may include HR, occupational health, an employee assistance program, a trusted manager, or another qualified service.

Verify that the employee knows how to access the route without having to retell the entire story to several people. The common error is sending someone away with a list of contacts while leaving the manager responsible for the work condition unchanged.

Step 9: Set a review date and a trigger

Schedule a short follow-up before the conversation ends. The review should ask whether the agreed change happened, whether pressure moved somewhere else, and whether the employee needs a different level of support.

Add a trigger for earlier escalation, such as a missed critical control, unsafe fatigue, an inability to perform essential work safely, or a concern that requires urgent professional help. The common error is using a future meeting as permission to wait when the current condition already requires action.

Step 10: Record the management action, not private disclosure

Record the work condition, the agreed action, the owner, the review date, and any route that was offered. Do not write a speculative diagnosis or copy sensitive personal details into a routine management record.

Verify that the record can show whether the organization responded to the work-design issue. In Safety Culture: From Theory to Practice, Andreza Araujo emphasizes that culture becomes visible through repeated management choices, especially when operational pressure tests stated values. A common error is documenting the conversation so heavily that the person feels surveilled rather than supported.

What a good workload check-in should produce

How managers keep the conversation safe

The manager’s role is to make the work discussable, remove avoidable pressure, and connect the person with qualified support when the concern exceeds managerial responsibility. That boundary protects both sides. It avoids clinical overreach while preventing the organization from hiding a work-design problem behind a referral.

Andreza Araujo’s approach to safety culture is useful here because it keeps attention on the gap between declared care and operated care. If the manager asks about workload but refuses to change priorities, the conversation becomes a ritual. If the manager changes work without listening to the person exposed to it, the response becomes another form of control.

Use the 12-minute check-in as a repeatable leadership routine. A single conversation may reveal a local problem, but a pattern across several conversations can show where staffing, decision rights, scheduling, or recovery conditions require a broader management decision.

Final takeaway

A workload check-in is effective when it produces a clearer work condition, one practical adjustment, a qualified support route, and a visible review date. It does not require a manager to diagnose mental health. It requires the manager to notice when the way work is organized is making safe performance harder, then act before the pressure becomes normalized.

For more practical conversations about safety culture, leadership, and human performance at work, explore the Headline Podcast.