Horenso: The Japanese Work Rule That Almost Got Me
Most foreigners in Japan don't learn about horenso until they've already made the mistake. Here's what nobody tells you before the re-org.
How I came across horenso
Good work speaks for itself.
That was my assumption when I first moved to Japan in 2019. New to the country, confident in the job. Deliver quality, hit your deadlines, keep the team moving. That’s what gets you recognized.
In Japan, that framing is incomplete.
I knew I was performing. The work was solid, the results were showing up. What I didn’t see was that my manager wasn’t in the loop on most of it. And because they weren’t, they didn’t have what they needed to advocate for me when it counted. Being new to Japan meant I was new to the unwritten rules too. This one cost me.
That gap has a name. It’s called horenso (報連相). It stands for hōkoku (report), renraku (contact), and sōdan (consult). If you’ve spent time in a Japanese company, you’ve heard of it. If you haven’t, you’ve probably felt its absence without knowing why.
The re-org story
Now that I operate as a manager, I’ve watched this pattern repeat itself.
Someone joins a Japanese company, but their first manager isn’t Japanese. Maybe it’s a regional role, a startup-adjacent team, or an international division. The manager is results-oriented, high trust, moves fast. The engineer thrives. They operate with autonomy. They bring solutions, not problems. Everyone’s happy.
Then a re-org happens.
New manager. Japanese. Everything looks the same from the outside, but the operating model has changed underneath. The engineer keeps working exactly as before. Solving problems independently. Delivering good work. Not reaching out to the manager unless there’s something worth reporting.
The relationship starts to quietly deteriorate. The manager feels out of the loop. The engineer feels micromanaged when the questions start coming. Both sides grew frustrated without a shared language for what was actually happening.
The engineer was doing everything right by their previous manager’s standards. They were also doing everything wrong by their new manager’s standards.
The operating model had changed. Nobody told them.
What most people misunderstand
People eventually figure out hōkoku and renraku. Reporting and keeping people updated. Uncomfortable at first, but not foreign.
Sōdan is where it breaks down.
Consulting before you act feels wrong if you’ve built your career on independent judgment. You’ve been promoted for having the answer. Going to your manager before you have the answer feels like it signals weakness. Like you’re not ready.
In many companies in Japan, that instinct works against you. But here’s the part that reframed it for me: sōdan isn’t really about asking permission. And hōkoku isn’t just about keeping your manager informed.
It’s about giving your manager the material to go to bat for you.
In a Japanese organization, your manager represents you in rooms you’re not in. Calibration sessions. Cross-functional planning. Headcount conversations. If they don’t have a detailed picture of what you’ve been doing and how you’ve been thinking, they can’t make a case for you. They’re not withholding advocacy. They simply don’t have the information to do it.
That’s the cost of going dark. Not just a strained relationship. A manager who wants to advocate for you but can’t, because you never gave them what they needed.
What I now tell people navigating this
When I’m onboarding someone into a Japanese corporate structure, horenso is the first thing I mention. In most large Japanese companies, it’s already part of the onboarding program. They invest real time in it. But knowing the definition and actually knowing how to apply it are two very different things.
A few things I always say:
Report more than you think you need to, especially when things are uncertain. Don’t wait for something concrete. Progress updates give your manager something to reference when your name comes up in conversations you’re not part of. There’s a difference between “I finished the migration” and “I drove the migration that unblocked the Q2 rollout.” The first keeps your manager informed. The second gives them a sentence they can repeat in a room you’re not in.
Sōdan is not a sign of weakness. Walking your manager through your thinking before you move is how you build a shared picture. The manager who knows how you think is the manager who can speak to your judgment when it matters.
The method is part of the result. A decision made through proper consultation carries more weight inside a Japanese organization than the same decision made unilaterally. The how is evaluated, not just the what.
My honest take
Horenso isn’t without problems. It can be painfully slow when speed matters. It can create situations where the people who most need to raise concerns have the least safe path to do so. And like any structured system, it gets misused.
I stopped thinking of it as a reporting obligation and started thinking of it as how I kept my manager equipped. The evaluation results reflected that shift. It doesn’t guarantee outcomes — your manager still has to carry what you give them. But they can’t carry what they don’t have.
The professionals I’ve watched thrive in Japanese organizations are not always the most technically capable. They’re the ones whose managers always know where they stand. That knowledge travels. It shows up in conversations you’ll never be in the room for.
You usually figure that out from a difficult transition.
Or someone tells you before it happens.