Making workload a leadership conversation

Begin with a description of the work as it actually happens. Include scheduled tasks, interruptions, approvals, preparation, and the conversations required to keep things moving. A calendar may show meetings while hiding the work needed before and after them. A role description may list formal responsibilities without capturing the questions that repeatedly arrive because someone is experienced, available, or trusted.

Choose a representative period and describe the main demands in ordinary language. You do not need to account for every minute. The aim is to make competing expectations visible enough for a decision. For example, a person may be expected to lead a project, approve routine requests, and remain immediately available to several teams. Each expectation may appear reasonable in isolation while the combined arrangement is difficult to sustain.

Separate what is required from what has become customary. Ask who expects a particular task, what outcome it supports, and what would happen if its timing or format changed. Avoid assuming that a long-standing routine is necessary simply because it is familiar. Equally, do not dismiss responsibilities that are less visible to you. A useful discussion brings the whole demand into view so the people involved can decide what deserves attention and what can change.

When everything is described as urgent, the person doing the work may have to make hidden tradeoffs. Make those choices explicit. Ask which outcome takes precedence, which deadline can move, and what level of detail is appropriate. The decision should be made by someone with authority to accept the consequences, rather than left to an individual who is expected to satisfy incompatible demands.

Consider a team asked to prepare a major presentation while continuing its usual reporting. One option is to change the presentation date; another is to reduce a reporting requirement for a defined period. A third may involve additional help. The point is not that one option always works. It is that a concrete choice can be discussed, assigned, and reviewed.

Write down what is being deprioritized as well as what remains important. Otherwise, the postponed work may return later as an unexplained backlog or an accusation of poor performance. Clarify who will communicate the decision to affected people. A workload conversation becomes more useful when it ends with an agreed tradeoff, a person responsible for communicating it, and a date to reconsider the arrangement. General encouragement can accompany that decision, but it cannot make the conflicting requirements disappear.

Some workload comes from uncertainty about who can decide. A small question may travel through several people or return repeatedly because nobody knows which answer is final. Look for decisions that create delays, duplicate work, or unnecessary escalation. Ask whether the person receiving the question has the authority and information needed to resolve it.

A leader may unintentionally become the route through which every exception passes. Clarifying decision boundaries can change that pattern. For example, a team might be allowed to make routine adjustments within an agreed scope, with unusual cases going to a named colleague. The arrangement should include a way to ask for advice without transferring responsibility for every decision back to the leader.

Discuss how mistakes and uncertainty will be handled. People may keep escalating ordinary questions if the consequences of deciding are unclear. A practical agreement can specify which decisions need a record, which require consultation, and when a review will occur. This gives the organization a way to learn from the arrangement. It also helps distinguish a genuine need for senior judgment from a habit of seeking reassurance. Reducing unnecessary escalation can create space, but the change needs clear authority and support to be workable.

A person can describe a work difficulty without explaining every aspect of their health. Ask what practical information is needed to consider an adjustment and who should receive it. A manager's role may involve discussing responsibilities, availability, and agreed support. Clinical questions belong with qualified professionals. Keeping those roles clear can make the workplace conversation less intrusive and more focused.

Someone might say that their current schedule is difficult to sustain and ask to discuss a different pattern. The next step could be to clarify the demands and the available options, using relevant workplace processes where appropriate. It should not require colleagues to decide whether the person's distress is sufficiently convincing. Where professional recommendations are involved, discuss how their practical implications can be communicated without unnecessary personal detail.

Leaders also need a route for these conversations. Consider who can help them examine capacity, share authority, and make an absence possible if needed. That person may be a trusted colleague, a board representative, or another appropriate contact, depending on the organization. The arrangement should not rely on informal promises alone. Define the decision that needs to be made, the information required, and the people authorized to participate. Privacy and practical clarity can be maintained together.

An agreed change may look clear in a meeting and disappear during the following week. Check how it will be implemented. If availability changes, update the routes through which work arrives. If a responsibility moves, make sure the new owner has accepted it. If a deadline changes, tell the people whose plans depend on it. These details determine whether the adjustment becomes part of ordinary work.

Imagine agreeing that an employee will no longer attend a recurring meeting, while everyone still expects them to read a long transcript and answer follow-up questions immediately. The visible appointment has disappeared, but much of the demand remains. Ask what the change is intended to achieve and whether the surrounding expectations support that purpose. This makes review more precise than asking whether the person feels better.

Invite feedback from the people affected, including anyone taking on additional work. An adjustment should not silently transfer an unmanageable load to someone else. Consider what can be removed, simplified, or delayed across the team. If the first arrangement does not work, identify the specific obstacle and revise it. The aim is to create a practical system of responsibilities, rather than a temporary exception that depends on one person's continual negotiation or apologetic reminders.

Consider requests that arrive outside the agreed process. A new task may be sent directly to the person whose workload was supposed to change. Decide who will redirect it and explain the current priorities. Otherwise, the individual must repeatedly defend an agreement already made by the organization. Making that response part of the plan gives the adjustment practical support and prevents each exception from becoming a fresh negotiation about capacity in everyday work.

Set a review date when you agree on a change. Decide what information will be useful: which demands remain difficult, whether responsibilities are clear, and whether the arrangement is being followed. Avoid making the review an examination of someone's private health. It can focus on the work while leaving clinical matters with the appropriate professionals and the individual concerned.

Ask whether the original assumptions were accurate. Perhaps the volume of requests was underestimated, or a supposedly temporary project has become ongoing. A review gives the organization a chance to acknowledge those changes. It should also identify what is working, because useful arrangements can be lost when attention goes only to unresolved problems.

End with a clear next version of the plan. State what continues, what changes, and who will communicate the decision. If a question remains unresolved, name the person who will take it forward and when an answer is expected. Workload becomes a leadership conversation when the people with authority accept responsibility for these choices. Individual support may still be needed, but the organization can make its own contribution through realistic priorities, understandable decision rights, and a willingness to revisit how the work is arranged.