2. Presenter Notes:
You’ll see the presenter notes here.
A very friendly note:
The following slides are put together to give you an idea of what the
presentation flow will look like and to help you understand how the panelist
will be using visuals/text on the screen during presentation. The presenter
notes have been added on the right side.
Thanks and enjoy!
-C
3. Presenter Notes:
What is a wicked problem?
What are the wicked problems in
software development?
- Changing requirements
- User needs vs. what
stakeholders want.
WICKED PROBLEM
5. Presenter Notes:
Design as a system
Meadows - Thinking in Systems
(introduce the book, examples
from design systems course)
- Elements
- Relationship
- Function/Purpose
6. Presenter Notes:
Different elements/features/needs
create an endless backlog.
(Each feature needs a purpose or a
function for user)
Can we make everything ‘right
now’ with a given budget and a
deadline?
- Data needed to support
decisions (what to
implement, what to say no
to) during the dev process
7. Presenter Notes:
Each different product features has
its own requirements (interface,
buttons, menu etc.) - increasing
complexity
When the complexity increases,
user’s experience degrades
9. Presenter Notes:
Useful metaphor: Paolo Cardini -
iPhone cases for monotasking.
How can we convince our team and
our client to ‘let go’ the features
that are not necessary?
10. Presenter Notes:
How do you create a product
roadmap?
How do you list features in right
order for development?
That all sounds great but then..
How do you measure satisfaction?
How do you choose what to build in order to provide satisfaction?
How do you consider the level of effort to build a feature?
And how will you guide your development team to decide what features
should/should not be build?
How will you help them define priority?
11. Presenter Notes:
(Fact: Until we test the product
with the users, we think all is
working well, features are being
used correctly)
User testing - instead of doing
everything right now and spending
resources.
Elaborate on how..
(to play the gif, view this slide deck
through “other resource link”)
12. Presenter Notes:
Introduce Noriaki Kano:
- Educator, consultant
- quality management.
Introduction to Kano Model.
“In 1984, he published a paper
about set of ideas to measure
customer satisfaction with a
simple ranking scheme. This model
is today known as the Kano
Model.”
13. Presenter Notes:
is a technique that helps the
developers determine the users’
satisfaction with each product
feature.
Talk about Daniel Zacarias and his
explanation.
WHAT IS THE KANO MODEL?
- Customers’ Satisfaction with our product’s features depends on
the level of Functionality that is provided (how much or how
well they’re implemented);
- Features can be classified into four categories (Attractive, Must-
be, Performance, Indifferent);
- You can determine how customers feel about a feature through
a questionnaire.
foldingburritos.com/kano-model
14. Talk about 4 categories (convert
each into a separate slide)
- Attractive
- Must-be
- Performance
- Indifferent
Explain the chart
Satisfaction
Functionality
Performance
Attractive
Must-BeIndifferent
4 CATEGORIES
15. WHAT IS THE KANO MODEL?
Presenter Notes:
What is a Kano model
questionnaire.
Functional question
Dysfunctional question
Importance question
17. Presenter Notes:
Ok. but how is it customized?
Answer: Explain the importance of
level of effort that goes into each
feature.
High
Medium
Low
Existing
18. Presenter Notes:
Case Studies
- What did the stakeholders
want
- Paper prototyping with
users
- List of features with Kano
Model
- Creating a prioritized list
- Presenting them to
stakeholders
19. Presenter Notes:
What is our client engagement
model?
Dev lead + Design lead + Specialists
How do we solve wicked problems?
(more explanatory visuals will be
added)
