Redesign Your Development System into a Strategy-Linked Model That Fits Your Company

1. A Basic Perspective on the Issue

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 to this issue is not to reject U.S.-style systems, nor to preserve Japanese-style development as it is.

What is truly needed is to redesign the development system itself into a strategy-linked model, based on your company’s employment structure, HR system, evaluation assumptions, and approach to internal movement.

The first point executives, managers, and HR need to share is this:
A system will not produce the intended results unless the background, assumptions, and purpose that gave rise to it are also understood.

U.S.-style reskilling and job-based systems work because roles are priced, responsibility and compensation are linked, and labor mobility is assumed. There is a market-based logic and a level of evaluation precision behind the idea that “if you build the skill, you will be rewarded.” By contrast, many Japanese companies still operate on assumptions of expectations placed on people, long-term employment, internal transfers, and broad capability evaluation.

As long as these assumptions differ, introducing only the system itself will not lead to the same outcomes.
That is why the starting point of the solution is not “system introduction,” but understanding your own company’s environment correctly.

2. First, Clarify What Your Company’s Philosophy of Development Is Based On

In many companies, the development system operates 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 articulation of what they actually exist to achieve.

The first thing to organize here is which of the following your company is actually based on:

Do you develop people based on expectations placed on them?
Or do you define the capabilities required for a role and then develop those?

This difference is substantial.
If the first is the premise, the logic is to build broad capability through a variety of experiences and internal movement.
If the second is the premise, the logic is to work backward from the future roles required and develop the capabilities needed for those roles in a focused way.

The problem arises when this distinction is never clarified, and yet concepts such as U.S.-style reskilling or skill-based organizations are simply layered on top. When that happens, people in the field no longer know what they are expected to learn toward. The number of systems increases, but motivation does not.

Therefore, the first thing required is to put your company’s philosophy of development 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 what matters here is understanding the kind of talent your company expects not through intuition, but through structure. Who should be regarded as future core talent? What kinds of thinking tendencies, emotional traits, behavioral traits, and work values make a person more likely to fit both your company’s philosophy of development and its strategy?

To avoid leaving this at the level of vague impression, what is needed is a way to grasp that internal structure from multiple angles, including personality, emotions, thinking, behavior, and work values.

3. Do Not Introduce U.S.-Style Systems “As They Are”—Break Them Down and Adapt Them

Reskilling and job-based systems attract attention not because they are inherently superior.
They attract attention because 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 elements that need to be adapted fall broadly into three areas.

First is 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 making people more capable in the work directly in front of them. 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 is the logic of connecting learning to role transition. The fact that people were trained should not itself be treated as the outcome. The real question is which roles they became able to take on, and what judgments they became able to make as a result of that learning.
Third is the logic of dealing not only with skill, but with judgment standards as well. What is required in a period of strategic transition is not mere technical acquisition. Unless the organization also redesigns how people face uncertainty, set priorities, judge during conflict, and adapt to change, it will not produce 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. Once that is adapted to your own environment, it becomes a mechanism that can function in practice.

This is 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 understand them through thinking traits, emotional traits, and behavioral traits as well.

For example, a capability such as the 5D Profile Assessment makes 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 inclined to preserve the existing order.

4. Preserve the Strengths of Japanese-Style Development While Turning It into a Strategy-Linked Model

Japanese-style development has clear strengths.

The ability to pass on tacit knowledge through OJT
The ability to deepen expertise while working in the field
The ability to broaden roles while deepening understanding of the organization

These are not things that should be discarded lightly. 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 transfer 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 realistic way to keep learning from turning into a passing buzzword.

At this stage, however, it is no longer enough to ask only, “Who should be given experience?” What is also needed is the question: because this person has these particular traits, why is it worth developing them as a candidate for that role?

If that judgment is made only subjectively, future core candidates remain nothing more than “the people we somehow expect a lot from.”

As a way to make that more objective, a multi-dimensional assessment such as the 5D Profile Assessment is highly useful in identifying development candidates and improving placement decisions.

5. Do Not Measure by Participation Rate or Number of Certifications—Measure by Changes in Strategic Execution Capability

In companies where reskilling fails to gain traction, the performance indicators are often wrong.
Participation rate, completion rate, number of certifications obtained, satisfaction scores. These are operational indicators, 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. By contrast, once these changes become visible, development can finally be discussed as a strategic investment rather than a cost.

What matters here is shifting 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 makes the person visible from multiple dimensions, rather than through one-off skill checks, becomes an important factor in confirming development effectiveness and reviewing the validity of placement decisions.

6. Design Separate Responsibilities for Executives, Managers, and HR

One reason this theme 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.
These responsibilities need to be clearly defined.

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 day-to-day 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, because it shifts the conversation among these three groups from “impression” to “internal 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 giving the three groups a shared basis for discussion.

7. The Solution Is Not System Introduction, but a Shift in Design Philosophy

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 transfer 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 environment, systems can become a powerful management tool.

In that sense, what is really being tested 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.

To turn that redesign into something that works in practice, the company must be able to answer structurally:

“What kind of talent are we actually looking for?”
“Which people are more likely to fit which roles?”
“Who should be developed, and in what order?”

To answer those questions structurally, a multi-dimensional approach is necessary.
As one practical way to make that concrete, incorporating a multi-dimensional assessment such as the 5D Profile Assessment is a realistic option.

8. Conclusion

The solution to this issue is not to import the U.S. model. Nor is it to reject Japanese-style development.

What is needed is to redesign development into a strategy-linked model based on your company’s employment structure, HR system, and evaluation assumptions.

The question is not whether people were trained. The question is whether the organization was able to use them more strategically.
The metric is not participation rate. The metric is whether strategic execution capability actually changed.

Systems can be imported, but outcomes cannot.
However, once the underlying structure is understood and redesigned to fit your own environment, the system can finally begin to produce real results.

And once that redesign does not end as a desk-level concept, but includes a mechanism to make people’s structure visible, assess fit with roles, and turn development and placement into concrete action,
reskilling, skill-based organizations, and job-based logic stop being buzzwords and become 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?”— through five perspectives: personality, emotions, thinking, behavior, and work values.

Only when it is connected this far does the system stop being just a system and begin to turn into management results.