Workplace stress is a design problem, not a personal failing
Three classic models of occupational stress point the same way: the fix lies less in yoga sessions and more in how jobs are built.
When an organisation notices its people are stressed, the first response is usually a workshop. A wellness week, a session on breathing, perhaps an app. These are not bad things, but they quietly carry an assumption: that stress lives inside the employee, and that the employee should learn to cope with it better.
Fifty years of research on occupational stress suggests a different place to look. Stress is, to a large degree, a property of the job, of how work is designed, resourced and rewarded. That matters for anyone who manages people, because jobs can be redesigned in a way that personalities cannot.
Three models, one message
Demand and control. In 1979 Robert Karasek proposed that strain comes not from high demands alone but from high demands combined with low control over how to meet them. A surgeon and an assembly-line worker may both be under pressure, but the surgeon decides how to do the work. Karasek called the combination of heavy demands and little discretion high strain, and it is the combination, not the workload by itself, that predicts trouble.
Effort and reward. Johannes Siegrist’s effort–reward imbalance model, developed in the 1990s, adds fairness. People will put in great effort if they feel it is reciprocated, through pay, respect, security or a chance to progress. When effort stays high and reward stays low, the imbalance itself becomes a source of strain.
Demands and resources. The job demands–resources model (Demerouti, Bakker and colleagues, 2001) brings these ideas together. Every job has demands, which cost energy, and resources, which help people meet those demands and grow: autonomy, feedback, supportive colleagues, a manager who listens. Burnout follows when demands outrun resources for long enough; engagement follows when resources are plentiful.
All three point to the same conclusion. The levers that matter most — control, fairness, support — sit in the hands of the organisation.
Why sector matters
In my own research with colleagues on knowledge-intensive sectors, one theme keeps returning: the sources of strain are not the same everywhere. A software team, a hospital ward and a college department are all “knowledge work”, yet what drains people differs. In one it is constant interruption; in another, emotional labour; in a third, administrative load that crowds out the work people came to do.
That is why generic interventions disappoint. A meditation session cannot fix a reporting process that eats every evening. Before prescribing a remedy, a manager has to diagnose the specific demands and the specific missing resources in this job.
Quality of work life is the other side of the coin
Richard Walton’s well-known criteria for quality of work life, set out in 1973, read almost like a checklist for reducing strain: adequate and fair pay, safe and healthy conditions, the chance to use and develop one’s abilities, opportunities for growth and security, social integration at work, constitutionalism (rights and fair process), a balance between work and the rest of life, and a sense that the work is socially relevant.
When these are present, people still face hard days, but the hard days happen inside a job that gives something back.
What a manager can actually change
You do not need a large budget to act on this. Five places to start:
- Give people more say in how they work. Even small choices — the order of tasks, the method, the timing — raise control without lowering standards.
- Remove a demand before adding a programme. Ask your team which report, meeting or approval step costs the most for the least value, and cut it.
- Make reward visible. Recognition is a resource. Say specifically what someone did well, soon after they did it.
- Protect recovery time. Messages at midnight teach everyone that evenings belong to the job.
- Ask, then measure. A short, anonymous survey on demands and resources, repeated each term, tells you whether changes are working.
The point for students
If you are studying organisational behaviour, treat stress as a question of design. When you analyse a case, ask: what are the demands here, what resources are missing, where is effort going unrewarded? You will find that the most useful answers are rarely about the employee’s ability to cope, and almost always about the job they have been given.
Further reading: Karasek (1979), “Job demands, job decision latitude, and mental strain”, Administrative Science Quarterly; Siegrist (1996), “Adverse health effects of high-effort/low-reward conditions”, Journal of Occupational Health Psychology; Demerouti, Bakker, Nachreiner and Schaufeli (2001), “The job demands–resources model of burnout”, Journal of Applied Psychology.
Common questions
What is the demand-control model of stress?
Robert Karasek's 1979 model holds that strain comes from the combination of high job demands and low control over how to meet them. Jobs with heavy demands and little discretion, which Karasek called high-strain jobs, carry the greatest risk.
What is the effort-reward imbalance model?
Johannes Siegrist's model holds that stress arises when the effort people put into work is not matched by rewards such as pay, respect, security or the chance to progress. The imbalance itself is a source of strain.
What is the job demands-resources model?
The job demands-resources model (Demerouti, Bakker and colleagues, 2001) says every job has demands, which cost energy, and resources, such as autonomy, feedback and supportive colleagues, which help people cope and grow. Burnout follows when demands outrun resources; engagement follows when resources are plentiful.
How can managers reduce workplace stress?
Give people more control over how they work, remove low-value demands such as unnecessary reports or meetings, recognise good work specifically and soon, protect evenings and recovery time, and survey the team regularly on demands and resources to see whether changes work.