On a lot of teams, silence is fine. If your manager doesn't hear from you, they assume the work is moving and leave you alone. No news is good news.
On a Japanese dev team, the default runs the other way. If nobody has heard from you, the quiet itself starts to feel like a risk. Not because anyone thinks you're slacking. A problem nobody has heard about is simply one nobody can help you with yet. So the most valued habit is speaking up early, before anyone asks, while the work is still half-done — not saving up a clean report for the end.
There's a word for the whole bundle of habits around this, and you'll hear it constantly.
Hōrensō: three moves in one word
ほうれんそう (hōrensō) is a made-up word stitched from the first sounds of three others. It also happens to sound exactly like the word for spinach, which is why the name sticks. The term itself is plain business vocabulary, used in completely serious settings — the spinach resemblance is just a memory hook, not a punchline. The three pieces are:
- 報告 (hōkoku): reporting. Telling someone about a result. It looks backward at something finished.
- 連絡 (renraku): informing. Passing along a plain fact, with no opinion and nothing to decide.
- 相談 (sōdan): consulting. Asking for input before you decide, so it looks forward.
A quick way to sort them: do you need someone's opinion before you can move? That's sōdan. Is it just a fact the team needs to know? That's renraku. Are you reporting an outcome? That's hōkoku.
Here's each one in a normal work moment.
Reporting something you finished:
昨日お願いされた資料、完成しました。共有フォルダに置いておきます。
"The document you asked me for yesterday is done. I'll put it in the shared folder."
Short, backward-looking, no opinion attached. It names the task, says it's done, and says where to find it.
Informing the team of a fact:
明日、サーバーメンテナンスがあるので、朝9時まで一部の機能が止まります。
"There's server maintenance tomorrow, so some features will be down until 9 a.m."
Pure information: what's happening, when, what it affects. No request buried inside it.
Consulting before you commit to a direction:
ちょっとご相談があるのですが、今お時間よろしいですか？この設計、2つの方法で迷っていまして。
"Could I run something by you — do you have a minute? I'm torn between two approaches on this design."
The key verb there is 迷っていまして (mayotte imashite), "I'm torn between options." It asks for an opinion without demanding an answer, which is exactly what makes it a consultation instead of a decision you're announcing.
The part that actually matters: go first
You could memorize all three words and still miss the point of them. The real habit sitting on top of hōrensō is 先回り — going first. A short heads-up sent early beats a perfect report sent late.
This is the move that feels wrong if you come from a "don't bother people until it's done" background. On a Japanese team, sharing work that's still in progress is treated as a courtesy. You're giving people the time to react while there's still room to react.
The phrase that unlocks it is this:
まだ途中なんですが、今の進捗だけ先にお伝えしておきます。
"I'm still in the middle of it, but let me share where things stand so far."
The load-bearing part is the opener, まだ途中なんですが (mada tochū nan desu ga), "I'm still in the middle of it, but…". It gives you permission to report something incomplete. Once you can say that, you can surface a half-finished status, a blocker you just hit, or a risk you see coming, all without waiting for a tidy conclusion. If you learn one phrase from this whole idea, learn that one.
Why it works this way
None of this is about being formal for its own sake. The logic is mundane but real: catch a shaky design decision on Tuesday and it costs a conversation; catch it after it ships and it costs a sprint. Reporting in progress, passing facts along, asking before deciding — they're all ways of keeping information moving so nothing festers in a corner where only you can see it.
Once you read it that way, the instinct to go quiet and "come back when it's solved" is the one habit worth dropping. The quiet is the thing your team is trying to avoid.
The takeaway
If you're joining a Japanese dev team, don't save your updates for the finish line. Report what's done, pass along what's true, ask before you decide — and whenever you can, say it early, even mid-task. "まだ途中なんですが" is the phrase that lets you do the last one, and it's the one nobody writes down for you.
This is one lecture from a course I built called Japanese for Software Engineers — the workplace Japanese that only shows up once you're actually on a team: stand-ups, code reviews, incident calls, and the reporting habits above. If it's useful to you, it's free through August 21, 2026: https://www.udemy.com/course/japanese-for-software-engineers/?couponCode=ABAD7DB87460AA4E2853
TL;DR
- On Japanese dev teams, silence reads as risk, not reassurance. Sharing early is the valued habit.
- ほうれんそう (hōrensō) = 報告 report a result / 連絡 pass along a fact / 相談 ask before deciding.
- Sort them by intent: need an opinion first → sōdan; just a fact → renraku; an outcome → hōkoku.
- The real skill is 先回り (going first): a quick early heads-up beats a perfect late report.
- The one phrase to keep: まだ途中なんですが ("I'm still in the middle of it, but…"), which lets you report unfinished work.
Top comments (0)