#kanomodel

[projectmanagertemplate]

Requirements Prioritization MoSCoW and Kano Tools

Requirements Prioritization MoSCoW and Kano Tools. This blog will explore how these models work and how they can be applied.

In project management one of the most challenging tasks is to prioritize requirements effectively. Without clear priorities, projects can quickly become chaotic, resources can be wasted, and deadlines missed. Two popular models for prioritizing requirements are the MoSCoW method and the Kano Model. This blog will explore how these models work and how they can be applied to ensure that your project focuses on what truly matters.

[mohamsqr]

Beauty is when you can appreciate yourself. When you love yourself, that's when you're most beautiful. Model: @eaemann_s Dresses 👗: @moon_byme MUA: @lamerciebeautylounge Photo: @mohasheikh_photography #fashion #beauty #nigerianmodel #kanomodel #arewamodels (at Kano, Nigeria) https://www.instagram.com/p/Bow-DJ1F738/?utm_source=ig_tumblr_share&igshid=rijwjqp717ov

[catalyzingbydesign-blog]

Kano Questions and Evaluation Methods

Kano Questions:  E.g. How do you feel if this feature is present? How do you feel if this feature is absent? E.g. (Function Form) If you have to wait for less than 2 minutes before the customer rep answers your call, how do you feel? (Dysfunctional form of the question) If you hae to wait for more than 2 minutes before the customer service rep answers your cal, how do you feel? Likert scale: 1. I like it that way 2. It must be that way 3. I am neutral 4. I can live with it that way 5. I dislike it that way

[catalyzingbydesign-blog]

Kano- A quick intro

Kano A. Value attracts customers B. Quality keeps customers and builds loyalty C. Innovation is necessary to differentiate and compete in the market

Kano is based on 3 core types of need:Basic | Performance | Excitement

1. Basic: Attributes/ needs that are expected, assumed, given

Satisfying basic needs merely minimises dissatisfaction. Absence or poor execution leads to greater dissastisfaction. Users will rarely state these, so you have to observe or analyse other products, services in dept to get to what they need. No amount of execution quality will cause positive satisfaction, it will only minimise dissatisfaction.

E.g. Toilet rolls in a hotel room. Zero toilet rolls = unhappy customer. 3 extra toilet rolls = not unhappy but not happy customer. E.g. Car door hits curb when opened causes major dissatisfaction. Car door missing the curb causes no dissatisfaction, but not positive satisfaction.

2. Performance: Attributes/ needs that are consciously evaluated by the customer and at top of their minds when purchasing. Satisfaction is proportional to the way in which these are executed, starting from dissatisfaction due to slow, poor, or absent exection through to hight satisfaction due to quick, powerful or exquisite execution.

These are possibly the easiest to ascertain from users or customers as they are often 'stated' needs, so will come up in surveys, focus groups etc. e.g. More Miles per gallon = greater satisfaction e.g. Less waiting time in an airport = greater satisfation

3. Excitement: Attributes/ qualities that deliver "buzz". The wows, differentiations, innovations, unique selling/ value propositions. Presence of these will delight customers/ users and increase their satisfaction, but absence of them will not dissatisfy.

These are harder to come up with, and are really require an understanding of 'latent need' which can only really be understood through observation or incredible genius intuition. E.g. Internet access on a plane or tube is not expected and so will not upset if not present, but will delight if it is.

E.g. A pillow menu at Penny Hill Park Spa for RMA Xmas party is not expected but is a rare delight.

Over time... Excitement needs become performance needs, and then basic needs.

[courseradesign]

Attack of the Yeti

I recently read this article in BusinessWeek and I couldn't resist blogging about it here because of what an awesome product it is.

The product is called the Yeti. It's a $1,300 cooler that was invented by a couple of fishermen who needed a durable cooler to store their drinks and their fish. It evolved into a top-of-the-line cooler that can withstand grizzly bear attacks. Needless to say, it now enjoys a cult-like following and retailers can't keep them on the shelves. It's also become a prime target for thieves who can easily make a quick buck off a pinched Yeti due to the high demand on the black market.

Awesome product. Wonder if they used the Kano model to come up with the product attributes?

[courseradesign]

Kano Model

I'm currently in Week 2 and one of the principles that really stood out to me from "Lecture 2d: Types of User Needs" is the Kano model.

According to Wikipedia: In the late 1970s and early 1980s, Noriaki Kano and his colleagues laid the foundation for a new approach to modeling customer satisfaction. Kano challenged the conventional beliefs that improving each attribute of a company's product or service will lead to increased customer satisfaction. Kano believed that not all attributes of product or service performance are equal in the eyes of the customer, and that some attributes create higher levels of customer loyalty than others.

The Kano model is a theory for product development that consists of a horizontal x-axis that describes the extent to which you addressed a user need and a vertical y-axis describes the resultant level of customer satisfaction.

There are 4 types of user needs that Kano outlined: 1. Don't care: something not relevant to user 2. Linear: more is better (e.g., affordability) 3. Must haves: intense dissatisfaction if missing, but not noticeable if done extremely well 4. Latent needs: not noticeable if unaddressed, but extreme delight if done well

I think that 3 and 4 are both very interesting ways to think about design, particularly 4 which is difficult to coax out of interviews or surveys because the end user themselves may not be aware of it yet. And thus, the challenge as a designer is to have extreme foresight into what features fall into types 1-3 and what features MIGHT the user want in type 4.

Very thought provoking!

[krauti]

An easy to read article at the Baymard Institute about the Kano model: "The Kano model assumes three different attribute types – basic, performance, and delight – that collectively constitute the customer experience of your product."

Via @IATV