crafting features that matter - ux from a modern analyst's perspective

Post on 17-Jun-2015

105 Views

Category:

Software

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

How many features in a software is actually being used? Are we investing on features which our users love to have? What drives adoption? What kills it? Let's take a look at more scientific approach than just assumptions, to validate the feature ideas before investing on them. In the end let's do a small exercise to start using this approach.

TRANSCRIPT

Features that matters

@kosalanuwan

Lets have a Quick Poll - How things work at your

company?- Where does design come in?- Some of the challenges?

Traditional BAs are no longer valid

in this era. … those times are gone.They need to be modernized, and seated in the front-line.

- Hasanga Abeyaratne told to KP

On an average, IT projects run 45% over budget and 7% over time, while delivering 56% less value than predicted.

- Source: University of Oxford

78% of respondents reported that

the “Business is usually or always

out of sync with requirements”.- Source: KPMG

75% of project fail due toFuzzy business objectives, out-of-sync stakeholders, and excessive rework.

- Source: KPMG

Agile projects are successful 3X more often than non-agile projects.

- Source: CHAOS

Modern Analyst needs to ensure the right bundle of features to

ship.

… test analysis and design skills

take a front seat in this role.

Well, there’s one way to find out;

The Lean Startup, turn to page seventy-five!

- Yngvar Ugland, CTO - Compello

Lean Startup is based on

constant cycles of Building,

Measuring, &Learning very

quickly.

First 100 users are very important,

‘coz these are the users who talk about your product.

Project Fast5 - Compiled set of features for the

app- Pushed to AppStore- Wanted to know what’s happening- Google Analytics is cheap and fast- Built few hooks to learn user

behaviors- Pirate Metrics to track AARRR!

Growth hacking like a Pirate - Acquisition- Activation- Retention- Referral- Revenue

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

They call it Empathy. Know the user, and you are not the user.

a brand new COFFEE SHOP ... coming soon

- Hasanga Abeyaratne told to KP

What do you want ina Comfortable and a Useful Coffee Shop?

Users can’t always tell you what they want, but they always can tell you what’s wrong.

Customers promote products that

trigger feelings ofdelight and satisfaction.

- Noriaka Kano

How would you know what features will make an

impact?

How?

- Ask 2 Questions for each feature1 Positive Question, and 1 Negative Question

Sample Question: Do you like to upload all your contact to cloud? vs.Would you like to see your contacts where ever you go?

- 5 Emotional responsesLike, Expect, Neutral, Can Tolerate, and Dislike

How would you know what features to include your MVP?

How?

- Identify features you want to ship

- Prioritize each feature- Compile a Product Backlog

You are almost always wrong about your users.

http://www.mindtheproduct.com/

http://www.mindtheproduct.com/

Basic Expectation is a

feature you expect to

work, and you will bedissatisfied if its not there.

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.

http://www.mindtheproduct.com/

Delighters are features

that can make you WOW,

but doesn’t disappoint

you when not there.

Invest on the order of Basic expectations, Satisfiers, andthen Delighters.

Not worth invest in Expectations that are already Satisfied.

Worth investing on Delighters and

Satisfiers.

http://www.mindtheproduct.com/

Lets do it again?

- Identify features you want to ship

- Reprioritize the Product Backlog

http://www.mindtheproduct.com/

Delightful features become

Basic Expectations once it

has become something

users expect.

Ask the 3rd Question for each feature,

How important it is?

You have to include 3 Delightful experience for each bad experience that

causing.

What you just did?

- Gather exciting features- Remove clutter- Invest on what matters most- Communicating the ROI- Doesn’t burnout the team

A great product is deep. It doesn’t

run out of features and functionality

after a few weeks of use. - Guy Kawasaki

Useful references?

- Kano Model by Noriaka Kano- Lean Series: Lean Analytics- Lean Roadmapping by Bruce

McCarthy- 2 Jars of Marbles by Google

You cannot NOT have a User Experience

@kosalanuwanhttp://kosalanuwan.tumblr.com/

top related