Business in Tokyo rewards reliability. Companies prefer proven methods, decisions are built through consensus, and once a plan is agreed it is carried out with real discipline. That stability is valuable, but it makes changing course hard when the plan stops fitting the facts. Adaptability here means two things: recognizing early when persistence has become a liability, and using the existing consensus process to change direction instead of trying to override it.

The opposite mistake is also common. Some leaders, often newly arrived ones, treat adaptability as permission to change direction every few weeks. In a Japanese team that destroys trust quickly. Being adaptable in Tokyo means changing the plan when a new fact requires it, and then letting people finish the work.

How are decisions made in Japanese companies?

From outside, Japanese business often looks like a model of stability and long-term thinking. Working inside it, you find a system with its own logic, which Peter Drucker described for Western readers in the Harvard Business Review more than fifty years ago in “What we can learn from Japanese management”. Much of what he observed still applies.

Hierarchy and the senpai-kōhai relationship

Most Japanese organizations rest on the senpai-kōhai (senior-junior) relationship. The senior colleague mentors and protects; the junior offers loyalty and effort. It passes on institutional knowledge well and builds strong group cohesion over years.

The same loyalty slows down bad news. A junior employee who sees a problem with a senior colleague’s plan will often hesitate to say so directly, especially in a meeting. By the time the concern reaches someone who can act on it, the problem is larger.

Nemawashi and ringi

Major decisions are rarely made by one executive. They are built in two stages. Nemawashi is the informal groundwork: the person proposing a change talks to each stakeholder individually, hears their concerns and adjusts the proposal before any formal meeting. Ringi is the formal step, where a written proposal circulates for approval and each relevant manager adds their seal.

The process is slow and thorough. Its strength shows after the decision. Because everyone has been consulted, implementation tends to be fast and unified, with little of the post-meeting resistance common elsewhere. The difficulty is that a plan built with this much effort is hard to reopen.

When does stability become rigidity?

The signs that a project has outlived its purpose are usually visible well before anyone acts on them. They get ignored out of commitment to the original agreement and reluctance to make the people who built it lose face.

Warning signs

  • Drift: The market or the business has moved, but the project continues on its original path. It may still hit its own targets while no longer serving the company’s priorities.
  • Opportunity cost: The project absorbs the best people and budget, starving work that is going well. This is the most expensive sign and the easiest to overlook.
  • Past spending as the main argument: Meetings focus on what has already been invested rather than what the next stage will return. A useful test is to ask whether you would approve the project today if it were proposed from scratch. I cover this in more detail in deciding when to stop a project.
  • Defensive meetings: The team spends its energy explaining past decisions instead of improving the work. The aim quietly shifts from succeeding to avoiding embarrassment.

How do you change direction in a Japanese company?

Know when to let go

The hardest leadership decision is often ending a project, partnership or vendor relationship that has stopped working. Ending it is not quitting. It is recognizing that persistence has become the problem. The same applies to suppliers and partners. Keeping a vendor who repeatedly fails to deliver, because the relationship is long and ending it would be awkward, costs the company every month it continues.

Use the system to change the system

A frequent mistake by foreign managers is announcing a change of direction from the top and expecting the organization to follow. In a consensus culture that creates quiet resistance, and the new plan stalls in implementation.

It works better to use the same tools that built the original plan. Start nemawashi for the change: meet the key people individually, show them the evidence, listen to their concerns and let them shape the new approach. Give the people who championed the original plan a respectable role in the new one. When the change reaches a formal meeting, most of the agreement already exists, and implementation keeps the speed that makes Japanese teams effective.

Make the evidence easy to see

Consensus moves faster when everyone looks at the same facts. Much of the delay in changing course comes from information that only a few people can see: sales figures in one spreadsheet, customer complaints in someone’s inbox, project costs in the accounting system. A simple shared report that shows how the project is actually performing makes the conversation about the numbers rather than about who proposed what.

Change direction rarely, and explain why

Because the consensus process is expensive, each change of direction uses up goodwill. Save it for real changes in the facts, explain clearly what changed, and then hold the new course long enough for the team to deliver. A leader who pivots often trains the team to wait before committing to anything.

What a mixed approach gives you

Combining the discipline of a Japanese team with a habit of reviewing whether the plan still fits produces a strong organization. You keep the cohesion, long-term focus and careful execution, and add the ability to stop or redirect work when conditions change. The two work together when changes of direction are infrequent, based on visible evidence and built through the same consensus process as the original plan.

The ability to change course is as valuable as the ability to persevere. The skill is telling the two situations apart, and in Tokyo that usually depends on having clear information and taking the time to bring people with you. The same theme runs through turning a business decision into working practice and the cultural background in Japanese leadership culture and wa.

If you lead a team in Japan and want an outside view on which projects and systems still deserve investment, I work with companies as a fractional technology advisor, helping put the reporting and working structure in place so those decisions rest on shared facts.

Further reading: turning a business decision into working practice in Japan · deciding when to stop a project · preparing managers to work across borders