This page is a solutions page that organizes what should be changed, what should be retained, and where to begin in response to the issue raised in “What Are the Risks of Failing to Recognize the Difference Between Japanese-Style Development Thinking and the U.S. Approach?” Rather than focusing on the surface introduction of systems, it explains how to redesign development philosophy, role definition, placement decisions, and performance indicators.
1. The Basic Perspective
Let us consider how to respond to the issue raised in “What Are the Risks of Failing to Recognize the Difference Between Japanese-Style Development Thinking and the U.S. Approach?”
The answer is not to reject U.S.-style systems, nor to preserve Japanese-style development as it is. What is truly required is to redesign the development system itself into a strategy-linked model, based on your company’s employment structure, HR system, assumptions behind evaluation, and approach to internal movement.
The first thing executives, managers, and HR need to share is this:
A system will not produce the intended results unless the context and assumptions that gave rise to it are also understood.
U.S.-style reskilling and job-based systems work because roles are priced, compensation is linked to role, and labor mobility is assumed. Many Japanese companies, by contrast, still operate on expectations placed on people, long-term employment, internal movement, and broad capability evaluation. As long as those assumptions differ, importing only the system itself will not produce the same results.
Therefore, the starting point of the solution is not system introduction, but understanding the actual operating context of your own company.
2. Stage One: Clarify Your Company’s Development Philosophy
In many companies, the development system operates largely through long-standing custom. There is OJT. There is training. There are internal transfers. There is support for obtaining qualifications. Yet in many cases, these are run without a clear explanation of what they actually exist to achieve.
The first issue to clarify here is which of the following your company is truly operating on:
- Do you develop people based on long-term expectations placed on them?
- Or do you develop the capabilities required for a defined role?
This difference is substantial. If the first is the premise, the logic is to build broad capability through a range of experiences and internal movement. If the second is the premise, the logic is to work backward from the roles required in the future and develop the needed capabilities in a focused way.
The problem arises when this distinction is never clarified, yet concepts such as U.S.-style reskilling or skill-based organizations are simply added on top. When that happens, people in the field no longer know what they are actually expected to learn toward. The number of systems increases, but motivation does not.
Therefore, the first thing required is to put your company’s development philosophy into words.
- Are you developing people?
- Are you developing role capability?
- If both, how are the weights between them actually set?
If this remains ambiguous, no system will truly take root.
And this is exactly where it becomes critical to understand the kind of talent your company expects not through impressions, but through structure. Who should be regarded as future core talent? What kinds of thinking traits, emotional traits, behavioral traits, and work values make someone more likely to fit both your company’s development philosophy and your strategy?
To avoid leaving that at the level of vague impressions, a perspective is needed that can examine a person’s inner structure from multiple angles, such as the 5D Profile Assessment, which looks at personality, emotions, thinking, behavior, and work values.
3. Stage Two: Break Down U.S.-Style Systems into Elements and Adapt Them
The reason reskilling and job-based systems draw attention is not that they are inherently superior. It is that they have the function of redesigning talent in response to changing business structures.
What Japanese companies should learn is not the appearance of the system, but the thinking behind it. In other words, they need to identify what should actually be adapted and brought in.
The key elements to adapt fall broadly into three areas.
-
First, the logic of designing development by working backward from the roles that will be needed in the future.
Traditional Japanese-style development has been strong at building capability for the work immediately in front of people. It has not always been strong at developing people by working backward from the roles required by strategy five or ten years from now. This is where change is needed. -
Second, the logic of connecting learning to role transition.
The fact that someone was trained should not itself be treated as the outcome. The real question is what role they became able to take on and what judgments they became capable of making as a result of that learning. -
Third, the logic of addressing not only skill, but also judgment standards.
What is required during strategic transition is not merely technical acquisition. Unless the organization also redesigns how people face uncertainty, set priorities, make judgments in conflict, and adapt to change, it will not produce true strategic talent.
In other words, what should be imported is not the system itself, but an understanding of the structure that makes that system work. Only when that is adapted to your own operating context does it become a mechanism that can function in practice.
This is the point where executives and HR usually run into the same wall: “How do we make judgment standards visible?” One effective response is to stop looking at people only through career history or skill, and instead examine them through thinking traits, emotional traits, and behavioral traits as well.
For example, capabilities such as the 5D Profile Assessment make it easier to see that even when two people possess the same skill, one may be more capable of adapting during a strategic transition, while the other may be more likely to preserve the existing order.
4. Stage Three: Evolve Japanese-Style Development into a Strategy-Linked Model
Japanese-style development has clear strengths.
- The ability to pass on tacit knowledge through OJT
- The ability to build expertise while doing real work in the field
- The ability to broaden roles while deepening understanding of the organization
These are not things that should simply be discarded. The problem is not that Japanese-style development is inherently weak. The problem is that its connection to strategy is often too weak.
Therefore, the solution is not to destroy Japanese-style development, but to evolve it into a strategy-linked model. In practical terms, this means connecting OJT, internal transfers, and training to questions such as the following:
- Which future role does this experience connect to?
- What kind of strategic execution capability is this training intended to strengthen?
- What kind of judgment experience is this internal move intended to provide?
- For which core function is this development candidate being prepared?
Once this becomes clear, development moves beyond “let’s give them experience for now.” The individual, the manager, and HR can all understand why the person is learning and why the person is being given certain experiences. This is the most practical way to keep learning from turning into a passing buzzword.
At this stage, however, it is no longer enough merely to ask, “Who should be given experience?” What is needed is the question: Because this person has these particular traits, why is it worth developing them as a candidate for that role?
If this judgment is made only subjectively, future core candidates will remain nothing more than “the people we somehow expect a lot from.” As a way of making that more objective, a multi-dimensional assessment such as the 5D Profile Assessment can be highly useful in identifying development candidates and improving placement decisions.
5. Stage Four: Change Performance Indicators to “Changes in Execution Capability”
In companies where reskilling fails to gain traction, the performance indicators are often wrong. Completion rates, participation rates, number of certifications obtained, and satisfaction scores are operational indicators. They are not indicators of strategic execution capability.
What should actually be observed are changes such as the following:
- Has the number of people capable of taking on new roles increased?
- Has the number of people capable of making the judgments required by strategic transition increased?
- Has the ramp-up time after reassignment become shorter?
- Are more people emerging who can bridge existing businesses and new businesses?
- Has the number of managers who can handle cross-functional conflict increased?
Unless these changes become visible, no matter how well the learning system is built, management will still be unable to see the return on that investment. On the other hand, once these changes become visible, development can finally be discussed not as a cost, but as a strategic investment.
The key shift here is to move the perspective from “Did they attend?” to “Did their behavior and judgment actually change?” To detect that change, it is not enough to evaluate skill acquisition alone. You also need to observe changes in thinking, emotions, behavior, and values. A mechanism that can examine the person from multiple dimensions, rather than through one-off skill checks, becomes important for confirming development effectiveness and reviewing the validity of placement decisions.
6. Stage Five: Design Separate Responsibilities for Executives, Managers, and HR
One reason this issue does not progress is that responsibility remains unclear. When “what HR should do,” “what the field should do,” and “what management should decide” are split apart, in the end no one actually owns the issue through to the end.
This must be separated clearly.
- The responsibility of executives is to decide which strategy to pursue and define which future roles and core functions will be required. In other words, they are responsible for deciding what should sit at the center of talent development based on the future business structure.
- The responsibility of managers is to decide, in light of those role requirements, who should be given what kind of experience, and how development should actually happen in the field. In other words, they are responsible for developing strategic talent through work itself, rather than separating development from daily operations.
- The responsibility of HR is to connect the strategy defined by management with the development required in the field, and implement that as systems, placement, evaluation, and development measures. In other words, HR is responsible for turning philosophy into systems, and systems into operation.
Only when these three groups can speak in the same language do strategy and talent begin to move together.
This is where a mechanism such as the 5D Profile Assessment becomes useful. It shifts the conversation among these three groups from impression to structure. Executives can more easily see the connection to strategy, managers can more easily distinguish differences among development candidates, and HR can more easily align placement, development, and evaluation.
The purpose is not the assessment itself. Its value lies in providing a common basis for discussion among the three groups.
7. Conclusion: The Solution Is a Shift in Design Philosophy, Not Simple System Introduction
Ultimately, what Japanese companies need is not a copy of U.S.-style systems. What they need is to evolve Japanese-style development into a strategy-linked model.
- Are people priced, or are roles priced?
- Is internal movement assumed?
- Is expertise developed in fixed tracks?
- How far should job-based logic be introduced?
- How much of the Japanese-style model should be retained?
If a company introduces systems without having its own answer to these questions, those systems will inevitably become hollow. On the other hand, if the company can decide what to change and what to retain based on its own operating context, systems can become a real management tool.
In that sense, the real question is not whether the company is good or bad at introducing systems. The real question is whether the company is willing to redesign its own philosophy of talent in line with strategy.
And to turn that redesign into something that works in practice, the company must be able to answer structurally:
- What kind of people are we actually looking for?
- Which people are more likely to fit which roles?
- Who should be developed, and in what order?
One realistic way to make that concrete is to incorporate a multi-dimensional assessment such as the 5D Profile Assessment.
The solution to this issue is not to import U.S.-style systems. Nor is it to reject Japanese-style development. What is required is to redesign development into a strategy-linked model, based on your own employment structure, HR system, and evaluation assumptions.
The question is not whether people attended training.
The question is whether the organization was actually able to use them in more strategic ways.
The metric is not participation rate.
The metric is whether strategic execution capability changed.
Systems can be imported, but results cannot. However, once the underlying structure is understood and redesigned to fit your own operating context, the system can finally begin to produce real outcomes.
And once that redesign does not end as a desk-level concept, but includes a mechanism to make people’s structure visible, assess their fit with roles, and turn development and placement into concrete action, then reskilling, skill-based organizations, and job-based logic stop being buzzwords and become real management tools.
As one practical method to support that shift, the 5D Profile Assessment is well worth serious consideration. That is because it helps organize the real question at the heart of strategy-linked development: “Which person should be developed for which role, and how?” It does so through five perspectives: personality, emotions, thinking, behavior, and work values.
Only when the logic is connected this far does the system stop being just a system and begin to turn into management results.
What to Confirm First
The first step is not to add more systems. It is to confirm the following three points.
- Can your company clearly state whether it is developing people, developing role capability, or both?
- Have you defined the roles required by your strategy five or ten years from now, and the kind of candidates who could fill them?
- Are you evaluating development results through changes in strategic execution capability rather than participation rates?
If these three points remain unclear, then before introducing any new system, the organization needs to begin by organizing its development philosophy, role definitions, and judgment standards.