ux leanux 5 mvp incl cycle 2019 - hs augsburg€¦ · declare your assumptions build design an...

Lean UX Minimal Viable Product

KP Ludwig John

Lean UXMinimal viable product

Lean UX Development Cycle

KP Ludwig John

Project determination

How to decide, which features to put in?

You start a new project.

Suggestions?


KP Ludwig John

Project determinationProject Start

Suggestions?


KP Ludwig John


• What the project should do • What people would do with it

Collecting Assumptions

Project Start


KP Ludwig John




Recommendations

How would you do that?

• do it as a team• all disciplines (design, software, concept, marketing, etc.) should have a voice

• do analytic research before beginning(analysis of previous versions, analysis of competitors)

2 minutes


KP Ludwig John




Determine: • What goals wants the provider (business stakeholders)achieve with the product/system?

• What are the target groups of the product / system?

• Why would the target groups use the system? (user goal)

• What do they gain by using the system?

Agree on your assumptionsand prioritize it


KP Ludwig John

Project determination Collecting Assumptions

Assumptions are not Facts! It’s just your assumptions!



KP Ludwig John



Richard Phillips Feynman

American theoretical physicistNobel Price Winner 1965

How we would look for a new law?

reference: http://youtu.be/b240PGCMwV0

http://youtu.be/b240PGCMwV0


KP Ludwig John



Only when you confront your project with real users,it will show if your assumptions are right. Therefore: User Testing as early as possible,as regularly as possible throughoutthe whole development cycle



KP Ludwig John

Users as constant Referenceat all stages of the project(in reverse order):

general work flow in a project development cycle:


• User test the final project • User test before Release in Beta Version of the project • User test parts of the project in Prototype • User test individual features while developing and even

• User test the concept


KP Ludwig John

MVP (minimal viable product)

Already existing

• Personas • Context of Use • Hypothesis

Preconditions

Goalto validate your hypothesis to validate concepts, functionalities, design


KP Ludwig John


Goalto validate your hypothesis to validate concepts, functionalities, design

How?produce a minimal viable product and test it!

Lean UX


KP Ludwig John

Project Development Cycle

© Graphic out of the presentation by Jeff Gothelf and Josh Seiden at Interaction14 (Amsterdam/Hilversum)


KP Ludwig John


Idea Assumptions

State your desired OutcomesDeclare your Assumptions

Build

Design an ExperimentWrite a test case (first)

ProductPrototype

Build a Minimal Viable Product (MVP)

MeasureUser Test

Test with real Users

DataResults

Repeat

Learn

Team Synthesis Determination of next steps

Lean UX


KP Ludwig John


Repeat

Repeat this cycle constantly

with small chunks of the Product

in short periods of time (every 1-2 weeks)

with manageable effort

Goal: Constant feed back from the Userthroughout the entire development process Optimization of the development processQuicker, Cheaper, more Successful Better results!

The idea of Lean UX:

Reference: Gothelf/Seiden: Lean UX, O’Reilly 2013

Lean UX


KP Ludwig John

Some Key Insights

Product development is an iterative process.

Focusing on iteration and learning will help to develop better products.

Design is the process of gradually applying constraints until an elegant solution remains.Learning what those constraints are is a process of observation.

Luke Wroblewski Twitter@lukew Oct 10 2015

Project Development Cycle Lean UX


KP Ludwig John

Some Key Insights

Don’t just add features to your product.

Treat every idea as a question that needs an experiment.

Know what features to say no to.Don’t get stuck in the mentality that you’re just one feature away from the awesome product.

Luke Wroblewski Twitter@lukew Oct 10 2015

Project Development Cycle Lean UX


KP Ludwig John


Repeat

Working in short cycles

take small steps, try something new and see how it works.

If it fails, you’ve invested very little. If it succeeds, keep doing it and improving on it.

Recommendations

Reference: Jeff Gothelf https://medium.com/@jboogie/agile-vs-lean-vs-design-thinking-2329df8ab53c#.kp906jbus

Lean UX

https://medium.com/@jboogie/agile-vs-lean-vs-design-thinking-2329df8ab53c#.kp906jbus


KP Ludwig John


Repeat

Hold regular retrospectives

at the end of each cycle, review what went well, what didn’t go well and vow to improve one or two key things.

Recommendations


Lean UX



KP Ludwig John


Repeat

Put the user at the center of everything

Recommendations


Lean UX

Frequently ask: How do we know we’re shipping something users care about? How do we find out? How does that affect what we prioritize?



KP Ludwig John


Goal: Constant User feed back

But what can I testat early stages of the development?

Lean UX


KP Ludwig John


But what can I testat early stages of the development?

Constantly createMinimal Viable Products

and design focussed experimentsto test new features, ideas, parts of the product

Reference: Gothelf/Seiden: Lean UX, O’Reilly 2013

Learn and Repeat

Lean UX


KP Ludwig John

Test functionality and ideas quickly and very focused

Decide (first), which Function / Concept / Idea to test.Design an experiment exactly focused on this.

Goal


Create a prototype, which allows users to experience the new function / idea.

It should be small, quick produced, but functional for the aspects in focus

Process


KP Ludwig John

MVP Example IMS.UX 2017smart watch App Campus; Team Invisible Monkeys

Hypothesis:

Provides Function of the CampusCardas App on a smart watch


KP Ludwig John

MVP character IMS.UX 2017smart watch App Campus; Team Invisible Monkeys

Test


KP Ludwig John

MVP ExampleResult

IMS.UX 2017smart watch App Campus; Team Invisible Monkeys


KP Ludwig John

Low-Fidelity:

Clickable Wireframes, Paper, Wizard of Oz

depends on Test Goals and stage of project development

some Tools

Mid- and High Fidelity:

more detailed, Test Designs Simulation of final experience

Character of Prototype

Coded Prototypes

for native environments parts of code can potentially be reused for production time consuming

Reference: Jeff Gothelf; Lean UX, O’Reilly 2013



KP Ludwig John

Adobe XD adobe.com

Screenshot: https://medium.com/toptal-publications/adobe-xd-vs-sketch-which-ux-tool-is-right-for-you-903e6744b282

https://medium.com/toptal-publications/adobe-xd-vs-sketch-which-ux-tool-is-right-for-you-903e6744b282


KP Ludwig John

Axure • professional tool• lots of functionality

axure.com• difficult to learn• expensive, 30 days free trial


KP Ludwig John

Balsamiq

• Wireframe sketches• simple to use, quick

balsamiq.com

• low interactivity• rather expensive

• installed at UX-Lab

DEMO Video: https://balsamiq.com/


KP Ludwig John

Marvel

• Hi-Fidelity Prototypes• animations, transitions, interactivity

marvelapp.com

• prototype feels close to the product • free version available


KP Ludwig John

Proto.io

• Hi-Fidelity Prototypes• animations, transitions, interactivity

• prototype feels close to the product • trial version, subscription model

Ad Video: https://proto.io/


KP Ludwig John

Invision

• Prototypes + Reviews• collaborative work• statistics + metrics of Reviews

invisionapp.com

• free version available / subscription model • Apple Watch + Android• import from Sketch + Photoshop

Ad Video: https://www.invisionapp.com/


KP Ludwig John

Sketch sketch.comDesign Tool by/for InVision


KP Ludwig John

Protopie protopie.io


KP Ludwig John

MVP Example

Hypothesis:

IMS.UX 2017smart watch App Campus; Team Tedpish

bad design, difficult to read, fuzzy user goals and measurement; better use this format:


KP Ludwig John

IMS.UX 2017smart watch App Campus; Team Tedpish

Paper based Test

MVP Example


KP Ludwig John

MVP Testing

Test your Hypothesis

Prioritize your list of of Hypothesis

In general you would prioritize your assumptions by the risk they represent What are the consequences of this being badly wrong? The more severe the consequence the higher the priority.

and the level of understanding of the issue at hand (the less you know, the higher the priority)

Reference: https://www.interaction-design.org/ux-daily/628/a-simple-introduction-to-lean-ux

https://www.interaction-design.org/ux-daily/628/a-simple-introduction-to-lean-ux


KP Ludwig John

MVP Testing


• create the smallest thing to determine the validity of each hypothesis statement (this is MVP)

• run experiment with this MVP

• result: Evaluation whether your hypothesis was correct, should be pursued, refined or abandoned


Prioritized list of of Hypothesis results in several paths to explore


KP Ludwig John

MVP Testing


Decide, what you're trying to learn from the MVP

• Is there a need for the solution I'm designing? • Is there value in the solution and features I'm offering? • Is my solution usable?

Basic questions:



KP Ludwig John

MVP Testing


• Prototype an experience

• Simulate, what's like to use your product or service

• Expend as little effort as possible for the prototype

Approach



KP Ludwig John


MVP character

X



KP Ludwig John


MVP character

Test it and if there are no valuable results, abandon it. The MVPs which show promise can then be incorporated into further design and development rounds without too much hassle.

Build the most basic version of the concept as possible.



KP Ludwig John

MVP Testing


User research and testing, by the very nature of Lean UX, are based on the same principles as used in traditional UX environments. However, the approach tends to be “quick and dirty” – results need to be delivered before the next Agile Sprint starts. So there’s much less focus on heavy-duty document outputs and more focus on raw data.

Test methods



KP Ludwig John

MVP Testing

Test methodsSame principles as used in traditional UX

Discuss and collect2 minutes?

Examples


KP Ludwig John

MVP Testing

Test methodsSame principles as used in traditional UX

Examples

Approach tends to be “quick and dirty”

• Steve Krug’s Trunk Test • Screen Recording • Thinking aloud • Video observation • Eye tracking • Writing along (remote)

• A/B Testing • Card sorting • Diary Studies • Field studies

(Interviews, Observations) • Expert Review


KP Ludwig John

MVP Testing

Practice


KP Ludwig John

MVP Testing

Prioritize your Hypothesis

Sketch Experiments for the FIRST THREE of it

Practice

30 minutesTeamwork

Determine:

• What you trying to learn • Character of MVP • Method of test • rough test scenario

Lean UX Hypothesis Writing

KP Ludwig John

MVPCriteria

Clear research questionWhat do you want to learn?

Clearly related to the needs and goalsof one or more of your Personas

Simplicity of the MVP Focussed on research question / hypothesis

Traceable Measurement of the MVP / Hypothesis

Lean UX Hypothesis Writing

KP Ludwig John

Create a Minimal Viable Product

Prioritize your Hypothesis

Next

Deliver

Design a simple experimentfor the first three of it

Reference: Josh Seiden, Jeff Gothelf; work shop Hypothesis writing; Interaction 14, Amsterdam 5. Feb. 2014

hs-augsburg.de/homes/john

PDF containingHypothesis (prioritized)Sketch / Description of MVP and Test plan

ux leanux 5 mvp incl cycle 2019 - hs augsburg€¦ · declare your assumptions build design an...

Documents