When performance slips, managers reach for two familiar levers. If work is behind, they push harder: more overtime, more people, tighter deadlines. If money is short, they cut: headcount, maintenance, training, outside support. Both responses feel decisive, and sometimes they are exactly right. But both can also make the underlying problem worse, because they act on the symptom while strengthening the cause.
Consider a project that falls behind. Management adds labour and authorises overtime. The number of people rises, but the work area does not. Crews get in each other’s way, fatigue builds, mistakes increase and rework grows. Output per person falls, the schedule tightens further and more pressure follows. Or consider a business cutting costs. Maintenance is deferred and an experienced technician is let go. Cash improves this quarter, but breakdowns rise next quarter, and the knowledge needed to fix them has walked out the door.
This article explains why performance is usually a property of the system rather than of individual effort, how reinforcing loops turn pressure into more problems, how to diagnose before pushing, and how to tell genuine waste from the capability a business needs to recover.
Performance is a system outcome
Output is produced by interacting conditions: the flow of work, the availability of materials and information, the physical space, the sequence of tasks, the quality of instructions, the skills and condition of the people, and the decisions of management. Treating productivity as a property of the workforce alone leads managers to act on the wrong part of the system.
Research on construction projects illustrates this. A published system dynamics study of labour productivity modelled the interactions between the project’s workflow, its workforce, its duration and cost, and labour productivity. It included factors such as fatigue, weather, crowding of the work area, skill, the efficiency of project management, schedule pressure, rework and workforce policies, and showed how they affect one another. The authors noted that more projects would be needed to validate the model broadly, so its specific numbers should not be generalised. Its value is the way of thinking: performance emerges from relationships, not from any single factor.
Reinforcing loops
A reinforcing loop is a cycle in which a change feeds back to amplify itself. In operations, one of the most damaging runs like this:
schedule pressure → rushed or out-of-sequence work → more defects and rework → less useful output → more schedule pressure
Rework consumes the same people and time needed for the remaining work, so the completion forecast worsens and pressure rises again. Managers who measure only hours worked may see effort increasing and conclude that people are trying hard. They are, but the system is converting more of that effort into failure demand: work created by not doing something right the first time, such as fixing defects, answering chasers, expediting and redoing tasks.
The way out of a reinforcing loop is to break it, usually by removing the cause of rework or relieving the constraint, rather than by adding more pressure.
More people can mean less output
Every work area and process has physical and coordination limits. When more people are added than the space, equipment or supervision can support, they interfere with each other, wait for access and need more coordination. Output per person falls, and total output may rise only a little or even fall. The same happens in offices, design teams, maintenance shutdowns and software projects: adding people to a constrained workflow can increase queues, handovers and communication load.
Before adding capacity, identify the constraint. If the limit is access to a work area, a key piece of equipment, materials, drawings or a decision-maker, adding people elsewhere will mostly create waiting.
Overtime and fatigue
Short periods of overtime can help recover from a temporary problem. Sustained long hours tend to reduce output per hour, increase errors and raise safety risks as fatigue accumulates. Employers have duties to manage risks to health and safety, including fatigue, and employees’ hours are governed by awards, agreements and employment law. Check current guidance from Safe Work Australia, your state work health and safety regulator and the Fair Work Ombudsman. From a performance point of view, treat overtime as a short-term tool, not a recovery plan.
Management conditions shape output
Management decisions set many of the conditions under which people work: the sequence of tasks, whether materials arrive on time, how quickly questions are answered, how clear instructions are, how work is balanced and how quality is checked. When these conditions are poor, people appear slow because they are waiting, correcting or working around problems. A productivity problem is often a management design problem that shows up in front-line output. That is not a matter of blame. It is a matter of putting accountability where the cause sits.
Diagnose before you push
When output falls, work through six layers before adding labour, overtime or pressure:
- Useful output: how much accepted, finished work is being completed, as opposed to started or touched?
- Flow constraint: where is work waiting? Look for materials, information, equipment, approvals, access, earlier tasks or specialist skills.
- Rework loop: how much time goes into correcting earlier work, and what causes the defects?
- Resource interaction: would more people increase output, or create congestion and coordination overhead?
- Human condition: what roles do fatigue, skill gaps, morale, absence or safety concerns play?
- Management condition: which decisions, delays, sequencing rules or information failures are producing the current behaviour?
Observing the work directly, rather than relying only on reports, is often the fastest way through these questions.
The same trap applies to cost cutting
Cost cutting under pressure follows the same pattern. Some costs are genuine waste. Others protect the capability the business needs to serve customers and recover. A useful discipline is to classify every proposed cut:
| Type of cut | What it does | Example | Risk |
|---|---|---|---|
| Waste removal | Removes cost that creates no value | Duplicate approvals, unused subscriptions, avoidable rework | Low, if the waste is real |
| Demand reduction | Stops work that is not worth doing | Discontinuing unprofitable products or low-value projects | Moderate; needs honest assessment |
| Capability removal | Removes skills, capacity or relationships | Letting go of an experienced maintainer or planner | High; slow and costly to rebuild |
| Deferred obligation | Moves cost into the future, often larger | Skipping maintenance, delaying training | High; cost returns with interest |
Waste removal and demand reduction usually strengthen the business. Capability removal and deferred obligations can improve the next quarter while weakening the next year. Sometimes they are unavoidable, but they should be chosen deliberately, with their consequences understood.
Remove failure demand before removing capacity
If people are busy with rework, expediting, duplicated effort and recurring breakdowns, cutting headcount without removing those causes leaves fewer people doing the same failure work, which leads to longer queues and worse service. Removing the causes first releases capacity sustainably. Productivity improvement and cost reduction then become the same activity.
Protect scarce knowledge and reliability
Experienced maintainers, planners, estimators, operators and customer-facing staff often hold knowledge that is not written down and is slow to rebuild. Preventive maintenance and good supplier relationships are similar: they cost money visibly and prevent losses invisibly. Before cutting, ask which capabilities would take longest to rebuild, and protect them, even if it means harder choices elsewhere rather than spreading cuts evenly.
Stop work rather than shave everything
Pressure exposes activities, products and projects that consume attention without enough value. Stopping a few of them entirely often frees more capacity than making everything 10% cheaper. It is harder, because each activity has supporters, but it leaves a simpler and stronger business rather than a smaller version of the old one.
Stabilise the most urgent constraint first
In a genuine crisis, start with what most threatens survival or customers right now: cash, a failing asset, a major backlog, a quality escape or a supplier failure. Concentrate resources there. A rolling cash forecast, often prepared week by week for about 13 weeks, helps show how much time the business has. Stabilising the urgent constraint can require spending that seems to contradict a cost-cutting message, which is why the reasoning should be explained clearly.
A worked example
This is an illustration. A small fit-out contractor is four weeks behind on a shop fit-out with six weeks left on the program. Eight workers have been completing about 100 inspected and accepted units of work a week, such as installed fittings and finished sections, over a 40-hour week.
The manager adds four workers and Saturday overtime. Twelve people now work about 50 hours a week each, 600 hours in total. Accepted output rises only to about 110 units a week. Output per hour falls from about 0.31 units (100 ÷ 320 hours) to about 0.18 units (110 ÷ 600 hours). About a quarter of the hours are going into rework after inspections find problems.
The supervisor works through the six layers and finds that:
- The constraint is access: crews wait for ceiling areas while other trades finish, and two crews often need the same zone.
- Materials arrive late: some deliveries are not checked against the next day’s work.
- Drawing questions take days: crews guess rather than wait, which causes rework.
- Fatigue is rising: errors are concentrated late in long days.
The changes are to re-sequence work by zone so crews do not overlap, check materials daily against the next day’s plan, appoint a named person to answer drawing questions within 24 hours, have the supervisor check rough-in work before it is covered, and reduce the crew to ten working about 42 hours each, with Saturday work only for specific tasks.
With 420 hours a week, accepted output rises to about 150 units a week, about 0.36 units per hour, and rework falls to under 10% of hours. With about 600 units remaining, the job would have taken about five and a half more weeks at 110 units a week. At 150 units a week, it takes about four, with fewer people and less overtime.
How this applies to a small Australian business
Small businesses feel pressure quickly, and the instinct to push or cut is strong. Practical steps:
- Measure accepted output, not just hours or activity.
- Find where work waits before adding people.
- Track rework and its causes.
- Use overtime briefly, and manage fatigue within your work health and safety duties.
- Classify cost cuts as waste removal, demand reduction, capability removal or deferred obligation.
- Protect knowledge that would be slow to rebuild.
- Stop low-value work rather than trimming everything.
- Prepare a rolling cash forecast in a cash squeeze, and talk to your accountant early.
The articles on steering a small business through a downturn and lean as an operating system cover related practices.
Signals worth watching
- Overtime rising while accepted output stays flat.
- More people without proportionally more output.
- Growing rework or defects.
- Recovery plans that add pressure without removing constraints.
- More work in progress but slower completion.
- Maintenance deferral and rising breakdowns.
- Key people leaving faster than their knowledge can be captured.
- Low-value activities continuing while core capacity is cut.
Common mistakes
- Treating productivity as worker effort alone.
- Adding people to a constrained area.
- Relying on sustained overtime.
- Measuring hours rather than accepted output.
- Cutting capability and deferring maintenance without counting the consequences.
- Spreading cuts evenly instead of protecting critical capability.
- Keeping low-value work while cutting core capacity.
Frequently asked questions
Is it ever right to add people to a late job? Yes, when the constraint is labour and there is space, supervision and work ready for them. Check those conditions first.
How do we tell waste from protective capacity? Ask what would happen if the cost disappeared. If nothing of value would be lost, it is waste. If failures, delays or lost knowledge would follow, it is protective, even if it looks idle at times.
How do we measure accepted output in office or project work? Count finished items that the next person or the customer accepts without return: approved drawings, completed jobs signed off, invoices paid without query. Track how many come back for correction. Activity counts such as emails sent or hours booked say little about useful output.
What if we must cut capability to survive? Sometimes that is unavoidable. Do it deliberately: document critical knowledge, keep relationships warm and plan how you would rebuild if conditions improve.
Questions to ask
- What is the constraint on useful output in our most important work?
- How much of our capacity is going into rework or waiting?
- Where would adding people or overtime reduce productivity?
- Which management decisions shape the conditions our people work in?
- Which proposed cuts remove waste, and which remove capability or defer obligations?
- What capability would take longest to rebuild if we lost it?
- Which activities would we stop entirely rather than make slightly cheaper?
Bringing it together
When performance falls, pushing harder or cutting deeper can feel like control, but both can strengthen the cause of the problem. Performance is a system outcome shaped by flow, constraints, rework, space, fatigue and management decisions. Diagnose before you push: measure accepted output, find where work waits, break rework loops and check whether more resources would help or congest. When cutting costs, separate waste and low-value work from capability and deferred obligations, remove failure demand before removing capacity and protect the knowledge you will need to recover. Change the system, and effort starts to produce results again.
Source: KEVOS notes, drawing on F. Nasirzadeh and P. Nojedehi, “Dynamic modeling of labor productivity in construction projects”, International Journal of Project Management (2013). Examples and figures in this article are illustrations. This article is general information, not legal or workplace advice.
