impact driven delivery

54
IMPACT DRIVEN DELIVERY HOW TO DELIVER DESIRABLE PRODUCTS #impactmapping #impactmanagement #UX @ingriddomingues @HeedTheNeed

Upload: inuse

Post on 14-Jun-2015

925 views

Category:

Business


0 download

DESCRIPTION

Workshop at Agile by Example 14 in Warszaw. Well-functioning Scrum teams have proved to be good at delivering working software, but that does not necessarily mean that they deliver optimal, or even expected, business value. Agile is becoming the standard way of developing software, and the understanding of the value of User Experience (UX) is increasing. Impact Management and Impact Mapping ensures value creation by focusing on desired values for users and busines

TRANSCRIPT

Page 1: Impact Driven Delivery

IMPACT DRIVENDELIVERY

HOW TO DELIVER DESIRABLE PRODUCTS

#impactmapping #impactmanagement #UX

@ingriddomingues @HeedTheNeed

Page 2: Impact Driven Delivery

INGRID DOMINGUES

@ingriddomingues

STOCKHOLM GÖTEBORG MALMÖ

SARA LERÉN

@HeedTheNeed

Page 3: Impact Driven Delivery

WHAT IS THIS ”IMPACT DRIVEN SCRUM”

THING

HOW CAN IT HELP YOU?AND

Page 4: Impact Driven Delivery

Impact Management is an approach that sums up techniques and practices in order to deliver expected outcome for business and users. It was originally aimed for digital design projects, but has also inspired organizational development projects. 

The most prominent part is the Impact Map, that visualizes the idea of how business value is generated through use of the service or product. 

We first presented the idea of Impact Mapping in 2002, in a paper called “From Business to Buttons”. The initial concept was then detailed into Impact Management and published in the book “Effektstyrning av IT” (in Swedish, Liber 2004), and then translated into English and published as Effect Managing IT (out of print, Copenhagen Business School Press, 2007). In 2005 we also started teaching Impact Mapping and Management. The first international workshop was held in 2007 at the yearly From Business to Buttons conference.

Impact Mapping caught on in the agile software community around 2010. They spread the word about the method at conferences and courses as well as informal meetups all over the world. The agile delivery aspect of Impact Mapping was described by Gojko Adzic in the 2012 book Impact Mapping, which was recently translated into both Chinese and Japanese.

Page 5: Impact Driven Delivery

#impactmanagement

makes everyone focus on desired

outcomes

Page 6: Impact Driven Delivery

GOOD DESIGN?

Page 7: Impact Driven Delivery

“If I’d asked my customers what they wanted,

they would have said, ‘A faster horse!’”

Henry Ford

Page 8: Impact Driven Delivery

Summary Day 1NEED FOR SPEED

Increased speed enables faster experimentation

Continuous experimentation is required

to make sure you are on track

Customers don’t know what they

want

Small, cross-

functional, selfdirected

teams

Page 9: Impact Driven Delivery

SCRUM?

Page 10: Impact Driven Delivery

SCRUM?

Page 11: Impact Driven Delivery
Page 12: Impact Driven Delivery

#impactmappingis a great tool to describe desired

outcome

Page 13: Impact Driven Delivery

IMPACT MAP

Page 14: Impact Driven Delivery

WHYIMPACT ON BUSINESS

HOWIMPACT ON USE

WHATSOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

Page 15: Impact Driven Delivery

WHYIMPACT ON BUSINESS

HOWIMPACT ON USE

WHATSOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS andGENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 16: Impact Driven Delivery

A few defined rules and structures makesthe Impact Map a solid ground for design, planning and quality assurance, thus delivering desired value:

1. The WHY must consist of at least two actionable metrics with a timeframe

2. The HOW must be based on user studies, even if rudimentary

3. The HOW must be prioritized, based on impact on the WHY

4. Every point in the chain from WHY to WHAT should add a clear value

Page 17: Impact Driven Delivery

IMPACT MAP EFFEKTKARTA ®

Page 18: Impact Driven Delivery

WHY

IMPACT MAP EFFEKTKARTA ®

Page 19: Impact Driven Delivery

WHY

HOW

IMPACT MAP EFFEKTKARTA ®

Page 20: Impact Driven Delivery

WHY

HOW

WHAT

IMPACT MAP EFFEKTKARTA ®

Page 21: Impact Driven Delivery

#impactmanagementmakes it possible to validate ideas and deliveries along the

way

Page 22: Impact Driven Delivery

GENERATE LEADS5% of visitors to pages with a ”Contact me”-button should submit the contact form

Function:Super easy to find solutions based on symptoms

1THE CURIOUS

Doctors and nurses looking for the best wound care or surgical products

Need:Want quick answers to specific questions

IMPACT MANAGEMENT EFFEKTYRNING ®

Page 23: Impact Driven Delivery

As a USER I want a FUNCTION/CAPABILITY

in order to fulfil my NEED

Page 24: Impact Driven Delivery

Explicit needs

HUR DO PEOPLE EXPRESS THEIR NEEDS?

Visible needs

Latent needs

Page 25: Impact Driven Delivery

Summary Day 1EXPERIMENT TO EVALUATE SUCCESS!

Increased speed enables faster experimentation

Continuous experimentation is required

to make sure you are on track

Customers don’t know what they

want

Small, cross-

functional, selfdirected

teams

Page 26: Impact Driven Delivery

Evaluate design patterns User Stories with UX acceptance criterias Validate that design meets user needs Validate that long-term metrics are met

EVALUATE SUCCESS – Early and continuously

Page 27: Impact Driven Delivery

QUESTIONS?

Page 28: Impact Driven Delivery

WHYIMPACT ON BUSINESS

HOWIMPACT ON USE

WHATSOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS andGENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 29: Impact Driven Delivery

MEANINGFUL METRICS

• Are a direct result of use• Describe something that is

important for the business to achieve

• Must be measurable

Page 30: Impact Driven Delivery

START WITH DOMAINS

• Productivity• Effectiveness• Time spent• Customer

satisfaction• Recurrent

customers

• Conversion• Correctness• Brand

awareness• Recommendati

on• Learnability• …

Page 31: Impact Driven Delivery

CONTINUE WITH METRICS

SIMPLICITY

90% of users should consider the new reader to be as simple, or considerably simpler, than the existing reader

CORRECTNESS

90% reduction in cases where controllers catch customers who have, without realizing, paid too little

FLOW

80% of drivers should consider the new reader to cause less or equal queues compared with today

Page 32: Impact Driven Delivery

OBJECTIVEMETRICS

QUANTITATIVEMETHODS

QUALITATIVEMETHODS

SUBJECTIVEMETRICS

OBSERVED BEHAVIOUR Log analytics, user testing &field studies

• Visitor behaviour

• Success rate

ANALYSED OPINIONSUser testing, in-depth interviews, focus groups • Attitudes • Explained behaviour

MEASUREMENTSLog analytics, absolute

measurements • No. of mistakes• Conversion rate

• No. of returning customers• Task time

MEASURED OPINIONSSurveys

• Attitudes• Satisfaction

• Estimated time spent• Estimated quality

Page 33: Impact Driven Delivery

#impactmanagement

means measuring success

Page 34: Impact Driven Delivery

MEANINGFUL METRICS

• Are a direct result of use• Describe something that is

important for the business to achieve

• Must be measurable

Page 35: Impact Driven Delivery

MEANINGFUL AIMS

• Consists of one sentence• Summarises the metrics• Describes the value that the

solution brings to the business• Can be completed with a catchy

slogan

Page 36: Impact Driven Delivery

WHYIMPACT ON BUSINESS

HOWIMPACT ON USE

WHATSOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS andGENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 37: Impact Driven Delivery
Page 38: Impact Driven Delivery

The Eager

Page 39: Impact Driven Delivery

The Focused

Page 40: Impact Driven Delivery

Explicit needs

HUR DO PEOPLE EXPRESS THEIR NEEDS?

Visible needs

Latent needs

Page 41: Impact Driven Delivery

GembaGEMBA – WHERE IT HAPPENS

Page 42: Impact Driven Delivery

Spends time thinking about interior decoration and smart solutions for their own home, or even other peoples homes. Collecting smart and beatutiful solutions for now or the future, and likes to share their ideas with others.

NEEDS• Wants to be inspired about new design and renovations• Wants to daydream

The Dreamer”This could be very nice when...”

Page 43: Impact Driven Delivery
Page 44: Impact Driven Delivery

PRIORITISE

• Will give guidance for the project:– Release plan– Design – Cuttings

• Defined by business managers. Based on: – Number of users – Activity– Impact on others

Page 45: Impact Driven Delivery

NEEDS

• A sentence that starts with either–WANTS – close at heart–MUST – resistance

• The sentence should give guidance for validating designse.g ”wants to easily check what she has paid for”

Page 46: Impact Driven Delivery

MEANINGFUL NEEDS

• Describes why the product or service is used

• Shall make it possible to know what is needed to satisfy the user

• Avoid talking about functions, keep asking ”Why?” until you get to the real need

Page 47: Impact Driven Delivery

WHYIMPACT ON BUSINESS

HOWIMPACT ON USE

WHATSOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS andGENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 48: Impact Driven Delivery

THE KANO MODELWHAT KIND OF VALUE DOES THE FUNCTION GIVE THE USER?

Page 49: Impact Driven Delivery
Page 50: Impact Driven Delivery
Page 51: Impact Driven Delivery

IMPACT MANAGEMENT PROCESS

Page 52: Impact Driven Delivery

PRODUCT STRATEGY

Product Owner

UX Lead

- Buliding the right thing

- Thinking far ahead

DELIVERY

Scrum Master

Team

- Building in the right way

- Producing executable code

Page 53: Impact Driven Delivery

Some AMENDMENTS to Scrum in order to be IMPACT DRIVEN

• The Product Owner has clear priorities, based on expected user and Business impact

• UX Lead answers to all User Interface design related questions

• The Backlog is a transition of the Impact Map

Page 54: Impact Driven Delivery

Some AMENDMENTS to Scrum in order to be IMPACT DRIVEN

• UX Lead will see to it that User Stories with user interaction are defined in Backlog Refinement sessions

• User Stories (with user interaction) contain design and UX acceptance criterias

• Definition of Done contains UX validation

• Deliveries are tested with users