[Sigia-l] Kano Analysis

[Boniface Lau]

> From: Eric Scheid
>  
> The designer can take a guess as to which features will produce
> satisfaction, but without some feedback from the users (eg. KA

ISTM you are confusing KA with user feedback.


> or UE) then it is just a shot in the dark, perhaps guided by "best
> practices".
> 
> Say you're designing two different models of cars: one for the young
> singleton, one for adults with young families. They both might have
> "it must be fun to drive long distances" as a requirement (the
> summer break roadtrip to florida for college kids, vs the annual
> pilgrimage to disneyland for the family). I know you wouldn't
> suggest that both models should have the same features, I know
> you're not that stupid.

But you're wrong, due to your own self-imposed limitation. In
exploring design alternatives, I do not exclude the possibility that
both models can meet their requirements with the same features. After
all, there is nothing stating that both models cannot have the same
features. Good designers know the real boundaries.

Good designers also have the necessary confidence to ride the design
process exploring what seems like stupid things to others. Thus, being
"that stupid" is sometimes the precondition for coming up with a smart
design, e.g. one that allows both car models to meet their requirement
with the same features.


> 
> How do you determine which features produce the most satisfaction
> payoff for each group, thus meeting that requirement?

Validation.


> 
> I won't give you a hint, mmm'KAy.

That reminded me of the saying, "When all you've got is a hammer,
everything looks like a nail."


Boniface