Japanese Work Style: Why Decisions Are Slow and Execution Is Fast
Team KakehashiX

The short version
• Japanese companies feel slow to decide and then suddenly very fast to act. That is not inefficiency — it is the order the work happens in.
• Decisions are not made in meetings. A meeting confirms what was already agreed beforehand.
• You are judged not only on your results, but on whether someone else can follow how you got there.
• The most expensive mistake foreign staff make is not working slowly — it is taking initiative without telling anyone.
The pattern that confuses everyone in the first few months
Almost everyone who joins a Japanese company from outside goes through the same experience. A simple proposal — change a vendor, adjust a report format, buy one piece of equipment — takes weeks with no clear word back. You start to suspect it was quietly rejected.
Then the decision lands, and everything moves in two days. Everyone already knows what to do. Nobody asks again. Nobody objects halfway through.
Those two phases are one system. The time that felt wasted in the first phase is the investment that makes the second phase frictionless. Once you understand the mechanism, a Japanese company stops feeling slow and starts feeling predictable.
Ringi: the document travels, not the decision-maker
At many Indonesian and Western companies, a decision is made by a person. Someone holds the authority, hears the arguments, and decides.
At a Japanese company, what moves is the document. The system is called ringi (稟議): a proposal is written down, then circulated upward through every party it touches, each one reading it and adding their approval, until it reaches the level with authority to sign it off.
Three consequences are worth understanding:
• Your proposal is read by many people, not one. If it is written unclearly, the result is not rejection — it is the document quietly stopping on somebody’s desk.
• Everyone who approves it shares the decision. That is why the process is careful: the people who signed carry part of the responsibility if it goes badly.
• Once it is signed off, the debate is over. Everyone has already read and approved it. That is exactly why execution is fast.
From your side as the person proposing, one thing improves your odds immediately: write a proposal that makes sense without you in the room. Background, the problem it solves, the options considered, the cost, the risks. A proposal that needs you there to explain it will stop at the first reader who has never spoken to you.
Why the meeting is not where you argue
This is where people from outside most often misstep, because in many workplaces the meeting is precisely where you fight for an idea.
At a Japanese company, before a proposal reaches a meeting, the person proposing it has already spoken to each affected party one at a time — heard their objections, adjusted the proposal, made sure nobody will be surprised. The practice is called nemawashi (根回し), literally preparing a plant’s roots before transplanting it.
So by the time the proposal reaches the meeting, the decision has already formed. The meeting exists to confirm and align, not to choose.
If the meeting is the first time you raise your idea, you have already lost your best chance — not because the idea is bad, but because you have asked people to judge something in front of their boss with no preparation.
Do the reverse instead: talk to the people it affects, one at a time, before the meeting. Ask what they object to and fix your proposal. By the time you present it, it already has supporters.
On reading the indirect signals inside conversations like these — including when "that would be difficult" actually means no — we cover that separately in Japanese Business Communication for Foreigners.
The approval chain: why one signature can take a week
Many Japanese companies, including their Indonesian subsidiaries, still run layered approvals — whether by signature, by stamp, or through a digital system that mirrors the same chain.
What usually frustrates people is not the number of layers but not knowing which layer they are at. And here is the part that often goes unrealised: you are allowed to ask. Asking where a document has reached is not read as pushy or impatient — it is read as following your own work.
Three practical habits that save a great deal of time:
1. Ask up front who needs to approve your proposal, and in what order.
2. Note the date you submitted it, and ask where it stands if it runs past the expected time.
3. If there is a real deadline, put the deadline in the document itself — not mentioned verbally afterwards.
Daily rituals that have a function
Several habits at Japanese companies look like formality until you know what they are for.
Habit | What it is actually for |
Chourei (朝礼) | A short morning meeting. It levels the information for the day — who is out, what the priorities are, what is still unresolved. If you stay silent every morning, you lose the cheapest way to be seen keeping up with your work. |
Written reports | Not bureaucracy. Japanese companies rely on records another person can read while you are away. A tidy report is how your work becomes visible. |
PDCA and kaizen | Plan–do–check–act. It means "finished" is not the end; there is always the question of what could be better next time. |
Hansei (反省) | Reviewing what fell short after a job is done — including when the result was good. This is not fault-finding; it is the habit of checking. |
One thing about hansei worth getting right: when a Japanese manager discusses what fell short in work that succeeded overall, it is not a criticism of you. Responding defensively reads as an unwillingness to improve.
What you are actually assessed on
This is the difference that most shapes your performance review, and the one least often explained out loud.
In many workplaces, the result is what counts. Delivered on time, target hit, done.
At a Japanese company the result counts too — but the process is weighed almost equally. The questions in your manager’s head are not only "is this done", but also: did they tell the people who needed to know, did they ask before guessing, could someone else pick this up if they were away?
Which produces a pattern that surprises people: someone who delivers brilliantly but tells nobody along the way can be rated lower than someone whose result was ordinary but whose whole process was visible.
This does not mean initiative is unwelcome. Initiative is valued — as long as it is communicated. The distinction is narrow and it decides a lot.
The five most expensive misreadings
1. Taking your manager’s silence as agreement. No response usually means your document is in transit, or stalled with someone. Ask.
2. Raising a new idea for the first time inside a meeting. Talk to people individually first. Meetings confirm; they do not choose.
3. Solving a problem alone without telling anyone. In many workplaces this earns praise. At a Japanese company it costs your manager their picture of the work, and that is marked against you.
4. Waiting until you are certain before reporting a problem. An early, incomplete report is valued far more than a complete one that arrives late.
5. Taking correction as a personal attack. Discussing shortcomings is part of the work cycle, not a verdict on you.
Adapting without becoming someone else
Adapting to a Japanese way of working does not mean changing who you are. Most of what needs to change is mechanical, not a matter of personality.
What to change: your habit of keeping people informed, the tidiness of your records, and the order in which you talk to people before a meeting. All three are learnable within a few months and the effect is immediate.
What not to change: how you think, your willingness to propose improvements, and your nerve to say something is wrong. Japanese companies in Indonesia often hire local staff for exactly this — they need someone who can say that a plan will not work in Indonesia, and say it in a way that can be heard.
On hierarchy, etiquette and the unwritten daily rules — from hou-ren-sou through to nomikai — we cover those in full in Understanding Japanese Senpai–Kohai Culture. And if you are weighing up the office track at a Japanese company, we map the route in Not an Internship, Not a Factory: The Office Route at Japanese Companies.
Frequently asked questions
Why has nobody replied to my proposal at all?
Usually because the document is travelling through several parties, or has stalled with someone who does not yet understand it. Ask where it stands — that is normal and not read as pushy.
Am I allowed to disagree with a Japanese manager?
Yes, and it is often expected. What matters is the timing and the manner: raise it before the decision is signed off, privately, with a reason and an alternative — not in front of a group after everything has been settled.
Is this the same at every Japanese company?
Not uniformly. Large companies and factories are generally stricter; small companies, startups and branches run by local managers tend to be looser. But the underlying pattern — keep people informed, write it down, prepare before the meeting — is almost always there.
Do I need Japanese to adapt to this way of working?
Not strictly, but it helps a great deal. Many Japanese companies in Indonesia run day to day in Indonesian and English. Japanese ability speeds things up because you understand what was meant rather than what was translated.
How long does it usually take to get used to?
Most people get through the most confusing phase within the first three to six months. What speeds it up is not language ability but the habit of reporting more often than you think is necessary.
Looking for a role at a Japanese company? Browse current openings for Japanese speakers at KakehashiX.
About the Author
Team KakehashiX
Contributing writer at KakehashiX, sharing insights on Japan-Indonesia professional connections and career development.