Intro: The people who preach it are the ones who give the least status back
There's a phrase you hear all the time in Japanese workplaces: "horenso."
Report.
Inform.
Consult.
It's usually presented as the most basic skill of a working adult.
But in real workplaces, something strange happens.
The people who lecture loudest about horenso are often the ones who don't do it themselves.
They tell their staff, "Report to me," "Consult me," "Show some initiative."
But when it comes to the approval route they control, reporting up to their own superiors, returning an OK or NG, or sharing a "done" status, they don't do any of it.
So the person under them ends up here:
I made it
I fixed it
I shared it with everyone involved
I wrote down how we'd proceed
I sent the deadline and the completion notice
Other departments liked it too
But my boss won't move the approval route
Won't give me an OK or NG
Won't report the result upward
I don't even know if it was actually used
And in the end, the higher-up comes back to ME asking "so what happened?"
This is not a failure of the subordinate to report, inform and consult.
It's the opposite.
The subordinate is being forced to manage the boss's missing reports instead.
In this article, I'll call this reverse management.
Reverse management is a situation where a manager doesn't do the approving, reporting, deciding and status-returning that managers are supposed to do, so the subordinate has to manage even the manager's gaps and omissions.
This isn't initiative on the subordinate's part.
It's just an organizational cost.
1. Some people see horenso as a ritual of asking the boss's permission
People who only understand horenso on the surface tend to think like this:
Report = get the boss's approval
Inform = pass something along
Consult = ask "Which is better, A or B?"
That isn't wrong.
But it only scratches the surface.
If that's all you understand, horenso turns into a custom of "subordinates asking the boss for permission."
The subordinate reports to the boss.
The subordinate informs the boss.
The subordinate consults the boss.
In other words, horenso becomes a one-way street.
But in actual work, that isn't enough.
Real horenso isn't a ritual of rank. It's status management that keeps work from stalling.
2. What horenso really is: a way to make the state of work visible
Put in practical terms, it looks like this.
Reporting
Reporting doesn't just mean getting your boss's approval.
Reporting means making the state of the work visible.
Is it done?
Is it not done?
Where is it stuck?
Who is it waiting on?
What happens next?
Is there a problem?
Is there no problem?
Reporting is making all of this clear to the people involved.
Informing
Informing doesn't just mean passing on a message.
Informing means getting everyone involved on the same page.
Who is in charge?
By when will it be done?
Through which route will it be checked?
Which version is the latest?
What counts as "done"?
Who needs to confirm it?
Informing is making sure none of this drifts out of sync.
Consulting
Consulting doesn't mean dumping "A or B?" in your boss's lap.
Consulting means laying out the information needed for a decision so the decision can move forward.
Option A
Option B
The risks of each
The deadline
The scope of impact
Your own recommendation
What you need decided
Bringing it all the way to this point, so the decision can advance, is what consulting is.
So horenso is not a ritual for avoiding your boss's anger.
It is information infrastructure for keeping work moving.
3. There is also horenso from boss to subordinate
When people say horenso, they tend to think only of subordinate to boss.
But in practice, horenso from boss to subordinate matters just as much.
If the boss holds the approval route, the boss has information that needs to go back to the subordinate.
Did you show it to the higher-ups?
Was it approved?
Was it sent back?
Is it OK?
Is it NG?
Was it used for real?
Is it still on hold?
Are there further changes?
Can we treat it as done?
If this isn't returned, the subordinate can't move.
No matter how much the subordinate finishes, if the boss doesn't return the status, that piece of work is left hanging in midair.
In other words, a boss's horenso means returning status to the subordinate.
In a workplace without that, the subordinate is always stuck like this:
It should be finished, but I can't tell if it's complete
I fixed it, but I can't tell if it's OK
I shared it, but I can't tell if anyone saw it
It's waiting for approval, but I can't tell who's holding it
I can't tell if it was used for real
I can't tell if the result has reached the top
This is not the subordinate failing at horenso.
It's the boss failing to return status.
4. The video for high schools: the work was done, but it stalled on the approval route
Here's an example: a video project for high schools.
The deadline was June 2.
The video was already finished as of May 29.
The boss had remarked that "the set looks dark," and that was fixed on May 29 as well.
Other departments had also reacted warmly, with plenty of "nice" and "nice."
So the deliverable had taken shape well ahead of time.
On top of that, the approval route had been sorted out in a meeting.
Boss → Senior Managing Director
The check would go through this route.
People from other departments attended the meeting, and the boss was there too.
No one objected on the spot.
It was also shared in writing on Teams (Microsoft's workplace chat tool) as a settled matter.
The deadline for revisions and the notice of completion were also sent in writing to everyone involved.
If someone has done all that, they've done plenty of horenso on their side.
The problem is what came after.
I don't know whether the boss showed it to the Senior Managing Director
I don't know whether it was actually aired or used
I don't know whether it's OK or NG
I don't know whether there are further changes
I don't know whether it counts as done
Then on June 9, the Senior Managing Director asked the person who made it something like:
"What happened with that video? Oh, it already went out, huh. Show it to me again sometime."
That's pretty strange.
The person who made it had finished.
They'd made the fixes.
They'd shared it with everyone involved.
They'd even left the approval route in writing.
And yet the status of sharing and approval with the higher-ups stayed unclear, and in the end the question came back to the person who made it.
This isn't the maker's problem.
It's a problem of the person who holds the approval route not returning status.
5. If the same thing happens on a president's project, it's a recurring pattern
If this happened only once, it might just be a one-off slip in communication.
But if the same thing happens on another project, this one for the company president, the story changes.
The worker finishes the job
The boss grabs it partway through
Doesn't return approval, sharing, or next actions
The higher-up asks the worker "so what happened?"
It looks as if the worker was the one who stalled it
If this keeps repeating, it isn't a single accident.
The boss has stepped in between the deliverable and the higher-ups and become a bottleneck that stops the flow.
A manager is supposed to be the person who removes bottlenecks.
But this type of boss does the opposite.
Doesn't set up an approval route
Doesn't report results upward
Doesn't return OK/NG
Doesn't return a completion status
But does make nitpicky comments
With this, a subordinate has no way of producing results.
Even if they finish the work, it never reaches the top as a result.
6. Some people only make trivial comments and never move the real thing forward
Even more troublesome is the type who doesn't manage the main line of work but does make small remarks.
Say, for example, that on an urgent document you typed "1,800" into a field labeled "unit price" or "hourly wage."
In context, anyone would read that as 1,800 yen per hour.
It can't be 1,800 yen a day.
And it certainly isn't 1,800 yen a month.
Of course, there's nothing wrong with clarifying the notation precisely.
But then the boss says something like:
"I'm just pointing this out, but is that hourly? Or daily?"
and holds up the urgent document.
That is less a check than an itch to use the red pen.
A check that actually moves the work forward would just end with:
I'll process it as 1,800 yen per hour
I'll change only the notation to "1,800 yen per hour" and proceed
So the problem isn't the comment itself.
The problem is stopping work over comments barely worth stopping for, while not doing the approval, reporting and status-returning that are really needed.
That is the worst combination.
Hands down trivial comments to the people below
Doesn't report results to the people above
Doesn't return OK/NG
Doesn't say whether it was used for real
Yet lectures subordinates about horenso
At this point, the manager's added value is negative.
7. A real manager is someone who makes it easy for subordinates to work
What a real boss or manager should be doing is actually quite clear.
Decide the approval route
Report results upward
Return OK/NG
Remove bottlenecks
Make it easy for subordinates to work
That is a manager's job.
Take what the subordinate made and get it to the people who need it.
If a decision is needed, pass it to the decision maker.
Bring the higher-ups' reactions back to the subordinate.
If revisions are needed, send them back with specifics.
If no revisions are needed, mark it as done.
If something is stuck, make it visible where it's stuck.
When this happens, subordinates can move easily.
When it doesn't, they can't.
No approval route
No reporting upward
No OK/NG
Even when NG does come, it's trivial
Creates bottlenecks
Subordinates have a hard time moving
Being told to "show initiative" in this state is hard to take.
The boss is clogging the spot where a subordinate's initiative can't do anything.
8. This isn't "a lack of initiative," it's "a lack of process design"
The word "initiative" is also used carelessly in workplaces.
Real initiative doesn't mean shouldering everything that's been dumped on you through sheer willpower.
Real initiative means reading the situation, putting out the information that's needed, getting everyone involved on the same page, and moving the next action forward.
In a case like this one, the worker has already been acting on their own initiative.
Made it ahead of the deadline
Fixed the points raised
Shared it with other departments
Got their reactions
Organized how to proceed
Proposed an approval route
Left it on Teams as a settled matter
Shared the revision deadline
Sent the completion notice to everyone involved
If someone has done all of this, they have plenty of initiative.
If things still stall, the cause isn't a lack of initiative on the subordinate's part.
The approver doesn't move
Confirmation from the higher-ups doesn't come back
OK/NG doesn't come back
The completion status doesn't come back
It's a problem of process design.
If you swap that out and call it "the subordinate's horenso" or "the subordinate's initiative," the real problem becomes invisible.
9. What is reverse management?
Reverse management is a state in which a manager isn't doing the management they should be doing, so the subordinate manages the manager's gaps.
For example, it looks like this:
The boss doesn't decide the approval route
↓
The subordinate proposes an approval route
The boss doesn't report upward
↓
The subordinate posts a log of results for everyone
The boss doesn't return OK/NG
↓
The subordinate asks, "If there are no changes, may we treat this as done?"
The boss doesn't return status
↓
The subordinate lays out the outstanding items on Teams
The boss becomes a bottleneck
↓
The subordinate records that things are stuck at the bottleneck
At a glance, this can look like a solid, reliable subordinate.
In reality, it's pretty exhausting.
On top of their actual work, the subordinate is also patching up the boss's management failures.
In this article I'll call this the reverse management tax.
As the reverse management tax grows, a subordinate has to produce not only deliverables but also a defensive paper trail in case the boss drops something.
That is not work done to produce results. It's extra work done to protect results.
10. In workplaces with reverse management, results don't reach the top
In workplaces with reverse management, a subordinate's results have trouble reaching the top.
That's because the boss doesn't report those results upward.
From the subordinate's point of view, it goes like this:
The workload grows
Work stalls over trivial comments
You make the fixes
You finish the job
But the result never reaches the top
The higher-up comes asking "so what happened?"
It's hard for any of it to feed into your evaluation
This is a pure loss.
A boss is supposed to be the one who carries a subordinate's results upward.
Show what the subordinate made to the higher-ups.
Take in the higher-ups' reaction.
If it's good, report it as a result.
If revisions are needed, send them back with specifics.
If this works, the subordinate's work becomes an accomplishment.
But if it's jammed here, the subordinate's work ends at "they just made it."
The deliverable exists.
But no result gets reported.
So it doesn't show up as a result.
That is quite a serious problem.
11. Traits of the bottleneck boss
Once you've laid it all out this far, the traits of a bottleneck boss become visible.
Doesn't decide the approval route
Doesn't follow the route even once it's decided
Doesn't report results upward
Doesn't return OK/NG
Doesn't return a completion status
Doesn't share whether it was used for real
Doesn't say whether there's more feedback
But does weigh in on fine points of notation
Stops urgent work over unimportant comments
Doesn't realize they're the one stopping it
Demands horenso and initiative from subordinates
For a manager, this is quite dangerous.
It makes a subordinate's results vanish.
The deliverable is done.
The fixes are made.
It's been shared with everyone involved.
But the boss doesn't carry the result upward.
Doesn't return the status.
As a result, the subordinate is permanently stuck in a state of "I did it, but it isn't over."
If this continues, the harder a subordinate tries to produce results, the more worn out they get.
12. Countermeasure 1: Put completions, fixes and open items in writing
In a workplace like this, moving things forward by word of mouth alone is risky.
Always leave it in writing.
These four things are especially worth recording:
What has been completed
What has been fixed
Who it has been shared with
Who the open items are waiting on
For example, you could write something like this:
This item was completed as of 5/29.
The point you raised, that the set looks dark, was also fixed the same day.
The revised content has been shared with everyone involved.
The only remaining item is confirmation by the higher-ups along the agreed route.
Please let me know if you'd like any further changes.
This makes the worker's scope of responsibility much clearer.
The key is not to say only "I'm done."
What is complete
What was fixed
Who it was shared with
What remains
Who the remaining item is waiting on
Write all of that down.
That way, even if the boss stalls it, it's harder for it to look like "the worker stalled it."
13. Countermeasure 2: Don't say "stuck at the monkey," make it visible as "waiting on the higher-ups' confirmation"
Emotionally, you may want to say "it's stuck at the monkey" (a venting nickname for the bottleneck boss).
But when you put it out to others, reword it like this:
Waiting on confirmation from the higher-ups
Waiting on approval
Waiting on status from the approval route
Waiting on confirmation of whether further changes are needed
For example, you could write something like this:
The creation and revisions on our side are done.
The remaining items are confirmation by the higher-ups along the agreed route, and confirmation of whether any further changes are needed.
If there are no changes, my understanding is that we will proceed with this item treated as complete.
This way you can show where it's stuck without blaming anyone directly.
What matters isn't attacking your boss.
It's making the state of the work visible.
14. Countermeasure 3: Don't make your boss the only route for reporting results
If you leave result reporting to a bottleneck boss, the results never reach the top.
That's why it's better not to make your boss the only reporting route.
Of course, there are workplaces where sending something straight to higher-ups on your own would be risky.
Even then, you can still leave a completion log in the Teams channel or group chat that the people involved are already in.
This item is complete on our side.
Reflected before the revision deadline.
The latest version is below.
The remaining item is whether the approval route has approved it.
Even this much leaves a record that the deliverable exists, that the work is complete, and that the remaining item sits on the approval side.
Even if your boss doesn't report the results, at least they stay on record.
That matters.
15. Countermeasure 4: Set entry conditions before you accept a request
From now on, when you take on similar projects, it's better to set entry conditions.
Especially for projects where having your boss involved would create a bottleneck, set the conditions at the start.
Who is the approver?
Where is the review route?
Who consolidates revision feedback?
When is the feedback deadline?
Who makes the final call?
Who reports on actual use?
Where does the worker's responsibility end?
Taking on a project where these aren't settled is dangerous.
You were only supposed to produce a rough draft, and before you know it you're carrying approval coordination, higher-up checks, feedback collection and completion reporting.
At the entry point, it's fine to say this:
I'll handle drafting, organizing the structure and proposing improvements.
Please leave final decisions, coordination with stakeholders and obtaining approval to the department in charge.
Please consolidate revision requests through a single point of contact before sharing them with me.
If contact points are scattered, or the approval route is undefined, that falls outside my scope.
This isn't running away.
It's putting responsibility back where it belongs.
16. Countermeasure 5: Use the quality-control project approach
There was one form that worked well on a quality-control (QC) project.
It was a setup where someone from another department was given full authority and I stuck to being an advisor.
The person from the other department is the lead
The person from the other department is the point of contact
The person from the other department owns approval and coordination
I am the advisor
If the boss gets involved, route through that person
If responsibility or work comes back to me, I step away
This is quite strong.
That's because it keeps me from becoming a general errand-runner for the deliverable.
I give my opinions as an advisor.
I organize the structure.
I propose improvements.
But final responsibility, approval, coordination with higher-ups and feedback consolidation sit with the lead.
That makes it harder to get dragged in by a bottleneck boss.
It's better to steer future projects toward this setup as well.
17. Countermeasure 6: Separate trivial comments from high-risk comments
There are different kinds of comments.
If you treat them all with the same weight, work stops.
High-risk comments
Legally risky
Contains personal information
The amount is significantly wrong
Wrong information would go outside the company
It would mislead customers, students or applicants
It affects deadlines or contracts
These you act on.
Notation clarifications
Write out "1,800 yen per hour" explicitly
Unify the date format
Use the official name
Add the unit
These you fix without stopping and keep going.
The itch for the red pen
Stopping something that's clear from context
Holding up urgent work with a pointless check
A comment made only to show off a sense of control
For these, handle only the bare minimum.
If you take every one of them seriously, the bottleneck boss's itch for the red pen ends up running your work.
What matters is separating high-risk comments from low-value ones.
18. What subordinates should do, and what they don't have to
In this kind of workplace, subordinates also need to set their own boundaries.
What to do
Create it
Fix it
Share the deadline
Send the completion notice
Share with the people involved
Leave how things will proceed in writing
State the open items clearly
Confirm whether there is further feedback
You're fine to do all of this.
What you don't have to do
Patch up your boss's missed result reports every time
Chase every time whether your boss showed it to the Senior Managing Director
Take your boss's unreturned OK/NG as your own responsibility
Shoulder the missing report on actual use
Step in as a general errand-runner with no approval route defined
Take every pointless red-pen remark to heart
If you take on all of this, the reverse management tax is too heavy.
A worker is a person who makes deliverables.
They are not someone who endlessly repairs a manager's management failures.
19. Templates for your paper trail
Here are templates for building a defensive record from now on.
Completion report template
The creation and revisions for this item are complete on our side.
The points raised have also been reflected.
The latest version is below.
The remaining items are confirmation by the higher-ups along the agreed route, and confirmation of whether any further changes are needed.
Please let me know if you'd like any further changes.
If there are no changes, my understanding is that we will proceed with this item treated as complete.
Status check template
Just to confirm.
I'd like to check the current status of this item.
1. Has it been confirmed by the higher-ups?
2. Has it been used for real?
3. Are there any further changes?
4. Is it OK to treat it as complete?
The creation and revisions on our side are done.
If there are no further changes, I will record it as complete.
Entry conditions template
Let me confirm the scope of what I can handle.
I'll handle drafting, organizing the structure and proposing improvements.
Please leave final decisions, coordination with stakeholders, obtaining approval and consolidating feedback to the department in charge.
I can take this on if the approver, the review route, the feedback deadline and the completion criteria are settled.
If they are undefined, it falls outside my scope.
With these three, you're quite well protected.
20. Summary: Horenso isn't a ritual of obedience for subordinates, it's status management that keeps work moving
People who understand horenso only on the surface demand it only from their subordinates.
But real horenso is not a ritual of rank.
Report = make the state of the work visible
Inform = get everyone involved on the same page
Consult = move the decision forward
And there is also horenso from boss to subordinate.
Did you show it to the higher-ups?
Is it OK or NG?
Was it used for real?
Are there further changes?
Is it fine to treat it as done?
Where is it stuck?
A boss who doesn't return these makes it hard for subordinates to move.
If a subordinate has made it, fixed it, shared it, set the deadline, sent the completion notice and left how things will proceed on Teams, and the boss still won't move the approval route, won't report the results and won't return OK/NG, that is not the subordinate failing at horenso.
It is the boss failing at horenso.
And the state in which the subordinate is made to patch up that management failure is reverse management.
If you want to produce results, a worker has no choice but to do the following:
Leave completion in writing
Leave "fixed" in writing
Leave open items in writing
Leave "waiting on approval" in writing
Don't make your boss the only route for reporting results
Draw the line on your responsibility at the entry point
Don't take the bottleneck on as your own responsibility
Put in one line:
Before you preach horenso, return the status first, boss.
It isn't a lack of initiative on the subordinate's part.
It's a lack of process design on the boss's part.
