Friday, 21 November 2014

CQM - Handbook Chapter 5: Strategic Planning Models

What is strategic planning?
Organization's strategy defines what it strives to become and the means by which it will achieve it. It provides choices, which, guide in determining the nature and direction of an organization.
It provides consistency in behavior over time.  It is a continuous process of making present organizational decisions systematically and with the greatest knowledge of their futurity, systematical organizing the efforts needed to carry out these decisions and measuring the results of these decisions against expectations through systematic feedback.

What's the difference between long range planning and strategic planning?
Long range planning = extrapolating future plans based on current work.
Strategic Planning = Develop the vision for future, plan for near term, and address the future needs as envisioned.

Baldrige Performance Excellence Program describes strategic planning as the process that addresses strategic and business planning and deployment of plans with strong focus on customers and operational performance requirements.

End result of the strategic planning process is a strategic plan which communicates the organizational priorities throughout the enterprise. A road map on how to get to specific targets. It is affected by various internal and external forces. Alignment and integration of individual departmental strategies is important aspect of strategic planning.

Traditional Strategic Planning Process:
It has three stages: Strategic (or formulation) , Tactical and Operational (combined as operational). Deployment is a typical shortfall of this type of process.

Hoshin Planning:
Starts with vision and mission statement. Some organizations use guiding principles which are values which help establish and define the organizational culture. Goals are established after the environmental analysis. It uses a matrix involving Means (i.e. tasks or how one would achieve the stated objective), multi year objectives, responsibility, resources, measures and timeline. Results from the first year feeds into the next cycle of hoshin planning. Involvement of entire organization remains the single most troublesome area when it comes to Hoshin deployment.

Scenario Planning
The helps compensate for the usual errors in decision making such as over confidence and tunnel vision.

Overall when priorities and strategies are unclear, people do not know what to aim for or what to do.

10 most common pitfalls of planning are:


  1. Delegation of planning function by top management. 
  2. Current problems take over management's time and attention away from long range planning.
  3. Failure to plan properly
  4. Failure to involve everyone
  5. Failure to manage performance against the plan
  6. Failure to create supportive environment for the success of the plan
  7. Siloing
  8. To make process to formal
  9. Failure to review
  10. Failure to follow the plan





Tuesday, 8 November 2011

Run Chart Rules! - What you need to know about run charts...

Run chart can be used to detect any nonrandom process behavior. Data for run chart is plotted sequentially with a reference line called median. In Minitab, Run chart can detect oscillation, clustering, mixtures and trends by the two tests for nonrandom behavior.

There are four rules you can apply to validate if an improvement is the endresult of any changes you made to the process.

Rule one: shift.

This rule is in force when there are six or more consecutive points either all above or all below the median. Skip values that fall on the median  because value that fall on the median neither add to nor break a shift. 

Rule two: trend.

This rule is in force when there are five or more consecutive points all going up or all going down. When using this role, ensure that you are not counting points which as same values.

Rule three: number of runs.

This rule is in force when there are too few or too many runs. Determine the
number of runs by counting the number of times the line connecting the data
points crosses the median and add one.

Rule four: astronomical point.

These are the data points which are unusually high or low in value compare to other values. Don't get confused with the regular high and low end of the run chart points.

Sunday, 31 July 2011

Use carrot-and-stick approach to coax fractious team on project

Change Management in Action - From Leader-post colum.

QUESTION: My company has a “make or break” project that I’ve been assigned to lead. The problem is that there are two factions with strong interests in this project and they don’t agree on the direction we should take. How can I get them to come together? ANSWER: Try a carrot-and-stick approach. What’s in it for them if they compromise? What’ll it cost them if they don’t?

Success will depend on keeping the collective benefit from this project front and centre despite pressure from both sides, and will require great effort on your part. Start by listing your strengths, including tangibles such as organizational, communication, and negotiating skills, and intangibles such as resilience and determination. Other people who can provide knowledge and support, and who may have leverage over people in the two factions are also assets.

Then create a road map of successes, starting with your ultimate project goal. How will this project benefit your company as a whole? This will give you the “greater good” perspective that you’ll need. Then look specifically at the ways that subgroups within the company will be affected to help you build a case that will support forward movement for both parties. Working backward, establish a set of intermediate successes that will help you bring the parties together toward the collective goal.

Develop an equally clear statement of the risks of failure, including multiple perspectives — the whole organization, departments within the organization, and the individual employees.

Finally, list as many “derailers” as you can think of, their likelihood, and ways around them. Involve some of your allies to help develop as complete a view as possible.
Plan to work with each group separately when needed, bringing them together when you’ve found even small bits of common ground. Your starting point may have to be very high-level; for example, “We are committed to our company’s financial stability.” Then work with them to define the ways that this project supports that goal. Be direct if they appear to be putting their factional benefit ahead of the common good; remember that you’re holding the line on behalf of the company, so be resolute.

As you achieve areas of agreement, build on them to develop specific action strategies. You may find that the sides have made some tactical retreats and are putting up barriers at a new level. Continue to call this out so that covert disagreements don’t fester. Try having them advocate the other’s position to increase their understanding.

Use escalation and visibility as tools, when needed. If resistance doesn’t look substantive — and is made public — co-operation can magically appear. Just be sure that you’re being neutral rather than taking sides, so that you don’t undermine your credibility. Your project’s executive sponsor should take an active role in resolving disagreements, and a council of leadership with authority over the factions (and agreement on the project) may also help.

Be clear on the benefits of success and costs of failure, cajole when appropriate, be blunt when necessary, and be in it for the long haul — these will build your chances of bringing these groups together.

Liz Reyer is a credentialed coach with more than 20 years of business experience. Her company, Reyer Coaching & Consulting, offers services for organizations of all sizes. Submit questions or comments about this column at www.deliverchange.com/coachscorner or email her at liz@deliverchange.com.