Workload
The problem with an overloaded job is rarely the quantity in the abstract. It is the quantity combined with an inability to influence what arrives, in what order, or to what standard it must be done. Give a person facing more work than they can do the authority to decide what will not be done, and you have converted an intolerable job into a hard one. Refuse them that authority while continuing to send the work — which is what happens when every item is mandatory and every deadline is external — and you have designed a job whose occupant must either fail visibly or fail invisibly, and most people, sensibly, choose the second, which is how organisations come to be full of work that is recorded as complete and was not done.
from A Guide to Occupational Psychology: People, Work and Organisations in the Modern UK (2026)
GPT-5.6 Sol:
The passage makes a stronger claim than the familiar one that “too much work causes stress.” Its real subject is control under overload. A workload becomes especially destructive when three things coincide: demand exceeds capacity, priorities are externally imposed, and the worker is denied legitimate ways of reconciling the two.
That distinction matters because “too much work” is not a completely objective category. Suppose someone has 60 hours of potential work available in a 40-hour week. That is certainly overload in one sense, but there are radically different jobs hiding inside that description. One worker can say: A and B matter most; C will slip; D gets a lighter treatment; E is cancelled. Another is told that A–E are all essential, all deadlines are firm, and all must meet the normal standard. The first person faces scarcity and has to exercise judgement. The second faces a logically inconsistent set of instructions.
This is close to what occupational psychology has long found about job demands and decision latitude. High demands are not necessarily disastrous when accompanied by meaningful control. A demanding job with discretion can be exhausting but intelligible: the person can allocate effort, sequence tasks, improvise, and protect what matters most. High demand with low control is different. The individual bears responsibility for outcomes while lacking authority over the choices necessary to produce them.
There is also an important distinction here between autonomy over means and autonomy over commitments. Organisations often congratulate themselves for giving employees the former: “manage your own diary,” “work however suits you,” “we trust you to deliver.” But if the employee cannot renegotiate scope, deadlines, quality or priorities, that autonomy is largely cosmetic. They have freedom to choose how to attempt the impossible, but not freedom to make it possible.
The sentence about the authority to decide “what will not be done” gets to the heart of prioritisation. Genuine prioritisation is not ranking twenty items from 1 to 20 and then expecting all twenty. It requires deprioritisation. Something must receive less time, arrive later, be done to a lower specification, be delegated, or not happen at all. Without this, “priority” simply becomes an adjective attached to everything.
That is why the phrase “every item is mandatory and every deadline is external” describes a particularly dysfunctional system. It abolishes the ordinary mechanisms by which finite capacity is reconciled with demand. Management has effectively said:
We will specify the commitments, but you will absorb the capacity problem.
The contradiction then moves down the hierarchy. Senior management may never explicitly instruct anyone to cut corners. Indeed, it may repeatedly insist that corners must not be cut. But if it simultaneously imposes more mandatory work than can be completed to the stipulated standard, corner-cutting has already been selected as the de facto operating model. It has merely been selected without being acknowledged.
That explains the passage's distinction between visible and invisible failure. Visible failure means allowing the impossibility to appear in the official system: missing the deadline, refusing the task, reporting the backlog, declaring the target unachievable. Invisible failure means preserving the appearance of compliance while degrading something that is harder to observe: checking becomes cursory, records are completed retrospectively, consultations get shorter, tests are skipped, maintenance becomes nominal, cases are closed prematurely, documentation is copied forward, risks are waved through, or “done” slowly ceases to mean done.
Calling that choice “sensible” is deliberately provocative, but defensible as an account of incentives. If an organisation punishes visible non-compliance more reliably than it detects degraded quality, employees learn where failure is safest.
Imagine two nurses, engineers, auditors or caseworkers. One says, “I completed 14 of the 20 required cases properly; six remain outstanding.” The other marks all 20 complete but performs each at roughly 70% of the intended depth. If the organisational measurement system primarily records completion rates, the first appears to be the weaker performer. The organisation has therefore created an incentive to convert observable backlog into unobservable quality loss.
This is one of the more important implications of the passage. Chronic overload can corrupt information systems. Once workers adapt by making failure invisible, senior managers stop receiving reliable evidence about capacity. Dashboards remain green. SLAs appear to be met. Required forms have ticks in their boxes. The absence of recorded failure is then interpreted as evidence that the workload was feasible after all.
A feedback loop develops:
excess demand → hidden shortcuts → apparent successful delivery → management concludes capacity is adequate → further demand → more hidden shortcuts.
Eventually the organisation can become surprisingly ignorant about how its own work is actually performed. Formal procedures describe one organisation; everyday practice constitutes another.
There is a connection here with several familiar organisational phenomena: work-to-rule gaps, workaround cultures, normalisation of deviance, metric gaming, defensive documentation, technical debt, audit rituals and bureaucratic decoupling. They are not identical phenomena, but they share a family resemblance. Formal requirements exceed what the operating system can sustainably deliver, so people create an unofficial operating system underneath the official one.
The quotation is particularly good on the role of standards, because capacity is not merely a function of task count. Workload can be represented more realistically as something like:
Required capacity = Σᵢ (quantityᵢ × standardᵢ × complexityᵢ)
An organisation can reconcile workload with available capacity by altering quantity, timing, specification, resources, or process. Dysfunction begins when every variable except employee effort is declared fixed. At that point, the only remaining adjustments are overtime, acceleration, omission and pretence.
There is, however, one respect in which the passage overstates its case. Control cannot neutralise unlimited workload. Giving someone the right to choose which patients not to treat, which safety checks not to perform, or which statutory obligations to ignore does not magically make an impossible system healthy. Above some level, quantity itself is the problem. Decision latitude moderates overload; it does not repeal arithmetic.
Nor can all priorities properly be devolved. In safety-critical, regulated or highly interdependent work, individual workers may lack the information or authority to decide which obligations can safely disappear. The appropriate answer is therefore not simply “give workers autonomy.” It is to place prioritisation authority at the lowest level possessing both the necessary information and legitimate authority, and to create a functioning escalation mechanism when commitments exceed capacity.
That produces a rather more demanding managerial principle:
No manager should impose a new mandatory commitment without accepting responsibility for what it displaces.
That is far harder than telling staff to “prioritise.” If five tasks already consume available capacity and a sixth becomes urgent, the management decision is not merely to add task six. It is to decide whether 1–5 will be delayed, reduced, resourced differently, or cancelled. Refusing to make that decision does not avoid prioritisation. It delegates prioritisation covertly to the employee while denying them permission to admit that they are doing it.
This is also why exhortations about resilience, time management and productivity can become insulting in badly designed jobs. Those interventions are useful where the problem is genuinely inefficient individual behaviour. They are beside the point where committed demand structurally exceeds capacity. Teaching someone to organise an impossible workload more elegantly does not resolve the contradiction.
The deepest claim in the passage, then, is institutional rather than psychological. Overload does not merely make individuals tired. Unacknowledged overload changes the epistemology of the organisation. It teaches people to conceal trade-offs, converts quality problems into invisible ones, and progressively destroys management's ability to know how much work is actually being done and to what standard.
A well-designed organisation therefore needs more than reasonable workloads. It needs an explicit scarcity protocol: when capacity is insufficient, somebody is authorised to say this matters more than that; this will be late; this will be done less thoroughly; this will not be done at all. And those decisions must be visible rather than disguised.
That is what separates a genuinely demanding job from an impossible one. In the former, scarcity produces choices. In the latter, scarcity is officially denied—so the choices still occur, but underground.
