THE DEFAULT LIFE: Work Harder Is Usually The Wrong Instruction
When I was twelve, I had a paper round.
Every morning, the four paperboys would arrive at the newsagent before school.
And every morning, we would wait.
The problem wasn't delivering the newspapers.
We could do that.
The problem was that the newsagent insisted on writing every customer's address by hand onto every paper before we were allowed to leave.
So the usual routine looked something like this.
Turn up.
Wait.
Watch the pile slowly get prepared.
Eventually receive your papers.
Then rush around the village trying to finish before school.
Everybody accepted this.
Including me, initially.
Then I started arriving earlier.
Not because I particularly fancied getting out of bed earlier at twelve years old.
I knocked on the door and asked whether I could help label the papers.
So instead of standing there waiting for the bottleneck, I helped remove it.
I left earlier.
Finished earlier.
And usually had my round almost done while some of the others were only just starting theirs.
For years, I thought that story demonstrated work ethic.
It does, partly.
I got up earlier.
I made an effort.
But that's not actually the interesting bit.
The interesting bit is that I didn't become better at rushing around the village.
I questioned why we were all standing around in the first place.
There is a massive difference.
And I think we spend far too much of adult life teaching people to improve the wrong side of that equation.
Something is difficult?
Work harder.
Falling behind?
Work harder.
Business struggling?
Work harder.
Too much to do?
Work harder.
Career not progressing?
Work harder.
Team overloaded?
Work harder.
Can't keep up?
Become more disciplined.
Faster.
More organised.
More resilient.
Get up earlier.
Stay later.
Push through.
Sometimes that's exactly the right advice.
Sometimes the answer genuinely is:
You need to put more fucking effort in.
But surprisingly often, hard work is being used as compensation for a system nobody has bothered to question.
Effort is seductive because it feels like action
If something isn't working, trying harder feels responsible.
You're doing something.
Nobody can accuse you of laziness.
That matters.
Especially if your identity is built around being hardworking.
I know this well.
For most of my life, if there was a problem, my instinct was to step towards it.
Take responsibility.
Sort it.
If the workload increased, I increased effort.
If someone dropped something, I picked it up.
If the system became messy, I compensated.
This behaviour gets rewarded.
Rightly, often.
Organisations need people who take responsibility.
Families do too.
Society would fall apart pretty quickly if everyone's first response to difficulty was:
“Sounds like a system problem. Not my department.”
Work ethic matters enormously.
The problem begins when effort becomes the only tool.
If your answer to every problem is work harder, eventually you become exceptionally good at preserving systems that should have changed years ago.
There are two completely different questions
The first is:
How can I do this better?
Useful.
The second is:
Should this still be done this way at all?
Much more dangerous.
The first question assumes the system.
The second interrogates it.
If processing an order takes forty minutes, one approach is to train people until they can do it in thirty-five.
Another is to ask why the process has eleven stages.
If a manager is overloaded, you can teach them better time management.
Or ask why seventeen decisions every day require that manager's approval.
If staff keep making mistakes at the end of a twelve-hour shift, you can remind them to concentrate.
Or examine why they're still working twelve hours.
If a business owner keeps getting interrupted by routine questions, they can become more efficient at answering.
Or build a system in which routine questions no longer need them.
Those are different philosophies of improvement.
One increases performance inside the existing system.
The other changes what performance requires.
Operations research learned this a long time ago
Manufacturing provides one of the clearest illustrations.
Imagine a production line with five stages.
Four can process 100 units an hour.
One can process 60.
How much can the whole system reliably produce?
Not 460.
Roughly 60 units an hour through the complete process, because the slowest constraint limits total throughput.
You can make one of the 100-unit stages 20 per cent faster.
Lovely.
It may make almost no difference to finished output.
You've improved activity.
Not the system.
This principle sits at the heart of the Theory of Constraints, a management approach that developed from production scheduling into a broader operations philosophy.
Its central argument is that overall system performance is constrained by limiting factors, and improvement efforts should be focused on those constraints rather than blindly optimising every individual component.
A 2023 systematic review of manufacturing bottleneck research makes the same practical point from a modern perspective: identifying the throughput bottleneck is a crucial first step because it determines where improvement activity can meaningfully increase system performance.
This sounds obvious when we talk about machines.
We are much worse at recognising it when the thing working harder is a person.
Humans become extremely convenient shock absorbers
Let's say a process is badly designed.
It creates four hours of unnecessary work a week.
One option is to redesign it.
That might require thought.
Meetings.
Investment.
Authority.
Risk.
Someone admitting the existing process is poor.
Another option is:
Give it to Sarah.
Sarah is brilliant.
She works quickly.
Never complains.
Always gets it done.
Problem solved.
Except the problem hasn't been solved.
Sarah has been installed as the workaround.
This happens everywhere.
The capable person becomes an unofficial system component.
Missing procedure?
Ask Dave.
Customer difficult?
Give it to Emma.
Nobody knows how this works?
Steve does.
Deadline impossible?
Adam will sort it.
For a while, this looks like good management.
The work gets done.
Then the organisation becomes dependent on the very person whose effort is disguising the design flaw.
Work ethic can hide bad systems
This is one of the reasons I think hard-working people are particularly vulnerable to this.
Lazy people expose inefficiency quite quickly.
If a process is needlessly difficult, they don't compensate very effectively.
The failure becomes visible.
Hard-working people can keep broken systems alive for years.
They absorb the friction.
Work longer.
Remember the undocumented details.
Create personal spreadsheets.
Keep notes in their heads.
Make the extra call.
Check everything twice.
Stay another hour.
The business experiences continuity.
The individual experiences workload.
Then management looks at the output and concludes:
The system works.
No.
The person works.
There is a difference.
We tend to measure output, not compensation
Imagine a task should take four hours.
Because of poor information, duplicated entry and unnecessary approval stages, it takes seven.
Someone works late and completes it.
What does the dashboard show?
Task complete.
Green.
On time.
Excellent.
It does not naturally show:
Three hours of human life were consumed compensating for process design.
That cost disappears inside labour.
This is one of the reasons human inefficiency can survive for so long.
People are flexible.
Machines are irritatingly honest.
A machine reaches capacity and stops producing more.
Humans improvise.
Rush.
Skip breaks.
Stay late.
Carry things mentally.
Take work home.
We can stretch.
Until we can't.
Work intensification is not the same as improvement
This distinction matters.
A business can increase output by making its system better.
Or increase output by getting more intensity from the same humans.
Both can look like productivity.
They are not necessarily the same achievement.
A systematic review published in 2024 examined 74 quantitative studies of work intensification from literature spanning 1989 to 2022.
Researchers found work intensification was commonly represented through higher workload, longer working hours and greater time pressure, with a body of evidence linking intensified work with a mixture of organisational and employee outcomes. The authors specifically argue that organisations need to manage overload, working hours and time pressure rather than assuming ever-increasing intensity is sustainable.
The point is not that asking people to work hard is harmful.
It's that:
More effort and better productivity are not synonyms.
You can produce more by improving the work.
Or produce more by consuming more of the worker.
The spreadsheet may initially struggle to tell the difference.
Long hours eventually demonstrate the same problem
There is an old and unusually useful piece of productivity research here.
Economist John Pencavel analysed historical data from British munitions workers and found output did not increase proportionately forever as working hours increased.
Beyond a point, additional hours produced diminishing increases in output.
His later analysis also found evidence that insufficient recovery could affect subsequent productivity, and weeks without a day of rest were associated with lower output in the particular historical workforce studied.
We should be careful with this evidence.
These were wartime industrial workers from a very different era.
There is no universal hour at which every modern knowledge worker suddenly becomes unproductive.
But the broader principle is hardly radical:
Human effort has diminishing returns.
There are limits.
That matters because “work harder” implicitly assumes effort is the variable we should keep increasing.
Sometimes it isn't.
My own career rewarded working harder for a very long time
This is why I don't dismiss it.
Hard work changed my life.
It helped me progress.
It built trust.
It gave me opportunities I wouldn't otherwise have had.
I was often willing to do things other people weren't.
Stay.
Help.
Take responsibility.
Ask what else needed doing.
And that mattered.
There is a current fashion in some corners of work culture to pretend effort is outdated.
Systems.
Leverage.
Passive income.
Automation.
Work smarter, not harder.
As though hard work is for people who haven't discovered software yet.
Bullshit.
A brilliant system executed badly is still badly executed.
There are moments where the answer really is:
Put the hours in.
Learn the skill.
Do the repetitions.
Finish the job.
Take responsibility.
Stop looking for a clever alternative to doing the fucking work.
But work ethic becomes dangerous when it prevents the second question:
Is effort still the constraint?
Sometimes you are the bottleneck because you haven't done enough
Let's be fair.
Your business might not have a systems problem.
You might have made fourteen sales calls this year.
Your fitness plan might not need optimisation.
You've exercised twice.
Your writing process might be fine.
You simply haven't written.
You might not need another productivity system.
You need to start.
Agency is not intellectualising your way out of effort.
That would make the entire idea useless.
There are people who redesign endlessly because execution frightens them.
New process.
New tool.
New plan.
New framework.
No work.
Sometimes “Is there a better way?” is just procrastination wearing glasses.
The hard part is knowing which problem you actually have.
Ask where the constraint is
That is the useful question.
What is genuinely stopping the outcome?
Lack of effort?
Skill?
Information?
Authority?
Capacity?
A process?
A dependency?
A decision?
A bottleneck?
A pointless step?
A person who shouldn't be involved?
A tool that no longer fits?
Too much work entering the system?
Too little demand?
If the constraint is effort, work harder.
If the constraint is somewhere else, more effort may just create heat.
That's the distinction.
Imagine a restaurant kitchen
Orders are arriving faster than food leaves the pass.
Everyone starts working harder.
Chef moves faster.
Kitchen porter rushes.
Waiters hover.
Stress rises.
Perhaps that helps.
For a while.
But suppose the actual constraint is one oven.
You can shout at the salad station all night.
The oven remains the oven.
This is why good operators look for flow rather than simply activity.
Where is work accumulating?
What is waiting?
Where are decisions delayed?
Which step constrains everything after it?
This way of thinking is ordinary in operations management.
It should probably be ordinary in knowledge work too.
Knowledge work hides bottlenecks beautifully
There is no physical pile of half-built products beside the machine.
Instead, the pile lives in:
an inbox,
someone's approval queue,
draft documents,
unanswered questions,
a CRM,
meeting actions,
things waiting for “when Sarah gets a minute”.
Because the blockage is less visible, people compensate with communication.
Chase.
Follow up.
Meeting.
Reminder.
Escalation.
Another spreadsheet.
Now the bottleneck generates secondary work around itself.
People become busy managing the fact that work isn't flowing.
Then someone decides the team needs to improve productivity.
Perfect.
A ridiculous amount of work exists because another piece of work is badly designed
Report gets produced because management cannot see the data.
Meeting exists because the report doesn't answer the real question.
Follow-up meeting exists because nobody made a decision in the first meeting.
Action tracker exists because nobody trusts verbal ownership.
Weekly email exists to update the tracker.
Someone spends Friday preparing the weekly email.
Then we teach them inbox management.
At some point, perhaps we should ask whether the original information problem can be solved properly.
This is what I mean when I say working harder is often the wrong instruction.
We frequently optimise the compensation rather than remove its cause.
Job design research gives this a human version
Organisational psychology has a concept called job crafting.
Rather than treating employees as passive occupants of jobs entirely designed by management, job crafting looks at ways employees proactively modify aspects of their tasks, relationships or resources to improve how work fits them and how they perform it.
A major meta-analysis covering 122 independent samples and 35,670 workers found job crafting associated with outcomes including engagement, satisfaction and aspects of performance, although the relationships varied substantially depending on the type of crafting involved.
More recent meta-analytic work involving 58 samples and more than 20,000 employees found evidence that certain forms of job crafting can improve wellbeing and work attitudes by increasing useful task and social resources.
But it also found something important: attempts to craft job demands did not always produce positive outcomes and could increase strain.
That's useful nuance.
People can improve their own work.
But individuals cannot personally redesign their way out of every structural problem.
“Be more proactive” can become another way to dump responsibility on workers
This is the risk.
Company creates unmanageable workload.
Solution:
Teach employees resilience.
Company has chaotic priorities.
Solution:
Time-management workshop.
Manager interrupts everyone constantly.
Solution:
Focus training.
Processes duplicate effort.
Solution:
Productivity software.
Nobody knows what is genuinely important.
Solution:
Personal prioritisation matrix.
There is a place for every one of those interventions.
But organisations need to be careful not to turn system design problems into personal capability problems.
If everyone in a team is struggling with the same barrier, perhaps everyone has not independently developed the same weakness.
Perhaps the barrier is real.
Job demands and job resources matter
One of the most established frameworks in occupational psychology is Job Demands–Resources theory.
Very broadly, it distinguishes aspects of work that require sustained effort from resources that help people achieve goals, manage demands or develop.
A major 2023 review of the theory summarised a large body of research linking excessive demands with strain and burnout processes while resources can support engagement and performance. It also highlights growing interest in proactive employee behaviour and interventions that change the work itself.
Again, none of this says effort is bad.
Demand is part of work.
Challenge can be motivating.
The issue is the lazy assumption that every performance gap should be closed by asking the human to supply more.
Sometimes the job needs redesigning.
The people closest to the work often know exactly what is wrong
This gets overlooked constantly.
Someone in senior management sees a process diagram.
The person doing the work sees:
the workaround,
the duplicate entry,
the customer question asked every single day,
the missing field,
the useless approval,
the machine that always jams,
the report nobody reads,
the person everything waits for.
This is why employee suggestions matter.
A 2025 study using data from 308 firms across fifteen countries and regions found employee suggestions were positively associated with continuous-improvement performance, both directly and through small-group problem-solving processes.
The effects were also shaped by how centralised organisational authority was, which makes intuitive sense: spotting an improvement and being allowed to do something about it are not the same thing.
There is something slightly ridiculous about employing people for years and never asking them:
What makes your job harder than it needs to be?
They usually know.
The best process-improvement question is often embarrassingly simple
What are you waiting for?
Not metaphorically.
Literally.
During your working week, where do you wait?
For approval.
Information.
A customer.
A manager.
A report.
A signature.
Materials.
A decision.
Access.
Another department.
That's useful.
Now ask:
What keeps being done twice?
What continually gets corrected?
What only one person knows?
What creates the most chasing?
What repeatedly becomes urgent?
Where does work pile up?
Which problem keeps returning?
What requires somebody to “work their magic”?
Those are clues.
A well-designed system should not continually require heroics to produce ordinary outcomes.
Heroes are often evidence
This is uncomfortable because businesses love heroes.
The employee who saves the client.
Rescues the deadline.
Works until midnight.
Solves the crisis.
Gets applause.
Sometimes deservedly.
But repeated heroics should trigger a second response after the applause:
Why was heroism required?
If one person continually saves the same process, that person may not be demonstrating how good the process is.
They may be proving how bad it is.
The problem is that heroics are highly visible.
Prevention is almost invisible.
Nobody celebrates the crisis that didn't happen because someone quietly redesigned a process six months ago.
Which means organisations can accidentally reward rescue more than prevention.
Working harder is immediate
Redesign is slow.
This is another reason effort wins.
The deadline is Friday.
Redesigning the system takes two weeks.
So we push through Friday.
Reasonable.
Then Monday arrives.
New deadline.
Push again.
Reasonable.
Then another.
Eventually “we don't have time to fix this because we're too busy dealing with the consequences of not fixing it” becomes the permanent operating model.
I have seen this countless times.
Most businesses do not consciously choose broken systems.
They postpone fixing temporary workarounds until the workarounds become normal.
Hard-working people make this possible.
Sometimes you have to temporarily work harder to permanently work less
This is where the simplistic “work smarter” slogan falls apart.
System improvement itself requires effort.
You may have to invest more time now.
Document the process.
Train someone.
Build the automation.
Create the template.
Write the procedure.
Clean the data.
Delegate badly before delegation becomes good.
Accept that another person will initially take longer.
I once used annual leave to redesign a department because I knew the existing efficiency programme would only keep working while I was physically there.
That was not an example of avoiding hard work.
It was a ridiculous amount of work.
But it was effort aimed at changing the future requirement for effort, rather than merely surviving another day.
The important distinction isn't hard versus smart.
It is:
Does this effort have to be repeated forever?
Some work pays once
Other work keeps paying.
Answer the same question for the hundredth time.
Pays once.
Create a clear guide that prevents the next ninety questions.
Keeps paying.
Fix today's scheduling conflict.
Pays once.
Redesign scheduling so the conflict stops recurring.
Keeps paying.
Personally check every job.
Pays once.
Develop competence and checks that allow the right people to own quality.
Keeps paying.
Work harder focuses naturally on today's output.
Agency keeps asking whether today's effort can also improve tomorrow's system.
This is not always management's job
Employees can do this too.
Within limits.
A 2026 review of 85 job-crafting studies describes job crafting as a mechanism through which employees proactively alter tasks, relationships and aspects of their working environment to better align work with their strengths and needs.
The literature broadly associates effective job crafting with outcomes such as wellbeing, satisfaction and engagement, while also recognising important contextual and methodological limitations.
The 2026 Annual Review of Organizational Psychology and Organizational Behavior similarly describes job crafting as potentially beneficial but emphasises that outcomes depend on how it is done, the surrounding culture and whether employees inadvertently increase their own workload or burnout risk.
That's exactly right.
Agency should not mean:
Unofficially take responsibility for redesigning the entire company while continuing your normal workload.
That's how the fixer trap starts.
The question is who has the authority to fix the constraint
If it's yours, good.
Act.
If it's your manager's, raise it.
If it's organisational, make it visible.
If nobody will change it, now you have different information.
You may decide to keep compensating.
You may decide the trade is worth it.
You may decide to leave.
But at least you're no longer interpreting the friction as evidence that you personally aren't working hard enough.
That matters.
Hard work has a strange moral status
We don't merely treat it as behaviour.
We treat it as character.
Hardworking.
Good.
Lazy.
Bad.
That creates a problem.
Because once effort becomes moral, questioning effort can sound morally suspicious.
“Can we make this easier?”
Why?
Don't you want to work?
“Do we actually need this report?”
Why are you being difficult?
“Could this be automated?”
Trying to get out of doing it?
Maybe.
But easier is not inherently worse.
A surgeon using better equipment isn't cheating.
A builder using a digger isn't showing insufficient grit.
Nobody praises an accountant for refusing Excel because manual arithmetic demonstrates work ethic.
Civilisation advances largely by finding ways to achieve outcomes with less wasted effort.
Yet at individual level, struggle still enjoys extraordinary status.
Difficulty is not proof of value
This deserves writing somewhere large.
Difficulty is not proof of value.
Some valuable things are difficult.
Learning.
Parenting.
Building something worthwhile.
Getting fit.
Doing the right thing when it's uncomfortable.
But making something harder does not automatically make it more worthwhile.
If I can achieve the same or better outcome in half the time with fewer errors and less stress, that's usually improvement.
The fact that someone historically suffered through the old method is not a compelling reason to preserve it.
We inherit inefficient work as readily as we inherit efficient work
“This is how we've always done it.”
There it is.
Another default.
Someone designed a process in 2014 because of a limitation that disappeared in 2019.
Nobody removed the process.
The workaround becomes policy.
The policy becomes onboarding.
New employee learns it.
Assumes there must be a reason.
Now a decision made twelve years ago by someone who left eight years ago controls Tuesday afternoon.
Organisations are full of ghosts.
Processes survive their causes.
Agency notices.
Before working harder, ask what happens if you don't
This can reveal a lot.
What happens if this report isn't produced?
Who notices?
What happens if approval moves down one level?
What happens if customers get the information automatically?
What happens if we stop attending this meeting?
What happens if the owner doesn't answer?
What happens if people make minor decisions themselves?
Sometimes disaster.
Good.
Keep the process.
Sometimes:
Nothing.
That's useful too.
You have found potential waste.
The opposite test matters as well
What happens if I work twice as hard here?
Does the actual outcome improve?
If the answer is no, effort probably isn't the constraint.
You can type faster while waiting two days for approval.
Doesn't matter.
You can answer every email instantly while customers wait three weeks for production.
Doesn't matter.
You can finish surveys more quickly while laboratory turnaround remains the rate-limiting stage.
Doesn't matter.
Local productivity is not necessarily system productivity.
Operations management has known this for decades.
Humans still take it personally.
This is why being busy is such poor evidence
A badly designed system can create extraordinary amounts of busyness.
In fact, inefficiency often produces more visible activity than efficiency does.
Chasing.
Correcting.
Explaining.
Updating.
Recovering.
Escalating.
Reworking.
Waiting.
Starting again.
The efficient version may look suspiciously calm.
That can create perverse incentives.
The person putting out fires appears indispensable.
The person who redesigned the building so fewer fires occur appears less busy.
Which one created more value?
We need better questions.
“Can you handle more?” is not always the same as “Can the system handle more?”
Capable people get asked the first question constantly.
Another client?
Another project?
Another direct report?
Another responsibility?
You probably can.
For a while.
But personal capacity is not the only variable.
Does the surrounding system scale?
Does information scale?
Decision-making?
Delegation?
Quality control?
Administration?
One person repeatedly saying yes can hide the point at which the system should have changed.
That was a huge part of my own working life.
I could handle more.
So I did.
Until “Adam can handle it” became part of the architecture.
Capability is useful.
Dependency is different.
We'll get properly into that later in this series.
Hard work is best when aimed at the right thing
That's the argument.
Not less effort.
Better target selection.
If you're learning something difficult, work hard.
If you've made a commitment, fulfil it.
If the constraint is skill, practise.
If the constraint is volume of attempts, make more attempts.
If the business needs sales, sell.
If the work needs doing today and redesign can wait until tomorrow, get it done.
But don't turn emergency effort into permanent architecture.
Afterwards, ask why it was needed.
Otherwise work ethic becomes a very expensive patch.
I would rather have someone who asks why than someone who merely moves faster
With one condition.
They still have to deliver.
There is nothing more tedious than the person who questions every process while everyone else does the work.
Agency without execution is just commentary.
The people who change organisations tend to combine both.
They can perform within the existing system.
That gives them credibility.
Then they notice where it can improve.
They don't use questioning as an excuse not to contribute.
They use contribution to understand the problem well enough to improve it.
That combination is powerful.
Better beats quicker
This has become one of my strongest beliefs.
Not because speed is bad.
Speed is useful.
But a quicker way can simply accelerate the wrong process.
A better way improves the outcome.
Sometimes better is quicker.
Often it is.
Sometimes better costs more.
Sometimes it requires more effort initially.
Sometimes it means slowing down.
The test isn't:
Did we make this easier?
Or:
Did we make this faster?
It is:
Did we improve the result for the system as a whole?
That is a more demanding standard.
The next time you feel overwhelmed, don't immediately optimise yourself
This is where I think modern productivity culture has done some damage.
You are behind.
So buy a planner.
Download an app.
Wake earlier.
Batch tasks.
Use Pomodoro.
Time block.
Prioritise.
All potentially useful.
But first:
Why is there this much work?
Why does it belong to you?
Which part keeps repeating?
What can be removed?
What requires your judgement and what merely requires completion?
What are you compensating for?
Where is the bottleneck?
Which task exists because another process doesn't work?
Who else could own this?
What would happen if it stopped?
There are people who do not need better personal productivity.
They need less bullshit entering the system.
Productivity starts before the task list
That may be the simplest way of saying it.
Traditional productivity starts with:
Here are the things I need to do.
How do I do them efficiently?
Agency inserts an earlier step:
Should all of these things exist in their current form?
That question can produce much larger gains than shaving three minutes off a task.
It can also be more uncomfortable.
Because tasks are safe.
Systems involve politics.
Authority.
Habits.
People.
Identity.
Changing them is harder than buying a new notebook.
The system might be you
We shouldn't dodge this either.
Sometimes the unnecessary process exists because you created it.
You insist everything comes through you.
You won't delegate.
You check work that doesn't need checking.
You attend meetings because you don't trust people.
You answer quickly, so people keep asking.
You redo things because nobody does them exactly your way.
Then complain that you're overwhelmed.
I have done versions of this.
At that point:
“I need to work harder”
is especially absurd.
You are feeding the machine that is eating you.
The solution requires changing your own behaviour.
Maybe you're not overwhelmed by work
Maybe you're overwhelmed by unresolved design.
That's not always true.
Some people simply have too much work.
Staffing can be inadequate.
Demand can genuinely exceed capacity.
No clever system eliminates arithmetic.
But repeated overload should at least create curiosity.
If this keeps happening, what keeps creating it?
There is a difference between a busy week and an operating model that depends on permanent overextension.
One is life.
The other is design.
The default instruction is effort because effort preserves everything else
This may be the deeper reason “work harder” survives.
It requires no structural change.
No role change.
No difficult conversation.
No investment.
No delegation.
No admission that the process is poor.
No challenge to authority.
No reduction in scope.
Just:
Try harder.
The system remains untouched.
That's convenient for the system.
Less convenient for the person supplying the additional effort.
Good organisations should want employees to expose friction
Not conceal it.
Tell me where work gets stuck.
Tell me what you repeat.
Tell me what makes no sense.
Tell me where customer frustration originates.
Tell me which approval adds no value.
Tell me what only you know.
Tell me what we keep fixing.
Tell me where you waste an hour.
That is valuable information.
The 2025 cross-national study of 308 firms is interesting precisely because employee suggestions and small-group problem-solving were associated with stronger continuous-improvement performance.
The person doing the job isn't always right.
But ignoring them is extraordinary waste.
Work ethic and agency need each other
I don't want to choose between them.
Work ethic without agency:
You become brilliant at carrying weight nobody needed to keep adding.
Agency without work ethic:
You become the person in the meeting with seventeen improvement ideas and no intention of doing any of the difficult implementation.
Work ethic says:
I will take responsibility for the work.
Agency says:
I will also take responsibility for questioning whether this is the best way to achieve the outcome.
Together, they're far more powerful.
So should you work harder?
Maybe.
That's the annoying answer.
Sometimes absolutely.
You haven't done enough.
You haven't practised enough.
You haven't made enough attempts.
You haven't fulfilled the commitment.
Stop redesigning and do the work.
But before effort becomes the permanent prescription, ask a better question.
What is actually constraining the result?
If the answer is you:
Get better.
Work harder.
Learn.
Practise.
Deliver.
If the answer is the system:
Stop trying to outrun it forever.
Fix the fucking system.
Because eventually there is nothing noble about becoming increasingly exhausted by a problem that could have been removed.
And perhaps that is one of the easiest defaults to miss.
We are so accustomed to respecting hard work that we rarely ask whether the work deserved to be that hard in the first place.
Sources And Further Reading
Kevin J. Watson, John H. Blackstone and Stanley C. Gardiner, “The Evolution Of A Management Philosophy: The Theory Of Constraints”, Journal Of Operations Management (2007).
A review of the development of the Theory of Constraints from production-scheduling software into a broader management philosophy covering production, performance measurement and problem solving. Its central contribution is focusing improvement activity on the constraints that limit overall system performance rather than assuming optimisation of every component improves the whole system.
Matthias Thürer et al., “Throughput Bottleneck Detection In Manufacturing: A Systematic Review Of The Literature On Methods And Operationalization Modes”, Production & Manufacturing Research (2023).
A systematic review identifying fourteen different methods for detecting throughput bottlenecks. The authors emphasise that bottleneck identification is a critical precursor to meaningful improvement because throughput is constrained by rate-limiting resources within the production system.
John H. Pencavel, “The Productivity Of Working Hours”, The Economic Journal (2015).
Analysis of historical British munitions-worker data found a nonlinear relationship between hours and output. Beyond a threshold, additional working hours produced progressively smaller increases in output, providing evidence that simply extending human effort does not necessarily produce proportional productivity gains.
John H. Pencavel, “Recovery From Work And The Productivity Of Working Hours”, Economica (2016).
Further analysis of historical industrial data examined how long working weeks and inadequate recovery affected subsequent performance, reinforcing the importance of recovery and the diminishing productivity of sustained long hours.
Aiman Niazi et al., “Work Intensification: A Systematic Review Of Studies From 1989 To 2022”, Work (2024).
A PRISMA-based systematic review screened 2,823 records and analysed 74 quantitative studies. Work intensification was commonly expressed through increased workload, long working hours and time pressure, with the review identifying a substantial body of research examining both organisational and employee consequences.
Arnold B. Bakker, Evangelia Demerouti and Ana Sanz-Vergel, “Job Demands–Resources Theory: Ten Years Later”, Annual Review Of Organizational Psychology And Organizational Behavior (2023).
A major review of Job Demands–Resources theory describing the relationship between job demands, strain and burnout processes, and the role of job resources in engagement and performance. The updated theory also gives increasing attention to proactive behaviour and interventions that alter work characteristics rather than focusing only on individual coping.
Cort W. Rudolph, Ian M. Katz, Kristi N. Lavigne and Hannes Zacher, “Job Crafting: A Meta-Analysis Of Relationships With Individual Differences, Job Characteristics, And Work Outcomes”, Journal Of Vocational Behavior (2017).
A meta-analysis of 122 independent samples comprising 35,670 workers found meaningful relationships between job crafting and outcomes including engagement, satisfaction and aspects of performance, while demonstrating that different forms of job crafting produce different relationships with workplace outcomes.
David Holman et al., “Does Job Crafting Affect Employee Outcomes Via Job Characteristics? A Meta-Analytic Test Of A Key Job Crafting Mechanism”, Journal Of Occupational And Organizational Psychology (2024).
Meta-analytic structural-equation modelling across 58 independent samples and 20,347 employees found that forms of crafting which increased task and social resources were associated with improved wellbeing and positive job attitudes. Attempts to alter demands showed more complicated effects and could increase job strain, illustrating that proactive redesign is not automatically beneficial.
“Job Crafting Revisited: Current Insights, Emerging Challenges, And Future Directions”, Annual Review Of Organizational Psychology And Organizational Behavior (2026).
A contemporary review of job-crafting research examining predictors, positive and negative outcomes, cultural context and intervention design. The authors emphasise that proactive redesign can create healthier and more engaging work but can also increase demands or burnout when poorly directed.
“Redesigning Roles Through Job Crafting: A Systematic Literature Review And Future Research Directions”, The Learning Organization (2026).
A systematic review of 85 articles published between 2014 and 2024. The review identifies job crafting as an important way workers proactively alter tasks, environments and interactions, while highlighting its relevance to wellbeing, job satisfaction, engagement and productivity.
Research on employee suggestions, small-group problem solving and continuous improvement (2025).
Using data from 308 firms across fifteen countries and regions, researchers found employee suggestions were positively associated with continuous-improvement performance directly and through small-group problem solving. Centralisation of authority influenced the relationship, highlighting the distinction between identifying improvements and possessing sufficient organisational freedom to act upon them.
Research Gaps
“Work harder is usually the wrong instruction” is deliberately provocative rather than a measured population-level statistic.
There is no research establishing that hard work is literally the wrong response to more than 50 per cent of workplace problems. The title expresses the essay's argument that effort is too often treated as the default intervention before the underlying constraint has been identified.
Theory of Constraints emerged primarily from operations and manufacturing.
The logic of identifying limiting factors can be conceptually useful in knowledge work and personal productivity, but a human team, career or professional workload is not identical to a production line. Organisational politics, creativity, relationships and ambiguous goals make many knowledge-work constraints harder to identify.
Most bottlenecks are not literally singular.
The classic Theory of Constraints emphasises focused attention on the limiting constraint, but complex organisations can contain interacting constraints whose significance changes over time. Simplifying every problem to one bottleneck can obscure important dependencies.
Pencavel's working-hours evidence is historically specific.
The most widely cited empirical analyses use British munitions workers from the First World War and other historical industrial settings. They demonstrate that output need not rise proportionately with hours, but they cannot establish one universal productivity threshold for modern workers or knowledge-based occupations.
Long hours can sometimes increase total output.
Diminishing returns do not mean additional hours always reduce total production. Even when hourly productivity falls, longer working hours may still increase absolute output. Whether the trade is worthwhile depends on task, duration, recovery, quality, safety and economic context.
Work intensification has heterogeneous outcomes.
Research does not show that every increase in workload or pace is harmful. Greater challenge can sometimes increase engagement or performance, particularly when people have sufficient resources, control and recovery. Persistent overload and temporary high effort should not be treated as identical.
Job crafting is not equivalent to organisation-wide process redesign.
Job crafting usually concerns self-initiated changes employees make to their own tasks, relationships or perceptions of work. Redesigning a production process, approval structure or company operating model involves different levels of authority and may require formal organisational change.
Employees cannot fix every system from below.
Research on proactive behaviour can unintentionally imply that workers should solve structural problems themselves. Authority, resources, leadership support, regulation and organisational design may limit what an employee can realistically change.
Employee suggestions are not automatically correct.
People closest to a process possess valuable local knowledge but may not see wider financial, legal, strategic or operational constraints. Effective continuous improvement requires combining frontline insight with system-level information rather than automatically implementing every suggestion.
The distinction between “system problem” and “effort problem” can be difficult to make.
Low performance may reflect several interacting causes including unclear goals, inadequate skill, insufficient effort, poor tools, workload, leadership, incentives and process design. Diagnosing the wrong cause can waste resources regardless of whether the chosen intervention is harder work or redesign.
Process efficiency can itself produce work intensification.
Removing waste does not automatically improve employee experience. Organisations can use efficiency gains to create more slack and better work, or simply increase production targets and tighten schedules. The allocation of productivity gains remains a separate decision.
Heroic effort is sometimes genuinely necessary.
Emergencies, unusual demand, failures and one-off critical deadlines may require temporary extraordinary effort. The concern in this essay is not exceptional effort but repeated heroics becoming a substitute for correcting recurring causes.
Individual examples cannot establish general causal relationships.
The paper-round, management and consulting examples illustrate how questioning a process can outperform simply applying additional effort in particular situations. They should not be interpreted as proof that every worker or organisation faces equivalent opportunities for redesign.
“Better beats quicker” is a decision principle, not a validated performance metric.
Better may mean faster, safer, cheaper, more reliable, less disruptive, more humane or some combination. Real improvement requires explicit objectives and trade-offs rather than treating “better” as self-evident.