The Meeting That Never Resolves Anything
Picture a team that receives a new priority every morning. None of them replaces the previous one. By the end of the week, the manager asks why work is behind schedule and recommends better organisation. The team can tidy up its calendar, but it cannot make room for decisions that leadership refuses to take. When everything remains urgent, asking people to stay calm leaves the source of much of that pressure entirely untouched.
What Belongs to the Organisation
Established frameworks for occupational health identify excessive workload and limited control over one's work as meaningful risk factors. That reference does not allow anyone to diagnose an individual or to attribute every difficulty a person faces to their employer. What it does is help draw a boundary of responsibility: the way work is organised deserves scrutiny, rather than treating every struggle as a personal shortcoming.
I write here about leadership and operational decisions. A manager is not a substitute for health professionals, and a work conversation should not become a clinical investigation. But a manager is accountable for something that genuinely belongs to them: how tasks are distributed, whether priorities are coherent, and how they respond when someone signals that what was agreed is no longer executable. It is within that concrete margin that a declared concern for people can carry real consequence.
What the Register Does Not Show
Consider a hypothetical: someone holds a main project, responds to requests from three departments, and helps colleagues work through recurring problems. The planning document records only the main project. When a deadline slips, the situation looks like a productivity failure. In reality, the record may simply be incomplete. Before concluding that commitment is lacking, it is worth making visible the work that was requested and consumed time without ever formally altering the schedule.
This observation does not mean accepting every estimate without discussion. A team needs to talk about effort, skills, and quality. But that conversation improves when there is an accurate description of what work actually happened. The question shifts from why you did not manage to include what came in afterwards, what blocked execution, and which decision was missing. Individual responsibility remains; the organisation's responsibility stops disappearing from the picture.
The Hidden Cost of Small Interruptions
There are also small tasks that demand continuous availability. A response that takes a few minutes can break an activity that requires sustained concentration. Adding up only the minutes spent on replies does not capture the full disruption. There is no need to invent a figure to acknowledge the problem. It is possible to observe when interruptions occur, where they come from, and which ones could be grouped, delegated, or resolved by making information accessible to the right people in advance.
Every New Priority Needs a Decision About the Old One
I would argue that every new priority must arrive with a decision about the work already in progress. That decision might suspend a task, shift a deadline, reduce the scope, or require additional resources. There will not always be a comfortable answer. Even so, making the choice explicit is better than handing the team a contradictory obligation and expecting the contradiction to be absorbed in silence. The urgency may be real; so is the available capacity.
The difficulty grows when different managers make requests of the same person. Each request appears reasonable in isolation. Together they may be impossible. In that situation, the person should not have to negotiate priority conflicts alone between people who hold considerably more power than they do. There needs to be a decision point that considers the whole picture, owns the choice, and communicates to the affected areas what changes as a result.
Delegating Execution Is Not the Same as Delegating the Conflict
That decision point does not require centralising every detail. It requires defining who resolves the collisions that the team cannot resolve at its own level. Leadership that asks for autonomy must distinguish between the freedom to organise execution and the obligation to arbitrate incompatible interests. Delegating a task without providing the conditions to negotiate its dependencies may simply transfer the strain to whoever has the fewest instruments to bear it.
A Useful Conversation Starts With the Work
A productive conversation can begin with the work itself: which commitments are competing for the same time? Which instruction was left ambiguous? What happens when something unexpected arises? There is no need to probe into anyone's private life to recognise that planning needs to be revised. A person may need specialist support; that should follow appropriate channels, with discretion, and without turning the act of seeking support into a test of loyalty to the organisation.
What a manager does after listening also matters. If they thank someone for their candour and keep every demand exactly as it was, the practical message is that speaking up changes nothing. Not every request can be accommodated, but there should be a comprehensible response. A small, followed-up, and reviewed adjustment can be more useful than a broad promise that nobody knows when will begin. The follow-through shows whether the conversation entered management or remained only in rhetoric.
Demanding Standards Without Starting From Suspicion
The concern about misuse tends to surface in this discussion. An organisation needs rules and needs to monitor work; it does not need to begin from suspicion every time a difficulty is reported. It can check deliverables, analyse obstacles, and address non-performance in concrete terms. Conflating rigour with generalised distrust weakens the very information leadership needs to function. If raising a limitation is always read as an excuse, those limitations will tend to surface too late.
A practical management exercise is to choose one team and, over a defined period, record priority changes, significant interruptions, and the decisions taken to accommodate them. This is not about monitoring someone minute by minute. It is about observing the effect of management choices on commitments that have already been made. Any such exercise should weigh the usefulness and proportionality of what is recorded, and avoid gathering unnecessary personal information.
The Right Questions at the End of the Cycle
Ultimately, the question is not only whether more was delivered. It is also whether work became more predictable, whether problems were raised earlier, and whether those in charge were able to decide without keeping everything simultaneously unresolved. These are questions about organisation, not a clinical assessment. An operational improvement does not authorise a company to declare its employees' wellbeing resolved. The scope of any conclusion should match what was actually observed.
I would like to see more leaders able to say: this task matters, but it will not come in until I resolve the conflict it creates with everything else. There is a kind of firmness in that sentence. It acknowledges the value of the work, the capacity of the people doing it, and the responsibility of whoever is deciding. Looking after a team includes providing the conditions to deliver. When every task remains urgent, the first agenda that may need reorganising is that of leadership itself.