Last week I was at a requirement engineering course.
One thing that stuck was, the Kano model, which can be used to classify requirements:
Depending on their category (excitement-, performance- or basic-attibutes) the corresponding requirements have a very different influence on customer-satisfaction.
Basic attributes can easily be overlooked, if you are not familiar with the domain, because often they are not explicitly mentioned.
Excitement attributes are the factor that make the difference.
Over time, with each new product-version, given attributes drift from excitement to performance to basic.
I had to read this several times before I realised that there was a meaning to it. The "satisfied / dissatisfied" axis is talking about customer satisfaction, not about how well the requirement is satisfied. Maybe we need to use a different pair of words, like "delight / disappointment"!
ReplyDeleteThere is a GREAT website that explains the Kano Model in more detail. Check it out.
ReplyDeletewww.kanomodel.com (direct link)
or for further innovative examples go to www.c2c-solutions.com