🇯🇵 Would you survive a meeting in Tokyo? Take the 10-question quiz →
Bengaluru has one of the largest concentrations of Japanese-linked employers in India — automotive, electronics, engineering, and the global capability centres behind them. If you work in this city long enough, you will end up in a meeting with a Japanese company.
Most Indian professionals who struggle in those relationships are not struggling with the work. They are excellent engineers, capable managers, careful analysts. What catches them out is a set of conventions nobody writes down, because to the Japanese side they are too obvious to mention.
Here are eight of them, drawn from twenty years of teaching, translating and interpreting between the two countries.
1. “Difficult” usually means no
If you present a proposal and your counterpart calls it 難しい (muzukashii, difficult), the temptation is to hear a negotiation opening. Often it is a refusal.
Direct rejection is avoided in Japanese business language because it causes the other party to lose face. “That would be difficult,” “we will consider it carefully,” and “that may be challenging at this time” are all ways of saying no while leaving the room intact.
What to do: don’t push for a yes in the room. Ask what would need to change for the proposal to work. If the answer is vague, you have your answer.
2. Silence is thinking, not confusion
In most Indian meetings, a pause after you finish speaking means something has gone wrong. So we fill it — we re-explain, add detail, raise our voice slightly.
In a Japanese meeting, that pause is consideration. Somebody is weighing what you said and preparing a response. If you talk over it, you bury the one point they were actually thinking about, and the discussion moves on without them.
What to do: after you finish, count to five silently before adding anything. It will feel unbearable. Do it anyway.
3. The decision was made before the meeting
根回し (nemawashi) literally describes preparing a tree’s roots before transplanting it. In business it means building agreement quietly, one conversation at a time, before anything reaches a formal meeting.
Indian managers often read this as slowness or indecision. It is neither. The decision-making happened — you simply were not in the conversations where it happened, because nobody invited you into them.
The corollary is that pushing for a decision during the meeting doesn’t read as decisive. It reads as disruptive, and it can quietly kill a proposal that would otherwise have passed.
What to do: do your own nemawashi. Speak to people individually beforehand. Arrive at the meeting with agreement already built.
4. Bad news does not improve with age
This is the one that costs the most, and it is worth an example.
Some years ago I was interpreting for a Japanese trainer who had flown to India to deliver technical training. A few days, fixed window, flights and calendar arranged months ahead. The training required certain parts. Those parts were delayed — and we knew.
He was told after he landed.
His answer was that we should proceed on schedule, which was the only answer left by then. The days did not go the way they should have. A man had come from Japan for a handful of days and we could not use them.
Nobody lied. Nobody was incompetent. What happened is the most human thing there is: somebody had bad news, thought they could fix it before it mattered, and waited.
In a Japanese company that instinct is exactly backwards. There is a word for the alternative — 報連相 (hōrensō): 報告 report, 連絡 inform, 相談 consult. Raise it early, tell everyone affected, and ask before it becomes a crisis.
What to do: the moment you know a deadline is at risk, report it — with the cause, what you are doing about it, and a revised date. The delay is rarely the problem. The days you sat on it are.
5. On time is late
A 9:00 meeting does not mean arriving at 9:00. It means being seated, set up and ready before the hour. Walking through the door as the clock strikes is read as cutting it fine, and cutting it fine is read as not valuing everyone else’s time.
This scales. Japanese trains are famously punctual because punctuality is treated as a shared obligation rather than a personal virtue.
6. Improvement is small, constant and bottom-up
改善 (kaizen) gets translated as “continuous improvement,” which makes it sound like a management programme. In practice it is the opposite of a programme: small changes, made constantly, suggested by the people actually doing the work, documented so the next person inherits them.
The instinct many of us bring is the big fix — the transformation, the new system, the consultant. Kaizen is the small fix, today, repeated forever.
7. Inside and outside are real categories
内 (uchi, inside) and 外 (soto, outside) describe a boundary that governs a great deal of Japanese social and professional behaviour — including how formally people speak to you.
As a new external partner you are firmly soto. The formality you encounter is not coldness; it is the correct register for someone outside the circle. What surprises people is the other side of it: once you are uchi, the relationship becomes notably warm, and it tends to last for years.
What to do: don’t try to shortcut it with familiarity. Reliability over time is what moves you across the line.
8. A schedule is a commitment, not a proposal
This one underpins several of the others, and it scales all the way up.
When a date is agreed with a Japanese partner — a delivery, a visit, a launch — it is treated as settled. Not as an intention, not as a best case, and not as something to be revisited when circumstances change. The planning that went into it on their side assumed the date would hold.
The Indian working assumption is often gentler: dates are targets, everyone understands that things slip, and a slip communicated is a slip forgiven. Both approaches are internally reasonable. The trouble starts when each side assumes the other shares its own.
What that looks like in practice: your counterpart hears silence and reads it as confirmation. You hear no follow-up and read it as flexibility. Nobody is being difficult, and the relationship still ends up damaged — because from the other side, a date that moved without warning looks like a commitment that was not honoured.
The same misunderstanding shows up at every scale, from a training visit that could not be used to cross-border deals that have ended in years of arbitration. Only the number of zeros changes.
What to do: treat every agreed date as fixed until you have explicitly agreed a new one. If it is at risk, say so early and bring a proposed alternative. Silence is not neutral — it is read as confirmation.
The part that is actually about you
In most Japanese multinationals, Indian managers reach the Tokyo head office through a translator. Your ideas arrive filtered through somebody else’s choice of words, and somebody else decides how you sound.
Learn the language and you bypass that. You stop being a local employee whose work has to be relayed, and become the connection between two halves of a company. Every CV in the pile has finance, marketing and analytics on it. A language moves you into a different pile.
None of that requires fluency on day one. It requires starting.
Where to start
Saachi Japanese Language Institute runs live online JLPT courses from N5 to N2, plus corporate training for teams working with Japanese partners. Our Chief Trainer, Lata Naik, holds JLPT N1 and BJT Level 2, with over twenty years of teaching experience. Saachi also has extensive experience in translation and interpretation services.
If you are not sure which level you would start at, our free level check takes about twenty minutes and tells you where you actually stand.
Questions about batches, timings or fees? Message us on WhatsApp — you’ll get an answer straight away, whatever time it is.