Difference between revisions of "Hoshin Kanri"

From AardRock Wiki
Jump to navigation Jump to search
(Initial version.)
 
(#REDIRECT parel:Hoshin_Kanri)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Hoshin Kanri has its roots in the 1950s when lectures by Dr. Deming and Dr. Juran in Japan taught the Deming Wheel (PDCA Cycle) and the need to focus on management processes for continuous improvement, including both '''Breakthrough Management''' and Daily Management.
#REDIRECT [[parel:Hoshin_Kanri]]
 
Hoshin Kanri is an organising framework for strategic management. It is concerned with four primary tasks:
*it focuses organisation attention on corporate direction by setting, annually, a vital few strategic priorities;
*it aligns these with local plans and programmes;
*it integrates them with daily management, and
*it provides for a structured review of their progress.
 
It became a more formal process within Japanese companies during the 1960s and 1970s. Utilizing forms, clear accountability, and review meetings structured many management processes.
 
More and more companies recognized its value over the 30 years of refinement. Today, '''[http://en.wikipedia.org/wiki/The_Toyota_Way The Toyota Way]''' resonates well with the practices of '''Agile Software Development'''. Joined with '''[[holacracy|holacratic]] principles''', government and practices it grows into a very effective leadership instrument.
 
Hoshin Kanri is part of the management process that helps to '''align the organization toward the most important strategic goals'''.
 
There is only surface understanding of Hoshin Kanri. Many of the enthusiasts of Toyota Production System (TPS) tools know something about '''[http://en.wikipedia.org/wiki/Kaizen kaizen] events''', implementing standardized work or pull systems, but Hoshin Kanri is often a lessunderstood term on the list, or is a chapter in a book on Lean or TPS that is glossed over.
 
After all, many companies start their lean journey with kaizen events without a real strategic direction. They might have incorporated some of the "tools" into their implementation efforts, but you don't often hear someone say they conducted a "Hoshin Kaizen".
 
Interestingly, you don't have to be using TPS principles or implementing Lean or Six Sigma to use Hoshin Kanri, as the process is one that provides structure to strategy execution independent of choice of methods used to execute.
 
'''Hoshin''' means “'''compass''', or pointing the direction,” and '''Kanri''' means “'''management''' or control”. Combined, these two words show that  Hoshin Kanri is essentially the process for '''Strategic Direction Setting'''.
 
One of the interesting parts of a Hoshin Sheet is the fact that you can provide in such a management compass on a comprehensive single sheet of paper.
 
===Links===
*[http://www.iwchallenge.com/0107/images/Jan07WhitePaper.pdf An Introduction to Hoshin Kanri], a.k.a. Strategic Goal Deployment—How To Use this Process to Deploy Your Strategic Goals, By Pete Winiarski, Win Enterprises, LLC
*[http://en.wikipedia.org/wiki/The_Toyota_Way The Toyota Way]. Wikipedia.
*[http://www.si.umich.edu/ICOS/Liker04.pdf The 14 Principles of the Toyota Way]: An Executive Summary of the Culture Behind TPS.

Latest revision as of 16:01, 3 October 2007

Redirect to:

Retrieved from "https://wiki.aardrock.com/index.php?title=Hoshin_Kanri&oldid=7379"