UX & Test at CocoonThe foundations of an MVP

Kimberley Bottomley & James SaltLean Start-Up Yorkshire, 18/07/2015

What we’ll cover tonight...

Process as an enabler not a restriction

Options, data and priority

Experience of helping shape a start-up

https://queenphotos.files.wordpress.com/2013/08/freddie-3-b-w-split-1019x1024.jpg

http://www.beckysage.com/2015/03/09/sweet-surrender/

http://www.popsugar.com/moms/photo-gallery/32086719/image/32087187/Shaping-Dough

About Cocoon

http://seriousplaypro.com/2015/03/12/lego-case-study-team-culture/

Scene Setting

Context

Philosophy

REQUIREMENTS = ASSUMPTIONS

“WE KNOW” = “WE BELIEVE”

“LET’S BUILD IT” = “LET’S TEST IT”

CAN WE = SHOULD WE

Read more about Lean UX: http://www.jeffgothelf.com/blog/lean-ux-book/#sthash.0abLXGUq.dpbs

● Don’t become wedded to the ‘wrong’ solution

● Allows a problem to be seen from multiple perspectives

● Exploration creates freedom - to find new ways

● Keeps the big picture in view

Why are test and ux important to a start-up?

Why is data important for start-ups

● Minimises risk of building the wrong thing

● Minimises waste - time and money

● Gives confidence - to founder(s), team and investor(s)

Process

Data > Intuition

Prioritise

Discover

Develop

Validate

Options

● Prototyping

● Usability testing

● Acceptance testing

● Issue Surfacing

Some techniques for generating options

What are you prototyping?

Acceptance criteria as assumption:

As an Active Cocoon customer

I want clear audio from my Cocoon device

So that I can determine the appropriate response

Techniques for generating options

This is a prototype

This is a prototype

This is a prototype

Test - with real people

Observe behaviour

Set real world tasks

“What do you think it would do?”

FREE! Tools for guerrilla UX testing

Highlights - Feedback on home screen concepts

2 participants were not immediately certain what the purple icon represented.

3 participants felt a photo or name/initials would be more of an indicator as to who someone was.

1 participant said they expected a flatline unless Cocoon was alerting them on something.

1 participant expected that they would be able to configure their alerts.

1 participant was unsure what ‘Live View’ was.

1 participant felt that ‘Activity’ was a better title for this screen than ‘Your Cocoon’

1 participant said they would want to know when another user was in the app.

1 participant suggested they might want to IM other users via this app.

1 participant expected that they would have to log in to the Cocoon app - the cited the experience of entering a few numbers of a code/password on their banking app, as an example of their expectation.

Version A Version B

Defect Surfacing

Acceptance Testing

Summary

● Prioritisation is a team sport

● Use data to support prioritisation

● Get data from discovery methods

● Iterate design based on learnings

● Develop only what’s required

● Validate - more data!

● Be confident with releases

Experience

● Fluidity and structure

● Time and communication - tools can’t solve

● Appreciate that some decisions have been made

Balance

http://www.yogabalance.co.uk/

Questions?