Professional Documents
Culture Documents
Policy Deployment
Policy Deployment, as the Western translation of ‘hoshin kanri’, the Japanese strategic planning
and management process involving setting direction and deploying the means of achieving that
direction, with appropriate involvement at all levels of the organizational hierarchy. The chapter
reviews the history and concept of policy deployment and proposes a policy deployment model.
It is argued that this model will enable an organization to deploy, in an effective manner, its
vision, mission, goals, objectives, targets and means.
‘Policy Deployment within a process of long-term planning is one of the features of “the
approach” to Total Quality Control (TQC) by Japanese companies’, Dale (1990). He described
the deployment of the president’s annual management policy plan through the levels of the
organizational hierarchy. The process involves developing plans, targets, controls and areas for
improvement based on the previous level’s policy and an assessment of the previous year’s
performance. The plans and targets are discussed and debated at each level until a consensus
on plans and targets is reached, along with the methods for meeting the goal.
The following are the main characteristics which emerge from this discussion of policy
deployment definitions:
Clear organizational goals understood by employees from each level of the organization.
Involvement of employees in the development of action plans.
All employees and functions are working in the same direction to achieve the
organization’s objectives.
Regular review mechanism using the PDCA cycle thereby promoting an environment of
continuous improvement.
Visible display of information.
Leadership
Communication
Control
Review
And that there are four stages:
Policy-setting
Policy deployment
Policy implementation
Evaluation and feedback
Policy deployment is not a solution to all planning problems but a process which enables
managers to plan effectively and translate those plans into actions. Furthermore, although
Integrated Quality Dynamics (1997) consider the description of hoshin kanri as policy
deployment as ‘not the best translation’ (they describe hoshin as a one-year plan with targets
and means and state that hoshin management is not only ‘deployment’), their ‘myths’ are worth
repeating:
In the literature on policy deployment there is consistent reference to cascade and catch ball as
essential elements. However, based on research and practical experience, deployment is the
area where management can have the most impact but often fail to deliver what is necessary.
The cascade processes
Essentially, CRISP entails each individual and team catching the policy, reflecting and
improving upon it, but, before passing the policy up and down the hierarchical chain, having
their work scrutinized by the previous level to ensure the reflection and improvement are in line
with the original. This is the all-important ‘check’ aspect in the PDCA cycle which often does not
occur in an organization’s deployment process. Although, at first sight, this approach may
appear to add unnecessary bureaucracy to policy deployment and extend the process time-
frame, the addition of scrutiny does not have to be viewed as a burden, because the CRISP
approach has the following advantages: often does not work because line managers fail to
communicate with their teams in an effective manner due to lack of time, skills or management
style.