Pareto Principle (80/20 rule)

August 27, 2007 – 8:17 pm

By Bryan Eisenberg, The Clickz Network, Mar 11, 2002

Italian economist Vilfredo Federico Damaso Pareto observed in 1906 that 80 percent of the land in Italy was owned by 20 percent of the population. Later, he observed this noteworthy ratio seemed to apply to other parts of life, such as gardening: 80 percent of his peas were produced by 20 percent of the peapods. Over time, this concept has come to be known as the “Pareto Principle,” “The 80/20 Rule,” and even “The Vital Few and Trivial Many Rule.” Interestingly, another of Pareto’s most noteworthy and controversial theories is that human beings are not, for the most part, motivated by logic and reason but rather by sentiment.

Observing the Pareto Principle in Action

Here are some 80/20 rule applications:

* Does 20 percent of your sales force produce 80 percent of revenues?

* Do 20 percent of your products account for 80 percent of product sales?

* Do 80 percent of your visitors see only 20 percent of your Web site pages?

* Do 80 percent of delays arise from 20 percent of the possible causes of delay?

* Do 80 percent of customer complaints arise from 20 percent of your products or services?

We all waste lots of time on trivial, repetitive tasks. That often means people are kept busy whether it is important or not, equipment is running whether needed or not, sales are made whether they are profitable or not.

Is the assertion that a small number of events produce the majority of results valid? It may not be a hard rule with a fixed ratio, but the observation has merit:

# A handful of customers out of many produces the bulk of revenues.

# A handful of products out of many items in a line produces the bulk of orders.

# A handful of salespeople out of many produces the majority of new business.

# A handful of scientists produces most research and development innovations.

# Most grievances come from a few employees, and most absenteeism can be narrowed down to specific individuals.

# Most accidents occur in clearly identifiable groups.

# Truly poor (or great) performance is achieved by a few easily identifiable individuals.

We tend to ignore these realities in practice. We often give the best salespeople the most difficult accounts instead of focusing their talent in areas where they could generate extraordinary volumes. The most highly skilled workers are often given the toughest work, although concentrating their skills on trouble-free jobs would allow them to produce significantly more than less-skilled coworkers. The most talented people are often assigned to the most challenging problems that, even when resolved, generally contribute little additional revenue for the company.

Applying the Pareto Principle to Your E-Business

Here are three ways you can use the Pareto Principle.

1. Use best-seller lists.

Find the “vital few” and make them easy for your visitors to find.

Book bestseller lists, music top-40 charts, TV ratings, and Hollywood box-office receipts are not merely a barometer of popular culture. They’re important marketing tools.

According to John Bear (”The #1 New York Times Bestseller”):

On Sunday, August 9, 1942, with no prior announcement and no fanfare, the New York Times published a list, ‘The Best Selling Books, Here and Elsewhere.’ Without exception, that list has appeared in every Sunday edition of the paper for 50 years.

A book that makes it to the top of the New York Times’s bestseller list can proudly display “#1 New York Times Bestseller” on its book jacket. The publishers hope you will find yourself in a bookstore, see the book, and think, “If everyone else is reading it and buying it, I will, too.” Think The Amazon.com 100 was created for some other reason?

2. Find out what to optimize on your Web site.

Often, when we review a client’s WebTrends report, we spend a lot of time analyzing where and how traffic flows through the site. Guess what? About 80 percent of the traffic hits only 20 percent of the pages. We’ve found this to be true for both business-to-business (B2B) and business-to-consumer (B2C) sites (although it’s not always true for content sites). Where do we focus our energy? Ideally, on those 20 percent of pages that are critical to the sales and buying processes and are required to maximize conversions. If users can’t find those critical pages, we optimize the pages required to lead them there in the conversion process.

Take a look at Max-Effect.com, first the old site, then the redesigned one. When we analyzed how people bought yellow pages ad design from Max-Effect, we came to the conclusion they flowed through three pages: the home page, the samples page, then the contact page. So we spent time rewriting the copy on those pages and changing the samples page from a bunch of thumbnails to a couple of before-and-after ads with some copy. Bottom line: Max-Effect is generating four times more leads and closing more business with a third less traffic.

3. Fix or discontinue problematic products and services.

Stop wasting precious resources on products and services that drain energy, time, and money. Whatever the problem costs you today, when you redirect your efforts the return on investment will be much greater. Without negative baggage, you’ll see real improvement in efficiency, morale, and productivity.

Why only three items, and not a top-10 list? You guessed it, the Pareto Principle. Again.

By Bryan Eisenberg, The Clickz Network, Mar 11, 2002

PRD (Product Requirement Document)

July 13, 2007 – 6:45 pm

Sometimes equated with Project Requirement Document

The PRD and Me

If you are in the web / internet industry, then you have more than likely heard this acronym float past your ears a dozen times or more. It is one of the most important documents a project/product can have. At first, it was like pulling teeth to get me to write one of these “things”. I remember the first one reminded me of those papers I used to crank out at the last minute in college, but as time wore on and I became more involved in all web processes and the PRD became my safeguard, my shield, my savior.

Now that I have written over twenty product requirement documents (some small, some large), I can give some good guidelines for the concept, format and content. Marinade on these items below and you’ll make everyone happy including yourself. Finger lickin’ good!

My PRD Definition

A PRD is a document that outlines all the requirements that should be met for building a product. The PRD is created when the MRD (Marketing Document) has been finalized and delivered. The scope of the PRD could be a few FSDs (Functional Specifications Document) or it could be a massive bundle of documents.

Special Notes: A PRD and an MRD may be merged depending on the size of the project. Generally, the larger the project, the more documents you will have.

PRD Outline

  • What is the product exactly
  • Give a title
  • How does it work in a general sense
  • Give a brief on what is does
  • How does it work in a technical sense. (*The FSD is supplied by the technical department)
  • The FSD usually follows the PRD as a technical guideline of how it will be built
  • Who does it affect
  • Does it compromise anyone else’s requirements?
  • Will this affect other relationships
  • What parts of the site will it affect?
  • Will pricing change?
  • How does it fit into the information architecture?
  • Does it affect your policies
  • Conditions of use?
  • Privacy?
  • Sales contracts?
  • Potential pitfalls?
  • Where could errors develop?
  • Maintenance?
  • Who needs to sign-off?

Depending on how strict your company is or what template they are using, you can always just copy the bulleted list down and provide some answers underneath each bullet point.

The “Meat and Potatoes” of the PRD

This is the “what” and the “how”. The more detailed of an account given, the better.

Here is an example:

* On each product page there is “this”
* Clicking on this link does this
* Advanced view shows “this”
* My mouse does “this” and “this” when I rollover something
* A drop down does this, etc, etc.
* A link goes back to this page
* Purchase options are here

Again, depending on how strict your company is or what template they are using, you can always just create some comps (web lingo for composites, or image examples) which give a visual treatment to all of the above

Further PRDness

The illustration above is a perfect transition into use cases - “a description of sequences of events that, taken together, lead to a system doing something useful. Each use case provides one or more scenarios that convey how the system should interact with the users to achieve a specific business goal or function”- Wikipedia.

You can present different ways the product could affect or interact with the user. If a user goes “here”, then “this” will happen. If the user goes “here” instead, then this will happen instead. Basically, you take the the comps you created above one step further and provides different ways the user could interact with your product. Could they have a different experience if, let’s say Javascript was turned off? Is the content dynamic? Is there only one path the to product? These are the fine tuning that creates a really nice document and remember, there’s no exact way of writing a PRD. See what works for you or your business and go from there.

Enjoy!

XML Inventory Feeds

June 19, 2007 – 2:08 am

Do you float inventory on your site?
Do you want to sell what you don’t have?
Are you too small, with too few cash reserves to buy in large quantities?
Would you like to test a products virility?

If you answered yes to any of these you may want to start hitting up your vendor about “XML inventory feeds”. Get the discussion going and see where it leads. Have your people talk to their people!

This is how it works…

A manufacturer provides a real-time XML inventory file that performs a query on inventory levels for their items and then it is fed into the resellers site. Generally, you use the same model numbers as the manufacturer for database synchronization. The inventory quantities for your products should be updated automatically using the XML feed. (Will also require a means to not query inventory for products that do not come from that manufacturer.

What is XML?

Structured information contains both content (words, pictures, etc.) and some indication of what role that content plays (for example, content in a section heading has a different meaning from content in a footnote, which means something different than content in a figure caption or content in a database table, etc.). Almost all documents have some structure.

A markup language is a mechanism to identify structures in a document. The XML specification defines a standard way to add markup to documents.

More Resources:
http://www.xml.com/pub/a/98/10/guide0.html
http://www.sixapart.com/about/feeds