Continual Improvement or Continuous Improvement?

Is your organisation involved in Continual Improvement or Continuous Improvement?   In the context of IT Service Management, many professionals interchange these quality management terms. However, there is a significant difference between the two terms when it comes to improving our management practices, and providing excellent customer service.

Continual Improvement is more about planning and implementing strategic programmes to change the company's products, services, people and processes for the better.  Whilst Continuous Improvement is related to the constant, daily work practices and staff activities that are relentlously devoted to removing wasted effort and ellimitating defective products, services and processes.

Customer, Client or Consumer

We all have a reasonable grasp of the meaning and use of the words "customer", "client" and "consumer", and we often interchange them in our conversations and documents.

However, from a Service Management perspective, there is a difference that IT service management professionals should be clear about. Why is this important?

Quality Management Ghostbusters

Do you want to get rid of the demons in your quality management system?    Who you gonna call? 

Scenario:  You've just seen the monthly customer feedback reports, and they are not pretty. Furthermore, two more clients have flagged their intentions to drop your services.

In times of need these days, most organisations would keep the phone number of their corporate Six Sigma Black Belt guru handy (magnetic tag on the staff room fridge maybe). But wait a minute, do you really need another analytical deep dive into your problem tickets, financial data or other performance metrics.

Maybe the real demons are with your quality management system.

You Can't Improve A Process You Don't Have

Process Improvement hinges on end to end analysis and value mapping of existing support  and delivery processes.  An improvement project would wisely commence with the most critical and the high impacting, "broken" or defective processes.  A  Pareto Analysis  could help with that.

Sadly, the challenges of improving your company's core processes are daunting if they are not defined.  ISO 9000 gives us the terminology and management guidance to define, document and clearly articulate exactly what our processes are.

To put it bluntly - If your core processes are not clearly documented, accurate, relevant, current, and available to all your support staff,  then you don't have any processes  to improve.

Selecting a Web Hosting Company

Recently I updated my blog on Web Design with a review I came across called the Top Ten Best Web Hosting Companies of 2013.  I know the title sounds a bit presumptuous, but was worth some merit due to the thoroughness and scope of the content.

You need to login to read our blogs and other material, but I'd thought I'd share my personal views and experience when it comes to selecting web hosting companies.

Problem Solving Model

I suspect many of you are familiar with several, if not many tools available for solving product defects and process problems (from Lean, Six Sigma and TQM).  Statisical Process Analysis, 5 Why's, Fisbone charts and RCA come readily to mind. The ISO 9000 component  on Preventative and Corrective Action offers another, complimentary tool for problem solving.

The value of having a wide range of tools and methods to tackle defects and solve problems becomes clearer when we realise that in the real, customer driven and competive markets of today, the nature of problems and defects are moving targets.  Don't fall for the common trap of setting your company's problem management processes in concrete.


Site maintained by the QualityHelp Community