Intro: Turn Workplace Trouble Into a Log, Not Just a Memory
When something bad happens at work, the first thing that sticks is the feeling.
"That was brutal."
"That wasn't fair."
"I was scared."
"They moved the goalposts on me again."
"It feels like I'm the only one getting the blame."
Those feelings matter.
But when you talk to someone else about it, feelings alone can be hard to get across.
To explain it to a hotline, your manager, HR, or an outside advisor, you need to lay out:
- When it happened
- Where it happened
- Who was involved
- What they actually said
- What led up to it
- What you did
- What happened afterward
- Whether the same thing has happened before
That's where logging workplace trouble comes in.
Logging doesn't mean just writing "that was awful."
It means putting events in order by date and time, and keeping the exact words, your own response, the impact on your work, and the points that could be a problem, each recorded separately.
A Log Shows You Weren't Doing Nothing
When you get hammered at work, it's easy to feel like it was your fault.
"Should I have started sooner?"
"Did I just not understand it well enough?"
"Was it how I reported things?"
"Did I lack initiative?"
But once you write it all down, you often find you actually did quite a lot.
For example, in one workplace case, generalized here, the log showed things like these:
- Preparing materials in advance
- Submitting a draft before the deadline
- Asking coworkers to check the work
- Asking for direction
- Making the requested fixes
- Offering alternative proposals
- Trying to confirm the scope of the job and the criteria for decisions
- Trying to keep a record in chat or documents instead of relying on spoken words alone
- Covering for other people's delays so the deadline still got met
Seen this way, the problem isn't simply "this person did nothing."
What you may see instead is this:
They were doing their part, but the decision criteria, division of roles, what counts as "good enough," and who was responsible were all vague, so changes kept coming after the fact and blame got passed around.
A Log Shows a Pattern, Not Just One Bad Remark
If someone spoke harshly to you once, it can be hard to judge what it meant.
It could have been a busy moment, a mix-up in tone, or even legitimate coaching on the job.
But when you line your records up by date, a pattern can show up that a single incident never would.
For example, patterns like these:
- You act on your own judgment and get told, "Don't just do things on your own."
- You ask a question and get told, "Think for yourself."
- They want an explanation out loud, but get annoyed when you try to put it in writing in chat.
- You propose an idea up front, and later hear, "That's not what I meant."
- You end up redoing the same thing over and over in tiny ways.
- Your first draft gets rejected outright.
- The scope of your job keeps growing after the fact.
- You have no authority, yet you're stuck with all the responsibility for the result.
- They demand "initiative," then shoot down the ideas you take the initiative to bring.
- They say they want to reduce work that only one person can do, yet never set aside time or name anyone to build the standard process.
If this keeps happening, it's worth looking at it as how the workplace is run, not as an isolated comment.
In this article, I call this structure the initiative double bind.
In short:
They demand initiative, but never create the conditions that let initiative happen.
If you think and act on your own, you get shut down. If you check first, you're told you lack initiative.
This kind of structure is hard to fix through sheer personal effort.
A Log Lets You Sort Out the Problems
When it's all just emotion, it tends to end at "that was awful" or "that was rough."
Once it's in a log, though, you can sort the problems into categories.
For example:
- Attacks on your character
- Scolding in front of others
- An intimidating tone
- Excessive demands
- Instructions that change after the fact
- Blame shifted onto you
- Unclear decision criteria
- Responsibility without authority
- An atmosphere where it's hard to ask for help
- Verbal-only instructions that make records hard to keep
- Endless redoing of the same work
- The initiative double bind
- Quietly absorbing work that only one person knows how to do
- Shooting down improvement ideas, then complaining that nothing is improving
Once you can sort it, it's easier to explain to someone else.
Instead of "I don't like my boss," you can say:
"The standards for instructions are never clear, changes keep coming after the fact, and even when I ask or check, I'm rated as lacking initiative, which puts a heavy mental strain on me while I do my job."
Use the Ministry of Health, Labour and Welfare's Definition as a Reference
In Japan, the Ministry of Health, Labour and Welfare (the government body in charge of labor issues) lays out three elements for workplace power harassment:
- Words or actions that rely on a power imbalance in the relationship
- Going beyond what is necessary and appropriate for the job
- Harming the employee's working environment
It also lists typical types: physical attacks, psychological attacks, being cut off from relationships at work, excessive demands, too-small demands, and invasion of privacy.
That said, whether any specific incident counts as power harassment is ultimately decided by looking at the whole situation.
So in an article or a log, rather than declaring "this is definitely power harassment," it's safer to keep it as
an organized set of facts you can use to ask whether it might count as power harassment.
What Logging Did for Me
Logging workplace trouble has these benefits.
1. You capture it before your memory gets fuzzy
As time passes, what was said and the order of events blur together.
With a log, you can go back and check.
2. Your own actions get recorded too
You can record not only what the other person said, but what you did.
That lowers the risk of being seen as someone who "did nothing" or "didn't report."
3. Changes after the fact become visible
Once it's in order by date, you can see whether the conditions changed later or were set that way from the start.
4. You can see whether it keeps happening
You can tell if it was a one-off or a repeat.
5. It's easier to ask for help
When you explain things to someone else, you can show them a record instead of just your feelings.
6. It sorts out your own thinking
Instead of "Is it me or is it them?", you can separate things out:
- This part is something I can improve
- This part is about how the other person speaks
- This part is a problem with the company's system
- This part is a problem because the decision criteria were never defined
Wrap-Up: Logging Is for Protecting Yourself, Not Attacking Anyone
The point of logging workplace trouble isn't to attack the other person.
The point is to record your condition and what happened accurately, so you can take it to someone for advice.
The painful memories matter.
But memory alone can be hard to explain.
So keep a record of:
- The actual words said
- The order of events
- What you did in response
- The impact on your work
- What could count as a problem
- Whether something similar has happened before
Logging doesn't erase your feelings.
If anything, it lets you sort out the facts in order to protect those feelings.
Don't carry workplace trouble around in your memory alone.
Write it down.
Put it in order.
Record what you did, too.
Look for the pattern.
Reach out for advice if you need to.
That's the first step toward protecting yourself.
