A lot of engineers arrive on a Japanese team with one quiet assumption: here, you don't show weakness. You figure things out on your own, you don't make noise, and above all you don't announce to the room that you're blocked.
So they go quiet. They burn two days on a problem a teammate could have unblocked in five minutes, because saying "I'm stuck" out loud feels like admitting they can't do the job.
After about twenty years in Japanese software teams, I can tell you that assumption is backwards. On the teams I've worked on, naming your blocker early is the expected move, not the risky one. There's literally a slot built into the day for it.
The stand-up has a third slot, and it's for being stuck
Most Japanese stand-ups run on a fixed three-part template, in this exact order:
- 昨日（きのう）— what you did yesterday
- 今日（きょう）— what you're doing today
- 困（こま）っていること — what you're stuck on
That third part isn't optional color. It's a structural slot, and the team expects you to fill it when you have something. Walking in with a blocker isn't interrupting the ritual — it is the ritual. The lead is listening for exactly that so they can hand you the key, the access, or the two minutes of context you're missing.
Once you see the blocker slot as "the thing I'm supposed to report," the whole fear dissolves. You're just giving a status update that happens to end in a request — nobody in the room hears a confession.
Name the blocker. Don't apologize for it.
Here's the phrase that does the most work:
〜で詰（つ）まっていて
~ de tsumatte ite — "I'm stuck on ~"
詰まる is the same word you'd use for a clogged pipe or a traffic jam. Something isn't flowing. That's the whole frame — you're describing the work, not grading yourself. You name the thing that's blocked, and then you ask for help:
助（たす）けてもらえますか
Tasukete moraemasu ka — "Could you help me out?"
Put together, it sounds like this:
ただ、APIキーがなくて詰まっていて、助けてもらえますか。
"The thing is, I don't have the API key so I'm stuck — could you help me out?"
Notice how little is in there. No three sentences of backstory about the four things you tried first, no string of apologies — one clean fact, one clean ask. That directness is the part that reads as competent.
Size the ask to who's listening
The blocker phrase stays the same. What changes is how heavy the request gets, depending on who's in the room:
| Who | How you ask |
|---|---|
| A colleague（同僚） | ちょっと見（み）てもらえる？ — "Mind taking a look?" |
| A senior（先輩） | ちょっと見ていただけますか？ — "Could you take a look?" |
| Client-side（顧客側） | お手数（てすう）ですが、ご確認（かくにん）いただけますでしょうか — "Sorry to trouble you, could you confirm?" |
Same request, three lengths. If you only remember one, remember the middle one — 見ていただけますか is safe with almost anyone you report to and never sounds too stiff.
In chat, you have to add the tone back in
Stand-up is face to face. Chat isn't, and that changes the math. In person, your expression and tone soften a blunt request for you. In a Slack message, the words are doing that job alone — so a bare "can you check this?" lands colder than you mean it to.
Two short phrases carry the softening:
お忙（いそが）しいところ恐縮（きょうしゅく）ですが…
"Sorry to catch you when you're busy, but…"お手すきの際（さい）に…
"Whenever you get a free moment…"
The first acknowledges you're taking their time. The second signals there's no fire — it can wait for a gap. Drop them around the same blocker-and-ask you'd say out loud, and a written request stops feeling like a demand:
お忙しいところ恐縮ですが、こちらのPR、お手すきの際にご確認いただけますか？
"Sorry to catch you when you're busy — whenever you get a moment, could you review this PR?"
The two traps
Almost everyone getting this wrong falls into one of two ditches.
Going quiet — or over-explaining. The silent version is obvious: you don't report the blocker at all and lose a day. But the louder version trips people up too. They finally raise it, then bury the actual blocker under a paragraph of everything they tried first. By the time they reach the ask, the lead has lost the thread. Lead with the blocker. The backstory, if anyone wants it, comes after.
Apologizing instead of reporting. A reflex すみません、すみません… feels polite, but a pile of apologies is vaguer than one concrete sentence. "I'm stuck on the API key, could you help?" tells the lead exactly what to do. "I'm so sorry, this is probably my fault, sorry to bother you…" tells them nothing actionable. On a Japanese team, the concrete report is the respectful move — it saves everyone's time, which is the thing actually being valued.
Say it early, say it plainly, and size the ask to the room. The silence you were so worried about? That's the only part that ever actually looks bad.
If you want to drill these out loud before you need them for real, this is exactly the kind of thing my Udemy course walks through — stand-ups, code reviews, Slack, and asking for help, all in real workplace Japanese. It's at its lowest price ($9.99) until Oct 20: Japanese for Software Engineers.
TL;DR
- Japanese stand-ups have a built-in slot for blockers (困っていること). Reporting one early is what the team expects — nobody reads it as weakness.
- Name the blocker as a fact: 〜で詰まっていて ("I'm stuck on ~"), then ask: 助けてもらえますか.
- Keep the phrase, change the weight of the ask by audience — 見ていただけますか is the safe default.
- In chat you lose tone, so add it back: お忙しいところ恐縮ですが + お手すきの際に.
- Avoid the two traps: going silent / over-explaining, and apologizing instead of giving one concrete report.
Top comments (0)