Performance Under Pressure: The Organisational Conditions That Support Sound Work

There is a familiar gap in pressured organisations: people are visibly working hard, yet the work becomes less clear, slower to coordinate and harder to finish well. Meetings create more follow-up than resolution. Teams protect urgent requests without a shared basis for trade-offs. Managers become the route through which every uncertainty has to travel.

The usual explanation is that people need to be tougher, more resilient or more accountable. Those qualities may matter in particular situations, but they are an incomplete explanation. If the work repeatedly arrives with competing priorities, unclear authority, missing information or unreliable hand-offs, individual effort can become the mechanism that conceals a design problem.

A more useful question is not, “Why are people struggling with pressure?” It is, “What conditions are we asking people to work within when pressure rises?” That keeps the focus on sound work: work in which people can understand the task, make appropriate decisions, coordinate with others and see what needs to happen next.

Pressure is not only a personal test

The distinction is between a demanding piece of work and a work system that makes demands harder to manage than necessary. A tight deadline with a clear outcome, named decision-maker and usable information is different from a tight deadline accompanied by changing priorities, conflicting instructions and approval routes no one can explain.

The UK Health and Safety Executive’s Management Standards offer a practical vocabulary: demands, control, support, relationships, role and change. In plain language, these concern the amount and pattern of work; say over how it is done; help and resources; working relationships; clarity of responsibility; and the way change is handled and communicated. [1]

How conditions shape work under load

One way researchers describe this is the Job Demands–Resources model. A job demand is an aspect of work that requires sustained physical or mental effort: for example, time pressure, complexity or difficult interactions. A job resource is something that helps people do the work, such as usable information, autonomy, manager support or clear feedback. A systematic review found substantial evidence for the model as a way of understanding work engagement and burnout, while also making clear that it is a framework rather than a universal recipe. [2]

When demands rise, people have less room to reconstruct a missing brief, negotiate a decision boundary or chase an owner for a dependency. If those tasks are routinely necessary, coordination becomes an additional job. A resource will not offset every demand, but recurring overload warrants inspection of work design before it is treated as an individual shortfall.

Questions that bring the conditions into view

Start with a live piece of work where pressure is already visible: a service peak, a cross-functional hand-off, a major change or a period of concentrated decision-making. Then ask questions that can be answered with examples rather than impressions.

What is the actual demand? Is the problem volume, volatility, complexity, emotional labour, a deadline, or several of these at once? Where does work bunch up, and what has to wait when it does?

Which trade-offs are people authorised to make? Can a team defer lower-value activity, adjust a sequence or resolve an exception within a clear boundary? If not, who can decide, and how quickly can the decision reach the point of work?

What support is available at the moment it is needed? This is not simply a question of goodwill. It includes access to a manager, specialist knowledge, functioning systems, timely information and colleagues who understand the dependency.

Where is responsibility unclear or duplicated? Ask people to describe the outcome they own, the decision they can make and the hand-off they rely on. Differences between those accounts often reveal a role problem before a performance problem.

What has changed without being translated into the work? A new priority, operating model, technology or target may be well understood at senior level while remaining ambiguous in day-to-day practice. What is different now, for whom, and what is no longer expected?

These questions make the operating context inspectable and help distinguish a one-off surge from a repeating pattern.

Make one pressure point easier to work with

A broad concern about pressure can feel too large to address. Begin instead with one recurring pressure point: the weekly allocation meeting, the customer exception process, the approval path that stalls delivery, or the first month of a major change.

Map the sequence briefly. What triggers the work? What information is needed? Who makes which decision? Where does it pause, get reworked or become dependent on informal help? Then choose one condition to clarify or improve. That might mean naming the decision owner, agreeing a visible rule for an exception, making a key input available earlier, or explaining a changed expectation before it reaches a team.

No single intervention can be assumed to work in every context. A review and meta-analysis of controlled work-engagement interventions concluded that such interventions *may* be effective, but found substantial variation between studies and limited ability to identify the important features. [3] Test changes in context and avoid treating a generic activity as a solution in itself.

Treat recurring friction as information

The most useful signal is often not the fact that a person found a week difficult. It is the recurrence of the same friction across people, teams or cycles of work: the same decision escalated late, the same dependency discovered too late, the same manager asked to reconcile incompatible demands.

That pattern is information about the system. It may point to an unresolved priority, an authority boundary, a resource constraint or a change that has not yet been made workable. It should not be used to make assumptions about any individual’s capacity or state of mind.

For leaders and HR/L&D colleagues, the next conversation is therefore practical. Which conditions are helping people direct effort where it matters? Which conditions are consuming effort without improving the work? And which recurring friction should be examined before asking individuals to compensate for it again?

No article can determine the right configuration for a particular organisation. The relevant pressures, responsibilities, relationships and constraints depend on the work, its risks and its operating context. The value of this framing is simply to make those conditions discussable before a preferred answer is assumed.