The document discusses prioritizing features for software products based on customer needs and feedback. It recommends using the Lean Startup methodology of quickly building, measuring, and learning from customers. Product managers are advised to empathize with users, understand what problems users want solved rather than features they ask for, and prioritize features that will trigger feelings of satisfaction over those that are merely expected functionality. The Kano model of classifying features into basic expectations, satisfiers, and delighters is referenced as a way to determine what impacts customers and where to focus development efforts.

1. Features that matter
@hasanga

2. Quick question.

3. This is why software sucks!!
Developers think how easy to code it…
Then software becomes developer
friendly but not user friendly.
- Kosala Perera to Me

4. On an average, IT projects run
45% over budget and
56% less value than predicted.
- Source: University of Oxford

5. How do we ensure we ship the
right bundle of features?

6. Well, there’s one way to find out;
The Lean Startup,
turn to page seventy-five!
- Yngvar Ugland to Kosala Perera to Me

7. Lean Startup is based on
constant cycles of
Building, Measuring, &
Learning very quickly.

8. Bad news travels fast.
A dissatisfied shopper tells
around 10 other people about
the shopper’s bad experience.

9. First 100 users!
How to retain them?

10. Empathy.
Know the user.
Remember you are not the user.

11. Let’s open a COFFEE SHOP!

12. What do you want in
a Comfortable and a Useful
Coffee Shop?

13. Users can’t always tell you
what they need,
but they will always tell you
what’s wrong.

14. Customers promote products that
trigger feelings of
delight and satisfaction.
- Noriaka Kano

15. How would you know
what features will make an impact?

16. How?
- Ask 2 Questions for each feature
1 Positive Question, and 1 Negative Question
- 5 Emotional responses
Like, Expect, Neutral, Can Tolerate, and Dislike

18. How?
- Identify features you want to ship
- Prioritize each feature
- Compile a Product Backlog

19. You are almost
always wrong about your users.

20. http://www.mindtheproduct.com/

21. http://www.mindtheproduct.com/
Basic Expectation is a
feature you expect to
work, and you will be
dissatisfied if its
not there.

22. http://www.mindtheproduct.com/
Satisfier is a feature that
can make you satisfied
when fully implemented,
but you will be dissatisfied
if its not there.

23. http://www.mindtheproduct.com/
Delighters are features
that can make you WOW,
but doesn’t disappoint
you when not there.

24. Invest on the order of
Basic expectations, Satisfiers,
and
then Delighters.
Not worth invest in
Expectations that are already
Satisfied.
Worth investing on Delighters
and
Satisfiers.
http://www.mindtheproduct.com/

25. Lets do it again?
- Identify features you want to ship
- Reprioritize the Product Backlog

26. http://www.mindtheproduct.com/
Delightful features become
Basic Expectations once it
has become something
users expect.

27. Ask the 3rd Question for each feature,
How important it is?

28. You have to include
3 Delightful experience for
each bad experience that causing.

29. What you just did?
- Gather exciting features
- Remove clutter
- Invest on what matters most
- Communicating the ROI
- Doesn’t burnout the team

30. A great product is deep. It doesn’t
run out of features and functionality
after a few weeks of use.
- Guy Kawasaki

31. Useful references?
- Kano Model by Noriaka Kano
- Lean Series: Lean Analytics
- Lean Roadmapping by Bruce McCarthy
- 2 Jars of Marbles by Google

32. Engineer happiness not
products
@hasanga