Interesting indeed
Jacques
Le 20/11/2015 09:47, Julien NICOLAS a écrit :
Hello Ron,
It's really interesting, thanks!
Julien.
Le 20/11/2015 07:41, Ron Wheeler a écrit :
This video is about the strategy surrounding the user experience.
https://www.youtube.com/watch?v=Hr1rN3jibIk
There are a lot of ideas about how to use the Kano Model to determine what
features should be included in a product.
- There are features that are so basic that they do not show up in user
requirements - Accounts must balance; Orders should not be lost.
These are typically expensive to include and if they work, you get no user
satisfaction but if they don't, you create a lot of user dissatisfaction.
- There are features that users consider key to the performance of the application and show up as "Features" in marketing docs and RFPs - good
documentation, search, multi-tenancy, support for eCommerce gateways, etc.
These have a linear line from "few features, unsatisfactory user experience" to
"many features with great user experience"
- There are features that generate "the WOW reaction". They are not expected to
be there but users/buyers are impressed when they are.
If they are not included, this does not generate dissatisfaction but if they
are there they generate user enthusiasm.
The trick is to know where each enhancement requested or suggested fits in the
space.
As time goes on, the "WOW" features move into the performance class and
eventually to the expected class.
For example, I can remember when touch screens were really exciting but now a
tablet or phone that only supports a keypad could hardly be sold.
One of the more interesting parts of the discussion is about why you need a process for
saying "No." to new features.
How do you keep a piece of software at exactly the right level of complexity?
Enjoy.
Ron
