X-Matrix Hoshin Kanri

Abstract

X-Matrix is a powerful tool from Hoshin Kanri that sums up in a single document the strategies, tactics, processes, and people involved in the achievement of a project success. It is a dynamic tool and the process results, financial impacts and cost could be recorded during the project execution. The main aim of this tool is to help project manager in the communication of the project stages to the internal team and stakeholders. Moreover, it provides a visual explanation of how the different steps are correlated and how they contribute to the project success. The implementation of this simple tool in the planning phase of a project and its subsequent monitoring during the implementation stage makes it easy to align plans and goals between each team within the organization. Considering that in the practice, most of the project's failure relies on not investing enough time and resources in the communication of project scope and goals, the importance of such a tool is undeniable. This article provides a brief introduction to the Hoshin Kanri methodology. Then the X-Matrix, the structure will be explained, following by possible variants according to the application field. Finally, the advantages and disadvantages of its application will be discussed.

Hoshin Kanri

Hoshin Kanri is formed by the two Japanese ideograms Hoshin (policy) and Kanri (management). The term policy managemen doesn’t reflect the meaning and purpose of Hoshin Kanri, which mostly is organizational learning method and competitive resource development system<ref. Hoshin Kanri was developed in Japan, to address the Japanese Industry's need for change in structure in order to be competitive in a global dimension. The term Hoshin Kanri has been used for the first time by Bridgestone Tire in 1964 and since 1980 the methodology has been adopted worldwide. Hoshin Kanri could be applied to reach different goals: manage complexity, launch a new product, manage strategic change within the organization. Moreover, it is also used to manage projects and programs, especially the ones which require cooperation between organizational functions.

Hoshin Kanri systematically applies Deming Cycle (PDCA) at each organizational level. Usually, a Scan stage of the current situation is carried on before the DO stage: Thus, PDCA becomes SPDCA. Furthermore, the stages are shared and nest within the company, as can be observed in the right figure below, and usually the teams are cross-functional. As result, strategy and goals are shared and every single worker is involved in kaizen (continuous improvement).

X-Matrix implementation and structure

Considering the application of Hoshin Kanri methodology to project management, the X-Matrix tool is implemented in the Plan stage. It could be seen both as a memorandum for the hoshin team (the team that set the project scope), and a visual tool to communicate and align the plans at each organizational level. The Matrix is divided into four blocks, that could be called also dials, linked by four correlation matrixes. Starting from the left block (the “east” block) and proceeding clockwise, it is possible to identify the four main dials: Strategies, Tactics, Processes and Results. In addition, People block is to the right side of the Process ones. Each of the block is linked to the following one by a correlation matrix, that will be explained later in the article.

The idea behind the tool is that a project scope could be split up into goals. The goals’ achieve-ment determines project success. The 100% rule, set by the Project Management Institute (PMI) for WBS, states that “‘the next level of decomposition of a WBS element (child level) must repre-sent 100 percent of the work applicable to the next higher (parent) element’’ (Guide, A. "Project Manage-ment Body of Knowledge (PMBOK® GUIDE & STANDARD)." Project Management Institute. 2001.  ; Haugan, Gregory T. 2002. Effective Work Breakdown Structures. Vienna, VA Management Concepts). Following a similar approach, each goal could be braeken down into lower-level goals. Each goal will be part of one of the following categories in decreasing level order: Strategic and Tactical and Process goal. Performing carefully this decomposition is vital for the project success and for the correct imple-mentation of the X-Matrix.

Strategies block

The Strategies Block is the mover of the entire X-Matrix and it is the first that should be filled up. The strategic goals are the first level of scope decomposition and each of them should be inserted into a row in the strategies block. The strategic goals must be expressed in general terms and, at the same time, they should clearly communicate the direction of the entire project. Each strategic goal will occupy a row in the strategies block. It is suggested to limit the number of strategic goals to avoid excessive complexity in the next steps. Ex : Considering a company that want to simplify the on-line sales project by implementing a new webpage. The main scope of the project is to design efficiently the web page and make it accessible to the customer. The scope could be split into strategies: design a page with a simple code, upload the products and make them visible, design a purchasing process easy to use for the customers.

Tactical Block

For each row in the strategies block, a set of tactical goals should be written down. A set of tactical goals is much more detailed than the related strategic goal, and clearly shows the action to be implemented to achieve it. As in the previous block, each row in the block contains one tactical goal. This block is linked to the strategic and processes ones by a correlation matrix. Moreover, each tactic is assigned to a person or a team. The responsible for each tactical activity can be found consulting the assignation matrix that linked the strategy dials with the people ones. Ex: the strategic goal “design a process easy to use for the customers” could be split into : create an initial interface with the different product category, in each page include the same features, include always a direct link to the basket, design a easy to use payment process, include a BOT to answer customer’s questions etc etc.

Processes Block

Each row in the processes block show a detailed action needed to achieve a tactical goal. The start and finish date and an estimation of the cost must be included for each process. It is allowed just one performance indicator for each process. This one must be pertinent and easy to measure. Ex: For this project some valuable processes could be “divide the product into categories (next week)”, “write the code for a standard page within 1 month” “generate a 3D imagine for each product and upload it within 1 month”.

Results Block

The scope of a project should be converted into measurable results. Each result will occupy a row in this table. In the most of the case the costs and revenues from project success are registered. Anyway it is not a limitation, each result address to be specific, measurable,