The short version
What wears people down at work isn't just "too much to do."
What really fries your brain is an environment like this:
- Someone says "that's not what I meant" after you've already done the work
- The requirements change depending on someone's mood
- You get the blame without any of the authority
- Main-line phone calls and interruptions keep breaking your focus
- You're told to run with no clear decision-maker, deadline, priority, or definition of "done"
That isn't a job that's hard. That's a job whose rules are broken.
It's more accurate to see this as a design failure in cognitive load, role ambiguity, interruptions, and workplace stress, not as a lack of grit or proof that you're "not cut out for office work."
It's not the workload. It's the unpredictability.
If the problem is just a big pile of work, there are things you can do.
Break it down. Rank it. Hand some off. Push a deadline. Make templates. Automate.
What's nasty isn't the volume. It's that the ground keeps shifting under you.
What was fine yesterday is wrong today.
You followed the conditions you were first given, and afterwards someone says, "that's not what I meant."
You can't tell who actually makes the call.
You have no authority, yet somehow the blame for failure lands on you.
Once that happens, work stops being a game of producing something.
It becomes a game of reading someone's mood.
And a mood is not a spec sheet.
That's why it's exhausting.
Burnout comes from chronic workplace stress that nobody manages
The WHO treats burnout in the ICD-11 as an "occupational phenomenon." It isn't a medical condition in itself, but it's described as a syndrome resulting from chronic workplace stress that has not been successfully managed.
The WHO lists three main features:
- Feelings of energy depletion or exhaustion
- Increased mental distance from your job, or feelings of negativity or cynicism about it
- Reduced professional efficacy
In other words, burnout isn't "weak people breaking." It's a pretty natural reaction when chronic workplace stress goes unmanaged for a long time.
Reference: WHO "Burn-out an occupational phenomenon: International Classification of Diseases"
https://www.who.int/news/item/28-05-2019-burn-out-an-occupational-phenomenon-international-classification-of-diseases
What the research says: high demands plus few resources is the danger zone
One well-known way to explain workplace stress is the Job Demands-Resources model, or JD-R model.
Roughly speaking, a job has two kinds of ingredients.
The first is job demands.
These are the things that use up your energy: heavy volume, mental strain, emotional strain, friction with people, deadlines, responsibility, vague changes.
The second is job resources.
These are the things that lower the load or help you move forward: autonomy, support from your boss and coworkers, clear feedback, clear roles, and the tools and information you need to get the job done.
The JD-R model says that when demands stay high and resources fall short, your energy gets drained and burnout becomes more likely.
The important point is that volume isn't the only problem.
Even with high demands, you can hold up if you have autonomy, support, clear priorities, a clear decision-maker, and requirements that stay put.
On the other hand, even a moderate workload wears you down if there are no resources.
For example, a situation like this:
- The goal is vague
- The decision-maker is vague
- The deadline is vague
- The definition of "done" is vague
- The scope of your responsibility is vague
- But if you fail, you get yelled at
- And the requirements change halfway through
That's a state where demands are high and resources are short.
Reference: Schaufeli, W. B. "Applying the Job Demands-Resources model: A 'how to' guide to measuring and tackling work engagement and burnout"
https://www.wilmarschaufeli.nl/publications/Schaufeli/476.pdf
"That's not what I meant" is usually a bad spec, not a reading-comprehension problem
When someone says "that's not what I meant" after the fact, the person who got the instruction tends to doubt their own understanding.
But if it happens every time, the problem is probably not the receiver. It's more likely that the instructions were vague to begin with.
What you actually need for a job is information like this:
- What are we making?
- Why are we making it?
- Who decides?
- When is it needed?
- How detailed does it need to be?
- What doesn't need to be done?
- If something changes, from what point does it count as a change to the requirements?
Without any of that, you're told "just do it."
Then afterwards you're told "that's not what I meant."
This isn't only a question of how well the receiver understood.
It's closer to making a developer build software with no spec, then complaining after delivery that it doesn't match the spec.
Of course, the receiver should also make an effort to double-check.
But in an environment where the requirements move even after you've checked, checking harder only goes so far.
When the rules shift with someone's mood, you can't build up learning
In a workplace where requirements change with someone's mood, raising the quality of your work doesn't win.
That's because the evaluation criteria never stay fixed.
Yesterday you were told, "You don't need to be that detailed."
Today you're asked, "Why didn't you check that more carefully?"
Yesterday it was, "Get it to me fast."
Today it's, "This is too sloppy."
Yesterday it was, "Think for yourself."
Today it's, "Don't just go ahead on your own."
If this keeps up, people lose the ability to learn how to do the job.
In an environment where learning works, input and results are linked to some degree.
Do it this way and it gets approved.
This much is enough.
This person looks at this angle.
For this deadline, this level of detail is fine.
Patterns like these build up.
But in a mood-driven environment, the rules change like the weather.
As a result, even though you're working, what you're really doing isn't the work. It's a game of predicting someone's mood.
That's seriously draining.
"Getting only the blame" is a role ambiguity and role conflict problem
Workplace stress research has concepts called role ambiguity and role conflict.
Role ambiguity is a state where it's unclear what you're supposed to do, how far it goes, and what's expected of you.
Role conflict is a state where you get contradictory expectations from several people or positions.
For example, Manager A says "get it out fast."
Manager B says "raise the quality."
The people on the floor say "don't over-check."
And afterwards the person in charge says, "Why didn't you check?"
That's role conflict.
On top of that, when you're held responsible without having decision-making power, you can't control your own work.
Carrying the blame for things you can't control is extremely draining.
A meta-analysis (a study that pools the results of many studies) also found a significant link between role ambiguity and role conflict on one hand and depression on the other, and the researchers note that clarifying roles and job goals may contribute to employee health.
Reference: Schmidt et al. "Uncertainty in the workplace: Examining role ambiguity and role conflict, and their link to depression—a meta-analysis"
https://www.researchgate.net/publication/254223120_Uncertainty_in_the_workplace_Examining_role_ambiguity_and_role_conflict_and_their_link_to_depression-A_meta-analysis
Main-line calls and interruptions aren't just pauses. They carry a "restart cost."
A call to the company's main line or a sudden request can look like it takes just a few minutes.
But in knowledge work, the bigger cost isn't the interruption itself. It's the cost of getting back to what you were doing.
The assumptions you were holding, where your documents were, the sentence you were about to write, the point you were weighing, the options you were comparing.
All of that sits on the workbench in your head.
Then the phone rings.
You deal with something else.
You come back.
And the workbench has collapsed.
You have to remember everything all over again.
When this restart happens over and over, you're working the whole time and yet nothing gets finished.
Research on interruptions also reports that when people are interrupted, they try to make up for it by working faster, but their stress, frustration, time pressure, and sense of effort go up.
In other words, in a workplace with lots of interruptions, your internal fuel economy is worse than it looks from outside.
Reference: Mark, Gudith, Klocke "The Cost of Interrupted Work: More Speed and Stress"
https://ics.uci.edu/~gmark/chi08-mark.pdf
NIOSH's workplace stress questionnaire includes "role ambiguity" and "role conflict" too
NIOSH, the US National Institute for Occupational Safety and Health, publishes the Generic Job Stress Questionnaire for measuring workplace stress.
Alongside workload, mental demands, autonomy, conflict with others, support, and job insecurity, it also includes role ambiguity and role conflict.
So problems like "my responsibilities are unclear," "the expectations contradict each other," and "my authority doesn't match my responsibility" aren't just venting. They're factors that are routinely measured when thinking about workplace stress.
Reference: NIOSH "Generic Job Stress Questionnaire"
https://archive.cdc.gov/www_cdc_gov/niosh/topics/workorg/detail088.html
NIOSH also explains that exposure to chronic job stress worsens mental health, and that we need to address the root causes in the organization, its management policies, and how work is done, not just individual stress tolerance.
Reference: NIOSH "Supporting Mental Health in the Workplace"
https://www.cdc.gov/niosh/bulletin/2024/mental-health-work.html
Conscientious people end up repairing the broken spec in their own heads
The people who burn out in workplaces like this aren't necessarily the less capable ones.
If anything, the ones who take it seriously at first are the ones who get worn down.
- Even when instructions are vague, they fill in the blanks themselves
- If nobody else will do it, they pick it up
- Even when responsibility is vague, they try not to drop anything
- They read people's moods and act ahead of time
- They double-check extra so they won't get yelled at later
- They sort out in their own heads things that the people above should have decided
At a glance, that looks capable and responsible.
But if it goes on, you end up paying the repair cost of a broken workplace design with your own brain.
Rules, decision criteria, priorities, and lines of responsibility are things an organization should provide.
You're covering for them with your personal working memory.
That doesn't last long.
And the people who survive aren't "tough." They know how not to absorb it.
Some people seem fine in a broken environment.
They don't necessarily have stronger brains.
They often have skills like these:
- They hand in 60% work and don't worry about getting scolded
- They don't soak responsibility into themselves
- They hand vague instructions back as vague
- They toss things back upward
- They keep records
- They treat other people's moods like the weather
- They don't try to define everything themselves
- They keep their expectations low
That's less about bad character and more about survival skills.
Of course, brushing everything off carelessly isn't the answer either.
But if you take every broken spec in good faith, you turn into a consumable.
Fix 1: Lock in verbal instructions with "Here's how I understand it"
When you get a vague instruction, don't fill in the gaps in your head and run.
Put it in writing once and send it back.
Example:
Here's my understanding.
Purpose: X
Deadline: month X, day X
In scope this time: A and B
Not in scope this time: C
Person to confirm with: Mr./Ms. X
I'll proceed on this basis.
The point isn't to corner the other person.
It's to avoid carrying the vagueness only in your own head.
Once it's in writing, the vagueness becomes visible to the other side too.
Fix 2: Treat after-the-fact changes as "a change in requirements"
When the premise changes later, don't take it on as your own mistake.
Think of it like this:
The premise changed, so from here on this is a change in requirements.
You can say it gently.
Understood. I'll revise it to the X version, on the understanding that the premise has changed.
That will take about X hours more than originally planned.
What matters here is not absorbing the late change for free.
A change in premise costs time, effort, and a reshuffling of priorities.
Make that visible.
Fix 3: Let the other person choose the priority
When you're told to do everything, don't take it all on yourself.
If I work on A, B, and C at the same time, only A will be done today.
If you want B first, A will slip to tomorrow.
Which would you like me to prioritize?
This isn't defiance.
You're just showing the real-world constraints.
If you decide priorities all by yourself, you get stuck with the blame later.
So let the decision-maker choose.
Fix 4: Ask where responsibility ends
If you tend to end up absorbing the blame, ask about the boundaries at the start.
Who makes the final decision on this?
Is my part done once the materials are prepared?
Or does it also include collecting responses from and chasing the people involved?
After I submit this, is it right that the decision is made on Mr./Ms. X's side?
The more vague the responsibility in a job, the more likely you are to hear "why didn't you do it?" later.
So draw the line in advance.
Fix 5: Leave a one-line note so you can get back after an interruption
If you can't get interruptions down to zero, lower the cost of getting back.
When the phone rings, when you step away, when you move on to something else, leave just one line in the file you're working on or in your notes.
Next: check company A's data from line 3. Look at the amount gap in column B.
Next: reply to the email. The point is whether the deadline can be extended. The attachment is the latest, v3.
Next: resume from "Decisions" in the meeting minutes. Unconfirmed items are waiting on Tanaka's reply.
It's small, but it works quite well.
You don't have to start from "What was I doing?" after an interruption.
Fix 6: Treat other people's moods as "weather," not as a "spec"
If you try to read someone's mood perfectly, you'll break.
A mood is closer to the weather.
There's no point blaming yourself on a rainy day by asking why it rained.
There are people in a bad mood.
Today is a hard day to get things through.
So keep a record, don't get drawn in, and get through with the bare minimum.
Don't try to read someone's mood as if it were a spec sheet.
What can't be read can't be read.
Fix 7: Quitting, transferring, or changing jobs isn't losing. It's a design change.
In an environment that's truly broken, individual workarounds only go so far.
In that case, a transfer, a job change, or a change of duties isn't a defeat.
It's a design change.
You're not "running away because you're weak."
You're simply judging that "in this environment, what I get back is too small for the energy I put in."
In investment terms, it's close to cutting your losses.
Cutting losses isn't losing.
It's a technique for protecting your capital.
Work is the same. Your health, focus, judgment, and stable life are your principal.
You don't have to wear down your principal just to put up with a broken spec.
A good workplace isn't an "easy" one. It's one where "the rules are visible."
A good workplace isn't one with little work.
Some workplaces hold up even when they're busy.
What they share is that the rules are visible.
- You know the purpose
- You know who decides
- You know the priorities
- You know what "done" looks like
- Authority and responsibility roughly match
- Changes in premise are treated as changes
- Interruptions are controlled
- You can ask for help when you're stuck
- What's been decided is recorded
In an environment like that, people can handle being somewhat busy.
On the other hand, even a slow workplace wears you down if it runs on moods, after-the-fact changes, and no lines of responsibility.
Wrap-up: It's not that the work is impossible. It's that taking a broken job design at face value is impossible.
Sometimes you worry, "Am I just not suited to office work?"
But that's not necessarily the case.
What you're not suited to may not be office work in general, but an environment like this:
- A catch-all "do whatever comes up" role with nothing defined
- Instructions that are almost all verbal
- Judgment after the fact
- Requirements that change with someone's mood
- No lines of responsibility
- Interruptions as the norm
- No records kept
- Unclear decision-makers
That isn't knowledge work. It's a war of attrition wearing knowledge work's clothes.
So it's natural to feel worn out.
What you need to do isn't only to get tougher.
Don't carry vagueness only in your own head.
Put the requirements in writing.
Treat after-the-fact changes as changes in requirements.
Draw the lines of responsibility.
Make it possible to get back after an interruption.
Treat other people's moods as weather.
And if the environment really won't change, change the design by transferring or changing jobs.
People who burn out at work aren't weak.
They burn out because conscientious people keep repairing a broken job design with their own brains.
So what you need isn't grit. It's boundaries.
Short templates you can use at work
Lock in the instructions
Here's my understanding.
Purpose:
Deadline:
Scope this time:
Out of scope:
Person to confirm with:
I'll proceed on this basis.
Turn a late change into a change in requirements
Understood. I'll revise it on the understanding that the premise has changed.
That will take about X more hours.
Let them choose the priority
If I work on A and B at the same time, only A can be done today.
If you want B first, A will slip to tomorrow.
Which would you like me to prioritize?
Draw the line of responsibility
Is my part done up to X?
Is it right that the final decision is Mr./Ms. X's?
A note for getting back after an interruption
Where to pick up:
Unconfirmed:
Next step:
Candidate internal links
- A life at 28 that looks like a "dead game" can be rebuilt with risk hedging, not giving up
- What is white-collar stamina? Not muscle, but the skill of protecting your brain's memory
- How to set "lines of responsibility" so work doesn't wear you down
- How to treat after-the-fact instructions as changes in requirements
- Why main-line calls and interruptions wreck your focus
Ideas for related articles
- A confirmation template so you don't get worn down in a workplace that says "that's not what I meant" afterward
- Five questions to ask first if you're the one who keeps absorbing the blame
- In a workplace where requirements change with moods, too much sincerity makes you a consumable
- You're not unsuited to office work. You're just unsuited to the catch-all "do whatever comes up" role
- A one-line-note technique to protect your brain's memory in a workplace full of interruptions
Notes for overseas rollout
For English-speaking readers, these angles are easier to run with.
- "It's not workload. It's unpredictability."
- "When requirements change with someone's mood, burnout is not your personal failure."
- "Role ambiguity is not a vibe problem; it is a workplace stressor."
- "Interruptions are not small. They create cognitive restart costs."
Related keywords:
- burnout
- role ambiguity
- role conflict
- job demands-resources model
- workplace interruptions
- cognitive load
- emotional labor
- toxic workplace
Points to watch when publishing
- Don't include anything that could identify a person, department, company, or time period
- Lean toward the general point that "the job design is broken" rather than "the boss is bad"
- Avoid medical claims. Keep it to something like "burnout is described as an occupational phenomenon"
- Structure it so readers can diagnose their own workplace, not around a specific grudge
- If publishing while job hunting, blur the examples across several industries to avoid pointing to your current employer
