New Prioritization Strategy – KANO Analysis

Filed in by Rackspace Blogger | March 2, 2009 7:16 am

In our never ending quest to give you exactly what you want, Mailtrust is employing new strategies to identify and prioritize our product roadmap. Developed in the 1980’s by Dr Noriaki Kano, KANO Analysis is gaining momentum among IT companies using Agile development methods. In the world of development, there are unlimited product possibilities and unlimited opinions on which products are the most important. Using KANO analysis, Product Managers have the ammo to say, “We need this feature now or we’re going to lose customers.” Mailtrust just finished our first round of KANO Analysis, asking customers two key questions:
(1) How would you feel if Mailtrust offered this new product?
(2) How would you feel if Mailtrust DID NOT offer this new product?
These answers tell us how “mandatory” future enhancements are to our current and potential customers. A typical survey might ask, “Would you like to have Active Directory synchronization?” Plenty of users would say “yes.” But KANO gives us the tools to separate those who said yes into those who must have the feature and those who wouldn’t mind having the feature. Customers that must have the feature might look to other companies if we don’t provide it. While customers that wouldn’t mind a feature are fine without it or okay with putting it on the backburner.
So far, we’ve gotten some powerful input from our users. What do our customers want? Email archiving, Active Directory synchronization, and SharePoint. Now that we know what’s most important, we can give customers the things they must have, as well as, some neat bells and whistles they wouldn’t mind having.
Want to know more about KANO? Check out a great explanation[1] of the process or take a look at my favorite video[2] on the subject.

  1. explanation:
  2. video:

Source URL: