When Does It Make Sense to Digitalize Hoshin Kanri?
Digitalizing Hoshin Kanri is often framed as a technology decision. In practice, it is usually a management system maturity decision. Based on our experience of digitalizing Hoshin at hundreds of organizations over the years, we have learned that organizations generally arrive at digitalization through one of two paths.
Operational Frustration
The first is operational frustration. These organizations have often used Hoshin Kanri for years, sometimes successfully, but primarily through spreadsheets, PowerPoints, and manually maintained reporting structures. Initially this works reasonably well. A small leadership team can coordinate objectives, projects, and KPIs without major difficulty.
The problems emerge gradually as adoption expands. Different business units begin modifying templates, therefore, over time, KPI definitions diverge. Multiple versions of the same X-matrix start circulating simultaneously. Project updates are reported inconsistently. Management review preparation becomes increasingly focused on reconciling information rather than discussing decisions. Teams no longer know which version is current, when data was updated, or whether KPIs are comparable across units.
At this stage, the issue is no longer the Hoshin process itself. The issue is that the information architecture no longer supports the organizational complexity. In these situations, digitalization is less about introducing new management practices and more about stabilizing existing ones. The organization already understands Hoshin Kanri conceptually. What it lacks is consistency, visibility, traceability, and governance at scale.
Selective implementation
The second path is different. Some organizations have experimented with Hoshin Kanri only in selected business units or leadership teams. They may have seen positive results locally and now want to expand the approach across the organization. Here, digitalization is not primarily driven by frustration, but by the desire to avoid fragmentation before it emerges.
These organizations recognize an important point early: scaling Hoshin Kanri through disconnected spreadsheets often leads each unit to developing its own interpretation of objectives, KPIs, review cadence, and reporting logic. Over time, the organization ends up with multiple parallel versions of Hoshin rather than a shared management system.
For them, digitalization becomes a mechanism for standardization. Not to eliminate flexibility, but to create a common governance structure from the beginning. Objectives are defined consistently. KPIs follow common logic. Review processes become repeatable across units. Alignment becomes easier to maintain as adoption grows.
When to digitalize?
At the same time, digitalization is not always the correct starting point. Organizations sometimes attempt to digitalize before they have developed even a basic understanding of how Hoshin Kanri should function operationally. In these cases, software risks becoming a substitute for management thinking rather than an enabler of it.
This is particularly common when organizations are still experimenting with Hoshin Kanri itself. If leadership is uncertain whether the methodology fits the organization, introducing a formal system too early can create unnecessary rigidity. Teams begin focusing on templates, workflows, and tool usage before the underlying management process has stabilized.
In such situations, simpler approaches are often better. A limited pilot using spreadsheets or lightweight structures may provide enough learning initially. The objective at this stage is not optimization, but understanding: how objectives are defined, how catchball works, how reviews are conducted, and whether the organization has the discipline required to sustain the process.
Digitalization becomes valuable once the organization reaches a different question. Not “Should we use Hoshin Kanri?” but rather “How do we scale and govern it consistently?”
This distinction matters because digitalization inevitably shapes behavior. Systems introduce structure, visibility, and process discipline. They standardize how work is planned, reviewed, and communicated. That is precisely why they become powerful once the organization is ready.
The mistake is assuming software creates management maturity on its own. In reality, digitalization works best when it reinforces a management process that leadership already understands and supports.
Amplon is designed around this principle. The objective is not simply to replace spreadsheets, but to create a consistent and scalable strategy management system. For mature Hoshin organizations, this means reducing fragmentation and improving visibility. For organizations preparing to scale Hoshin company-wide, it means establishing common governance before inconsistency becomes embedded in the system.
Conclusion
Digitalizing Hoshin Kanri is not automatically the next step for every organization. The right timing depends on where the organization is in its management system maturity journey. For some, digitalization solves growing complexity and inconsistency. For others, it provides a scalable foundation for broader adoption. But organizations still learning the fundamentals of Hoshin Kanri may benefit more from experimentation than formalization. The technology becomes valuable when the challenge shifts from understanding the method to managing it consistently at scale.
We’ve been using the Amplon X-matrix tool for our 500-person organization over the past two years. It has significantly enhanced clarity. Now, we have an easily accessible clear view for everyone of our long-term goals, annual objectives, and development topics both at the organizational level and within each activity.
Moreover, the Amplon team’s responsiveness and support have been outstanding. Overall, Amplon X-matrix has been an invaluable asset for our organization.
Ari Hyvärinen,
ABB Drives Oy
Projects represent the deliberate work undertaken to influence those outcomes. A useful way to think about projects in the X-matrix is to ask whether they materially advance the strategy. Some initiatives accelerate the current direction, such as scaling a successful product line or improving a pricing model to strengthen margins. Others enable a shift in direction by creating new capabilities, such as implementing a digital platform, building a new distribution channel, or redesigning a key operating process. What these initiatives have in common is that they change something meaningful about the organization’s trajectory.
A defining characteristic of a good project in the X-matrix is that it has a clear deliverable. Completion should correspond to a tangible outcome: a system implemented, a capability established, a product launched, or a process redesigned. This clarity prevents initiatives from becoming open-ended activities and allows teams to understand when strategic work has actually been completed.
