In Japan, a decision is often treated as finished once everyone has agreed to it. That is where execution starts. Someone still has to own the change, alter the process and tools it affects, tell the people who will work differently, and check a few weeks later whether the new way is actually in use. In 2026 the organizations that do those steps reliably, whatever their size, are pulling ahead of those that stop at agreement.

In Part 0 of this series I argued that 2026 is the year Japan’s future becomes visible: institutions are not transforming, but their limits are easier to see next to faster alternatives. This part moves from diagnosis to behavior. It asks who is doing the work of execution, and how they do it.

Why do large Japanese organizations struggle to execute?

Japan Inc. remains essential. Large institutions regulate, run national infrastructure, keep continuity and absorb risk at a scale nobody else can. That will not change this year.

What is changing is that they no longer set the practical limits of what can be done. The constraint is rarely ambition, intelligence or access to technology. It is structural. Decision rights are spread across layers designed to keep any one person from carrying the risk. Responsibility is shared so widely that failure lands nowhere in particular. Timelines stretch, accountability blurs and action waits for alignment rather than readiness.

That structure is very good at preventing mistakes and poor at taking opportunities. In a stable market the tradeoff is acceptable. When opportunities are shorter and feedback is faster, it becomes expensive. Projects stall because no one is positioned to move first, even when the idea is sound and the approval chain is intact.

Who are the operators?

The useful distinction in 2026 is not foreign versus Japanese. It is institutional versus operational.

Operators include foreign professionals working here, Japanese people who have spent years working in other business environments, regional teams working outside Tokyo-centered structures, and small independent companies whose credibility comes from what they have delivered. What they share is a working habit. They act before they are validated, treat uncertainty as normal, make decisions with incomplete information, and change course quickly when the evidence says so.

That habit used to carry real penalties in Japan, because capital, distribution and credibility came through institutional membership. The penalties are smaller now. Cheap software, overseas customers and alternative funding reduce dependence on the traditional gatekeepers, so execution can come before permission. Institutions still matter, and operators still work with them where it makes sense. The difference is that the institutions no longer hold a monopoly on legitimacy.

Does pressure produce results?

A common response when results fall short is to demand more effort. Targets are set clearly, often ambitiously, but the conditions around them stay the same. Authority remains diffuse. Innovation is encouraged in speeches while deviation still carries career risk. New tools arrive without any change to the workflow they are supposed to improve. Responsibility is assigned without the authority to act on it.

Operators work from the other direction. Instead of demanding performance, they change the conditions. They remove steps, reduce the number of approvals a routine decision needs, and build processes that can run on partial information. The advantage does not come from individual brilliance. It comes from a system that makes progress repeatable, so the organization does not depend on a few people working late.

How do you turn a decision into working practice?

Execution happens in steps, and each step can fail quietly. These are the ones I see skipped most often in Japanese organizations of every size.

Name one owner

Consensus decisions often end without a person responsible for carrying them out. Give each decision a named owner who has the authority to change the process, not only to report on it. If the owner needs three more approvals to adjust a form or a system setting, the decision will stall.

Write down what changes

Record the decision in one place: what will be different, from when, and for whom. “We will reduce paper invoices” is an intention. “From next month, invoices go out as PDF from the accounting system, and the finance lead handles customers who insist on paper” is a change someone can carry out and check.

Change the tools and the process together

A new policy that leaves the old spreadsheet, the old approval route or the old fax number in place will lose to the old habit. Update the system settings, templates, forms and permissions at the same time as the instruction. I cover why technology purchases so often fail at this stage in Part 2.

Tell the people who do the work

Staff who carry out a process need to know what changed, why, and who to ask when something does not fit. A short explanation in their language, in the channel they already use, does more than a formal announcement they have to find.

Check after a few weeks

Set a date to look at whether the change is in use. Count the paper invoices still going out, or look at whether the old spreadsheet is still being updated. If the old way persists, find out why before calling the decision done. Often the new process has a gap that staff are filling with the old one. If the check shows the change itself was a mistake, treat that as a decision to stop rather than a reason to push harder, which I cover in deciding when to stop a project.

Why execution now creates credibility

In earlier decades, institutional approval came first and made action possible. That order is starting to reverse. Small teams that deliver something concrete attract partners, customers and resources faster than committees discussing what might be done. Evidence that something works is starting to count for as much as formal endorsement.

This does not mean ignoring regulation or local custom. Operators still respect both. The difference is timing: they do not treat consensus as a precondition for testing something. They test it, show the result, and use the result to build agreement.

What large institutions will still do well

Large Japanese organizations will keep providing stability, legitimacy and coordination across infrastructure, regulation and national programs. In sectors where reliability matters most, those strengths are necessary.

Stability without adaptation turns into stagnation, however, and coordination without experiment turns into delay. Institutions will still shape the environment and decide where large amounts of money go. They will no longer be the only place progress starts. Some small projects will quietly succeed while larger ones stall, and over time those comparisons change what people expect. The conversation moves from what should happen to what is already working.

Where to start in your own company

Pick one decision your company made in the last six months and check whether it is in use today. Who owned it? What changed in the tools and forms? Did the people doing the work hear about it? The answers usually show where execution breaks down in your organization, and they tend to repeat across decisions.

If you want help closing that gap, I plan and implement operational changes with your team: setting up the tools, changing the process around them and checking that the new way sticks. For companies that need someone to keep that discipline going, I also work as a fractional technology advisor.

Further reading: Part 0: where change starts to become visible · Part 2: why technology adoption stalls after purchase · deciding when to stop a project · Daikin, Elliott and the Japan Inc. value gap