People Can Survive Hard Work Longer Than Pointless Work

The Work That Produces Nothing

People do not always burn out because the work is difficult.

Sometimes they burn out because the difficulty accomplishes nothing.

The report will not influence a decision.

The meeting will not solve the problem.

The approval will not improve the result.

The information already exists in another system.

The customer will still be transferred to somebody else.

The employee will explain the same issue again next month because everyone agreed it was important and nobody agreed to own it.

That kind of work creates a special exhaustion.

Your body is working.

Your mind is working.

Your calendar is full.

Your email is active enough to qualify as a small emergency.

Yet nothing meaningful is moving.

At the end of the day, you are tired without the satisfaction of having built, repaired, improved, taught, completed, or solved anything.

That is not simply hard work.

That is effort being converted into smoke.

I respect hard work.

I do not respect pointless hardship.

There is a difference.

Hard work builds something.

Pointless hardship burns calories and calls itself character.

Difficulty Is Not Always the Enemy

Some of the most satisfying work I have ever done was difficult.

Renovating a property is difficult.

Teaching students how to diagnose and repair technology is difficult.

Building a system from nothing is difficult.

Turning around a struggling operation is difficult.

Helping a customer whose situation does not fit neatly inside the approved script is difficult.

The work can be physical, frustrating, repetitive, mentally demanding, and occasionally held together by optimism, caffeine, and language that should not be repeated in a professional environment.

But you can see something changing.

The damaged room begins looking like a room again.

The student who needed help with every step starts recognizing the problem independently.

The customer leaves with a solution.

The broken process becomes usable.

The number moves.

The machine works.

The idea becomes real.

That progress gives energy back.

Not enough to make the work effortless. Not enough to eliminate stress or replace sleep. But enough to tell your brain:

“This is going somewhere.”

People can carry an extraordinary amount of weight when they understand why they are carrying it and can see themselves getting closer to the destination.

What destroys them is carrying the same weight around the same building while management calls it a journey.

Purpose Does Not Have to Be Dramatic

When people hear “purposeful work,” they sometimes imagine that every employee needs to wake up believing their job is saving humanity.

That is not realistic.

Not every spreadsheet is a spiritual calling.

Not every customer interaction will become a treasured memory.

Sometimes work is work.

People need income, insurance, stability, experience, and a way to pay the electric bill before the electric company begins communicating in a less friendly tone.

A job does not need to become your entire identity.

Purpose can be much smaller and more practical.

This record prevents a mistake.

This repair returns a device to a student.

This conversation helps a customer understand their options.

This inspection keeps someone safe.

This report allows a real decision to be made.

This process saves the next employee twenty minutes.

This follow-up prevents a person from being forgotten.

This lesson helps a student discover that they are capable of more than they assumed.

Purpose does not require dramatic music.

It requires a believable connection between effort and outcome.

Gallup found that U.S. employees with a strong sense of purpose at work were 5.6 times as likely to be engaged as employees with a low sense of purpose. Only 13% of those with strong work purpose reported feeling burned out very often or always, compared with 38% of employees with low purpose. Gallup defines that sense of purpose in practical terms: believing your work contributes to something important, positively affects others, or gives meaning to daily tasks. Gallup

That does not mean purpose magically protects people from exhaustion.

A teacher can believe deeply in education and still be overloaded.

A nurse can believe in patient care and still burn out.

A business owner can love the company and still reach a point where the body files a formal complaint.

Meaning is not a substitute for reasonable staffing, fair pay, sleep, support, or boundaries.

But meaning changes how effort is experienced.

There is a psychological difference between saying:

“This is difficult because the outcome matters.”

And:

“This is difficult because the organization refuses to fix something everyone knows is useless.”

Pointless Work Has a Particular Smell

Pointless work usually leaves clues.

Nobody can explain who uses the result.

The process duplicates information that already exists.

The task continues because “we have always done it.”

The approval protects no meaningful standard.

The meeting exists because another meeting ended without a decision.

The report measures activity instead of results.

The system moves responsibility without solving the problem.

Employees are asked for feedback, but every suggestion disappears into the same professionally decorated hole.

A problem is repeatedly discussed by people who do not have the authority, willingness, or intention to correct it.

The organization is not solving the issue.

It is performing concern around it.

That performance can look very productive.

There are agendas.

There are dashboards.

There are follow-up emails.

There are color-coded spreadsheets with enough conditional formatting to make the original problem feel underdressed.

There may even be a committee.

Nothing frightens a simple problem like twelve adults scheduling a monthly committee to observe it.

Eventually, people stop bringing their full energy to the process because they understand the agreement nobody will say aloud:

This does not need to work.

It only needs to look like work occurred.

The Meeting That Produces Another Meeting

Meetings are not automatically pointless.

A good meeting can clarify a problem, bring the right knowledge into the room, resolve disagreement, assign ownership, and produce a decision faster than fifteen separate conversations.

That is useful.

A pointless meeting has a different purpose.

It distributes responsibility so widely that nobody can be blamed for the absence of progress.

Everyone provides an update.

Everyone expresses concern.

Someone says, “We should definitely continue this conversation.”

Another person promises to “circle back.”

A follow-up meeting is scheduled to discuss the items that could not be addressed because the current meeting spent forty-five minutes reviewing information everyone had already received by email.

The calendar invitation becomes the final product.

Modern workers do not have a shortage of communication.

Microsoft’s 2025 Work Trend Index found that 80% of workers and leaders lacked enough time or energy to complete their work, while 53% of leaders said productivity needed to increase. Microsoft’s work-pattern data also found that employees were interrupted by a meeting, email, or notification about every two minutes during the workday. Microsoft Work Trend Index

We have created workplaces where people cannot complete the work because they are constantly being asked to discuss, document, announce, schedule, summarize, and provide status updates about the work.

Then leadership wonders why the work is late.

The employee is not always overwhelmed by the important task.

Sometimes the important task is the only part they cannot find time to do.

A Process Can Work Technically and Fail Completely

Organizations often judge systems by whether the required steps occurred.

The customer completed the form.

The ticket entered the queue.

The automated confirmation was sent.

The request was forwarded.

The employee selected the correct category.

The case was closed.

Every box received its checkmark.

Wonderful.

Did the person’s problem get solved?

That question occasionally arrives late to the celebration.

A process can be technically compliant and practically useless.

A customer can receive five perfectly professional messages without receiving one useful answer.

A teacher can complete every required data entry while having less time to work with students.

A manager can submit every report while the same operational problem grows underneath the reporting system.

A business can buy expensive software that successfully moves bad information faster.

The system worked.

Reality remains unimpressed.

This is why frontline employees become frustrated when leaders defend a process by showing that each required step occurred. The employee is looking at the outcome. Leadership is looking at the evidence that the organization followed the process.

Both may be telling the truth.

Only one of them may be solving the problem.

Researchers Have a Name for Some of This

Workplace researchers use the term illegitimate tasks for responsibilities employees perceive as unreasonable or unnecessary.

Unreasonable tasks feel inappropriate for the person’s role or circumstances.

Unnecessary tasks feel as though they should not exist at all—work created by avoidable inefficiency, broken systems, duplication, or rules that serve no useful function.

In two studies, researchers found that illegitimate tasks predicted resentment toward the organization, lower self-esteem, and burnout even after accounting for other work stressors. The important point was not merely that the tasks were unpleasant. Employees experienced them as violations of what could reasonably be expected from their role. Semmer and colleagues

That distinction matters.

Cleaning up a mess may not be in someone’s formal job description, but it can still be legitimate when the team needs help and everyone contributes.

I have no patience for people who hide behind a title while a preventable problem grows directly in front of them.

“That is not my job” is not always professionalism.

Sometimes it is fear wearing a name badge.

But an employee repeatedly entering the same information into multiple systems because nobody will correct the workflow is different.

A teacher documenting an intervention nobody will review is different.

A nurse spending more time satisfying a poorly designed administrative requirement than helping the patient is different.

A customer-service employee apologizing for a policy they are not allowed to question is different.

The task may be officially assigned.

That does not make it useful.

Red Tape Does Not Merely Waste Time

Red tape is often treated as an annoying but harmless feature of large organizations.

It is not harmless.

A study involving 354 school principals examined the effects of increasing or decreasing compliance requirements. Greater red tape increased emotional exhaustion and depersonalization while reducing feelings of personal accomplishment. Reducing the burden lowered exhaustion, although it did not immediately repair every dimension of burnout. Review of Public Personnel Administration

That last part should make leaders uncomfortable.

Adding pointless work may damage people faster than removing it repairs them.

Once employees have spent years learning that their effort changes nothing, eliminating one form does not instantly restore trust.

They have already adjusted.

They stopped suggesting improvements.

They stopped volunteering.

They stopped giving the organization the extra thought that once helped them notice problems early.

They learned to complete exactly what was requested, attach the required document, and protect themselves.

Management may call that disengagement.

The employee may call it pattern recognition.

You cannot repeatedly prove to people that initiative is useless and then repair the culture with a motivational email.

Hard Work Can Produce Pride

There is a reason people sometimes speak proudly about extremely difficult periods in their lives.

They built something.

They survived something.

They learned something.

They helped someone.

They became capable of something that once frightened them.

The difficulty became evidence.

I remember work that exhausted me but still left me satisfied because I could point to the outcome.

A struggling bank branch improved.

A property was repaired.

A customer found a solution.

A classroom gained tools.

A student developed confidence.

A system replaced a broken process.

The work was not easy.

Sometimes it was not remotely pleasant.

But the effort left proof behind.

Pointless work leaves a different memory.

You remember the meeting where everyone knew the solution and still chose another meeting.

You remember completing the report nobody read.

You remember explaining the customer’s problem to five departments while each department explained why it belonged to someone else.

You remember watching an obvious improvement die because the current process belonged to somebody important.

You remember being asked for your opinion and slowly realizing the question was ceremonial.

Difficult work can strengthen professional identity.

Pointless work erodes it.

One tells you:

“I can handle hard things.”

The other tells you:

“Nothing I do matters here.”

Busy Is Not the Same as Valuable

Some organizations have developed a strange emotional attachment to visible busyness.

A person typing quickly looks productive.

A full calendar looks important.

A long email looks thoughtful.

A thick report looks serious.

An employee who stays late appears committed.

Nobody asks why the system requires them to stay late.

Nobody asks whether the report could have been two pages.

Nobody asks whether six meetings could have been one decision.

Nobody asks whether the frantic activity exists because leadership keeps changing priorities without removing the old ones.

Busyness becomes camouflage.

It protects the organization from examining whether the work creates value.

This happens because activity is easier to measure than impact.

You can count calls.

Emails.

Tickets.

Meetings.

Forms.

Reports.

Hours.

Tasks completed.

Those numbers are not useless, but they can become dangerous when treated as the result.

A school can count how many devices were repaired.

It should also ask whether students received working devices quickly, whether recurring damage patterns were identified, and whether students performing the repairs became more capable.

A customer-service department can count how quickly calls ended.

It should also ask whether the customer’s problem was resolved or simply removed from that employee’s screen.

A business can measure how many leads were contacted.

It should also ask whether the contact was useful, relevant, and likely to build trust.

What is easy to count is not always what is worth improving.

When the metric becomes the mission, employees learn how to produce the number.

The number improves.

Reality develops trust issues.

Do Not Romanticize Overwork

This argument needs a warning label.

Meaningful work can still become too much.

Purpose can be exploited.

Some organizations take the dedication of good employees and use it as a substitute for adequate staffing, thoughtful management, and fair compensation.

“You care about the mission” becomes a polite way of saying:

“We expect you to absorb every failure in the system personally.”

No.

People have limits.

The World Health Organization defines burnout as an occupational phenomenon resulting from chronic workplace stress that has not been successfully managed. It is characterized by exhaustion, growing cynicism or mental distance from the job, and reduced professional efficacy. World Health Organization

Purpose does not cancel biology.

A meaningful eighty-hour week is still an eighty-hour week.

A teacher cannot permanently compensate for an entire broken system by caring harder.

A manager cannot remain available to everyone at every hour and call the eventual collapse a surprising development.

A small-business owner cannot continuously borrow energy from sleep, health, and family without receiving an invoice.

The point is not that people can survive unlimited hard work if leaders attach an inspirational mission statement to it.

The point is that the quality and meaning of work matter alongside the quantity.

Gallup has reported that how people experience their workload has a stronger relationship with burnout than hours alone, and that the quality of the work experience has roughly 2.5 to three times the influence of days or hours worked on overall wellbeing. Gallup

Workload matters.

So does whether the work feels fair, supported, useful, and possible to complete well.

We need both truths in the room.

People should not be protected from every demanding task.

They should not be sacrificed to badly designed work either.

Boring Does Not Mean Pointless

Employees also need to be honest.

A task is not pointless simply because you dislike it.

Some necessary work is repetitive.

Some important work is invisible.

Some responsibilities protect the organization from risks that do not appear until the responsibility is ignored.

Documentation may feel boring, but it can preserve information, support continuity, prove compliance, or prevent the next person from rebuilding the entire history from office folklore.

Quality checks can feel repetitive, but they catch mistakes.

Inventory can feel dull, but missing equipment becomes interesting very quickly when somebody needs it.

Following a procedure may feel slower than improvising, but sometimes the procedure exists because a previous improvisation ended with lawyers.

Before declaring a task pointless, ask:

Who uses this?

What decision does it support?

What risk does it prevent?

What would happen if we stopped?

Does it teach something necessary?

Does it connect one part of the organization to another?

Could the same result be produced more simply?

If there is a good answer, the task may be necessary even if it is not exciting.

Leaders should explain that answer.

Employees should be mature enough to hear it.

The problem begins when nobody can provide an answer beyond:

“Because that is the process.”

A process is not a religious text.

It can be questioned.

The People Closest to the Work Usually Know

The most accurate explanation of a pointless process rarely comes from the executive presentation.

It comes from the person doing it every day.

The clerk knows which information is entered twice.

The custodian knows which repair keeps returning.

The teacher knows which required documentation nobody uses.

The technician knows which approval delays a five-minute fix for three days.

The customer-service employee knows which policy causes the same angry conversation every afternoon.

The receptionist knows which instructions confuse almost everyone.

The person closest to the work sees where the official process and reality stopped speaking to each other.

That does not mean every employee suggestion is correct.

Frontline workers can see one part of the system and miss a requirement elsewhere. A step that looks pointless locally may protect another department, customer, legal obligation, or security standard.

That is why the conversation matters.

Do not dismiss the employee.

Do not automatically accept the complaint either.

Trace the process.

Show where the information goes.

Explain the constraint.

Ask what outcome the employee is trying to preserve.

Then redesign the work using both operational knowledge and organizational context.

That is leadership.

Not defending every process because changing it might imply that the original design was imperfect.

I have terrible news.

It was imperfect.

Everything humans build is imperfect.

That is why improvement exists.

Give People a Finish Line They Can See

One reason physical work can sometimes feel more satisfying than office work is that the finish line is visible.

The wall is painted.

The grass is cut.

The floor is installed.

The machine is repaired.

The room is clean.

Knowledge work often hides the finish line.

The employee sends the analysis and never learns what happened.

They make a recommendation and receive no response.

They complete one priority, only to discover that the priority changed three days earlier and nobody told them.

They solve a problem, but the organization continues measuring the outdated activity that existed before the solution.

People need feedback from reality.

What changed because of this work?

Who used it?

What improved?

What did we learn?

What happens next?

Leaders sometimes think employees want constant praise.

Most capable people do not need a parade every time they complete their responsibilities.

They need evidence that the responsibility mattered.

A short explanation can change how a task feels:

“This report helped us identify where the delays are occurring.”

“This documentation protected the customer when the case was reviewed.”

“This repair returned a device to a student who had been sharing one at home.”

“This follow-up prevented the account from being closed incorrectly.”

“The process you suggested saved the team nine hours this month.”

Now the effort has a destination.

Ownership Makes Difficult Work Lighter

People can tolerate more difficulty when they have some control over how the work gets done.

Ownership does not mean every employee makes every decision.

That would not be empowerment.

That would be organizational wilderness.

Ownership means people understand the result they are responsible for and have enough authority to make reasonable choices in pursuit of it.

Without ownership, employees become process operators.

Follow the steps.

Select the option.

Send the form.

Wait for approval.

Do not question the result.

When something unusual happens, forward it.

When the system fails, explain that the system failed.

When the customer becomes frustrated, remain professionally sympathetic while being structurally useless.

That is how capable people become passive.

They learn that judgment creates risk while compliance creates protection.

So they comply.

Then leadership complains that nobody takes initiative.

Initiative cannot survive indefinitely inside a system that punishes deviation and rewards visible obedience.

Give people guardrails.

Give them standards.

Give them clear boundaries.

Then give them enough room to solve the problem.

Responsibility without authority creates frustration.

Authority without responsibility creates chaos.

People need both.

Kill the Zombie Work

Every organization has zombie work.

The task died years ago.

Nobody told the calendar.

A report created for a former leader is still produced.

A meeting created during a temporary crisis has become a permanent weekly event.

An approval added after one mistake remains long after the original risk disappeared.

Information is collected because the form contains a field, and the form contains the field because the information has always been collected.

The work walks around consuming time while contributing nothing to the living.

Organizations should perform regular process funerals.

Ask every team:

Which task no longer serves its original purpose?

Which report is not used?

Which approval can be removed?

Which meeting can be shortened, combined, or eliminated?

Which information is entered more than once?

Which problem are we documenting instead of correcting?

Which rule protects a real standard, and which rule protects somebody from having to make a decision?

Which task could be automated without removing human judgment?

Which employee has developed a workaround because the official method does not function?

Then act.

Do not create a twelve-month initiative called Project Simplify that requires weekly progress reports, a steering committee, five approval levels, and a new software platform nobody requested.

Remove one useless thing.

Measure what happens.

Then remove another.

Improvement becomes believable when employees can point to a burden that no longer exists.

Employees Have a Responsibility Too

Pointless work is not an invitation to spend eight hours complaining about pointless work.

That only adds another unproductive process.

If something is broken, identify it clearly.

Do not say:

“This whole place is ridiculous.”

Say:

“We enter the same customer information into these two systems. It takes approximately four hours each week, and the second entry creates additional errors. Could we eliminate one entry or automate the transfer?”

Now there is a problem.

A cost.

A possible solution.

If a meeting is unnecessary, explain what decision it is failing to produce and suggest a better format.

If a report is unused, ask who reviews it and which decision depends on it.

If an approval creates a delay, identify the risk it is supposed to control and propose another way to control that risk.

Bring evidence.

Bring options.

Bring enough understanding to distinguish a broken process from a responsibility you simply do not enjoy.

Then accept that the organization may not change immediately.

Some constraints are real.

Some improvements require money.

Some rules come from outside the department.

Some risks are invisible until the rule is removed.

Some leaders will say no for a legitimate reason.

Others will say no because changing the process would require them to admit you have a point.

You cannot control every answer.

You can make the problem harder to ignore.

The Pointless-Work Test

Before continuing a recurring task, ask six questions:

1. What outcome does this create?

If nobody can identify the outcome, the task may have become detached from its purpose.

2. Who uses what we produce?

Name the person, team, customer, or decision. “The organization” is not a person.

3. What happens if we stop?

A real consequence suggests the work matters. “Someone may ask why we stopped” is not the same as a real consequence.

4. Are we solving the problem or recording its existence?

Documentation can support a solution. It should not become the solution’s permanent replacement.

5. Could the same result be achieved with less friction?

Necessary work can still be badly designed.

6. Does the person doing the work have enough information and authority to improve it?

If not, the organization may be paying for human judgment while designing a job that forbids its use.

Not every task will survive those questions.

Good.

A process should not receive permanent employment merely because it existed before the current staff arrived.

Make Hard Work Worth Carrying

The best workplaces are not necessarily easy.

They may be demanding.

Standards may be high.

Deadlines may be real.

Customers may be complicated.

Mistakes may matter.

People may leave tired.

But they also leave knowing what their effort accomplished.

They can see progress.

They understand the purpose.

They have some ownership.

Their judgment is respected.

Problems are allowed to be named.

Waste is allowed to be removed.

The work asks something from them and gives something back:

Skill.

Pride.

Evidence.

Trust.

Growth.

A result.

That exchange is what pointless work breaks.

It continues taking energy after it has stopped returning value.

Eventually, even hardworking people begin protecting themselves.

They stop caring before the organization stops paying them.

They remain present without being fully available.

They complete the procedure and withdraw the judgment.

Their hands still perform the work.

Their mind has quietly left the building.

That is the real cost.

People can survive hard work longer than pointless work because hard work can lead somewhere.

It can build a room.

Repair a machine.

Teach a student.

Help a customer.

Strengthen a team.

Save time.

Create proof.

Pointless work only asks people to keep moving without getting closer.

Do not make work easier merely so nobody feels challenged.

Make it clearer.

Make it useful.

Make the result visible.

Remove the difficulty that exists only because nobody has questioned it.

Keep the difficulty that develops skill, protects quality, serves people, and creates something worth having.

People can carry weight.

What crushes them is carrying it in circles.