Skip to main content

The 80/20 Rule

If you've been in Tech Support or Help Desks for any length of time - especially from a management perspective you'll be extremely familiar with something called the 80/20 rule.  

Put simply it implies that 80% of your calls/contacts are generated from 20% of your issues.  If you are able to focus efforts on clearing up some of those 20%'ers you would have a significant impact on the overall volume that is coming in to your center (note, once you've fixed the 1st 20% - then you can do a similar analysis on the next batch and so on!).  

Now, while this is true from an "on the floor" perspective there has actually been a study done on this and this "rule" is actually known as the Pareto principle (sometimes also called the "law of the vital few" or the "principle of factor sparsity ).  While these names all sound really fancy - I think the 80/20 Rule is most descriptive of what it is.

The principle was actually suggested by Italian economist Vilfredo Pareto.  Vilfredo observed that in 1906 80% of the land in Italy was owned by 20% of the population.  Surprisingly for Vilfredo Pareto he observed a similar distribution among other countries and as such developed this guideline.
  • More recently, this was seen in a 1992 UN Report that showed that 20% of the world's population actually controlled 82.7% of the world's income!
  • Microsoft also noted that by fixing the top 20% of the most reported bugs, 80% of the errors and crashes would be eliminated.
  • The Pareto principle was a prominent part of the 2007 bestseller The 4 Hour Workweek by Tim Ferriss which I have mentioned in a previous post As Tim Ferriss recommended, by focusing your attention on those (20%) factors that have the greatest impact to your income (80%) you will obtain and receive a greater "bang for your buck!"

So as you can see, some significant analysis has gone into determining whether or not this "rule of thumb" actually applies and while its not always 80% on the dot, it is close enough for you to use in determining what you should be looking at from a management perspective.

You can really think about the 80/20 rule from two different directions. 
  1. What are the negative impacts that you need to address.  As I've mentioned earlier, 20% of your issues are probably causing close to 80% of your interactions with your customers.
  2. 20% of your customers are also probably spending the most (80%) with you!  
  3. 20% of your employees are also probably the most (80%) productive! etc...
Dealing with the first option is reasonably easy - hopefully you can categorize your interactions with your clients utilizing any half way decent CRM system.  Once you know why you are being contacted, sort it out to see how many of each type (you should be doing this anyways!) and start with the top 20 types of problems.  
  • Are there any of them that you can address by providing better documentation to your customer so that they do not need to contact you in the first place?  
  • Is there something that you can and should do to fix your product so that they do not need to contact you?  
  • How about updating your FAQs and other setup information?  These are all simple and easy fixes and by doing them you'll make an immense impact on your bottom line.
Measuring & Dealing with the second should be even easier ... if you do not know who you top 20 biggest customers are ... SHAME ON YOU! ... they are your bread and butter and you should ensure that you are on extremely good terms with them.  

The same applies for your #3 of course - your staff themselves.  Reward your high performers with raises/bonuses and other perks.  These are the people that keep the ball rolling and I've mentioned previously the impact of losing highly trained staff have on a business.

Best of luck using the 80/20 rule in your business ... its a good one - keep it close to heart!
Post a Comment

Popular posts from this blog

The Difference Between Incident Managment and Problem Management

Incident Management and Problem Management are both key components of the ITIL service model and have been defined and created in an effort to provide a better and more streamlined service to consumers.
ITIL itself stands for the - Information Technology Infrastructure Library - and comprises of the following books:
ITIL Service Strategy ITIL Service Design ITIL Service Transition ITIL Service Operation ITIL Continual Service ImprovementIncident Management and Problem Management are both elements of the fourth volume - ITIL Service Operation, which tries to define the best practice for dealing with interruptions to a customers service. What is an Incident? An incident is a single - unique - issue impacting one specific customer and their service. While there can be many similar incidents impacting multiple customers, each of them are in their fashion unique and need to be logged and treated as such.
An example of an incident is you losing your home Internet connection. While the underly…

What is PRINCE2

PRINCE2 stands for PRojects IN Controlled Environments and is a very popular method for effective Project Management.  PROJECT MANAGEMENTWhile PRINCE2 is one way of managing Projects, it is worthwhile defining what exactly a project is and why it needs management in the first place! 

A project is specific task/role that needs to be completed to meet certain objectives. In a managed project, you would have a defined beginning and end and certain "check points" throughout the process itself to ensure that you were on target to meet your overall objectives.

These checkpoints are referred to as "gates" and at each gate, you would have certain deliverable and targets to check your progress against. By managing a project in this fashion, you are able to ensure that you stay on track and that any issues or concerns are identified and dealt with at an early stage of the process versus waiting till the end.

The defined "end" to a project is necessary as it creates …


Competition is extremely fierce in the world of business, only a handful survive, and some can barely keep up with the demands of the times. That's why it is necessary to have an idea of what it takes to be successful and an integrated strategy to help maintain excellent service results.

ITIL discusses at length the four “Ps” of strategy- perspective, position, plan and pattern, each of which represents a different way to approach your service strategy. Brief summaries are provided here: Perspective - This is basically the vision statement of an organization.  Why is it in business, why is it doing what it is doing?  What are the plans and ideas for the future and how does the organization interact with its customers?  A perspective cements a service provider’s distinctiveness in the minds of the employees and customersPositions - What is the competitive landscape and how will the organization compete with other similar providers?  What is the key distinction between them and oth…


In a similar fashion to interviewing and hiring people - the hardest and most expensive exercise is getting the right employee - getting people back into the door is exactly the same.  You want that repeat custom as that is what will save you money in your marketing and advertising.  One of the key components to this in addition to the quality of the product itself is the customer service that you provide to the customer in their purchasing and ordering decisions.  You can offer promotions and slash prices to bring in as many new customers as you want, but unless you can get some of those customers to come back, your business won't be profitable for long. Good customer service is all about bringing customers back. And about sending them away happy - happy enough to pass positive feedback about your business along to others, who may then try the product or service you offer for themselves and in their turn become repeat customers. 
Good customer service should be thought of as re…