105
Pushing through failure (quickly) @ jeremyjohnson

Pushing Through Failure (Quickly)

Embed Size (px)

DESCRIPTION

"Mantras of startups: "fail fast", "move fast and break things", "keep shipping" - these are all great slogans, but unknown to many - these are really all about learning. It's about getting things in front of your customers early, and often. Watching - and learning. Finding what ideas were not quite as brilliant as you once thought - and finding this out as fast and cheap as possible. How are modern product teams making this happen? Where does User Experience and customer research fit in this model? Taking from Agile, Lean, and User Centered Design - this talk will go over the build-measure-learn process, and how you can start to shape your organization to move fast, without leaving your customers behind."

Citation preview

Page 1: Pushing Through Failure (Quickly)

Pushing through failure

(quickly)@jeremyjohnson

Page 2: Pushing Through Failure (Quickly)

@jeremyjohnson

(yes, we’re hiring)

Page 3: Pushing Through Failure (Quickly)

https://twitter.com/SebastianMourra/status/401066297414676480/photo/1

Page 4: Pushing Through Failure (Quickly)

http://gapingvoid.com/2012/07/03/fail-often/

Page 5: Pushing Through Failure (Quickly)

“fail fast” is actually better

framed as “experiment fast.” The most effective innovators

succeed through experimentation.

http://www.uxbooth.com/articles/fail-fast-fail-often-an-interview-with-victor-lombardi/

- Victor Lombardi

Page 6: Pushing Through Failure (Quickly)

http://www.postalmuseum.si.edu/artofthestamp/SubPage%20table%20images/artwork/athletics/Vince%20Lombardi/vincelambardi.htm

Page 7: Pushing Through Failure (Quickly)

http://uxmag.com/articles/book-excerpt-why-we-fail

Page 8: Pushing Through Failure (Quickly)

“fail fast”

Page 9: Pushing Through Failure (Quickly)

http://en.wikipedia.org/wiki/Freeman_Dyson

Freeman Dyson

Page 10: Pushing Through Failure (Quickly)

Freeman John Dyson FRS is an English American

theoretical physicist and mathematician, famous for

his work in quantum electrodynamics, solid-

state physics, astronomy and nuclear engineering.

Page 11: Pushing Through Failure (Quickly)

“Say something about failure in experiments or businesses

or anything else. What's the value of failure?”

http://www.wired.com/wired/archive/6.02/dyson.html?pg=7&topic=

1998

Page 12: Pushing Through Failure (Quickly)

“You can't possibly get a good technology going without an

enormous number of failures. It's a universal rule. If you look at

bicycles, there were thousands of weird models built and tried before

they found the one that really worked. You could never design a bicycle theoretically. Even now,

after we've been building them for 100 years, it's very difficult to understand just why a bicycle works - it's even difficult to

formulate it as a mathematical problem. But just by trial and error,

we found out how to do it, and the error was essential. The same is

true of airplanes.”

Page 13: Pushing Through Failure (Quickly)

“So you're saying just go ahead and try stuff and you'll sort out the

right way.”

“That's what nature did. And it's almost always true in technology. That's why computers never really took off

until they built them small.”

Page 14: Pushing Through Failure (Quickly)

“Why is small good?”

“Because it's cheaper and faster, and you can make many more. Speed is the most important thing - to be able to try something out on a small scale quickly.”

Page 15: Pushing Through Failure (Quickly)

!“Fail fast.”

“Yes. These big projects are guaranteed to fail because you never have time to fix everything.”

1998

Page 16: Pushing Through Failure (Quickly)

Failing fast = learning with customers quickly

Page 17: Pushing Through Failure (Quickly)

https://twitter.com/davidakoontz/status/402896347470110721

Page 18: Pushing Through Failure (Quickly)
Page 19: Pushing Through Failure (Quickly)

http://siliconangle.com/blog/2013/05/13/has-instagram-become-too-risque/

Page 20: Pushing Through Failure (Quickly)

Systrom, Intuit founder Scott Cook, and Lean Startup author Eric Ries talked about the changes that have swept through product development in both big and small organizations. Many companies have moved from what's called "waterfall development" -- a method that relies on large engineering executing a carefully mapped-out plan -- to "lean" development, where creators move quickly to push out products and revise them on the fly. !"We thought about what we could do to iterate more quickly," Systrom said of Burbn's pivot. "People loved posting pictures on Burbn" -- so that's where they took the venture, jettisoning other planned features. Burbn now lives on only as an abandoned Twitter feed.

http://money.cnn.com/2011/09/13/technology/startups/instagram_burbn/

Page 21: Pushing Through Failure (Quickly)

$

Page 22: Pushing Through Failure (Quickly)

ready?to avoid a slow fail?

Page 23: Pushing Through Failure (Quickly)

Can’t get started?

- problem -

Page 24: Pushing Through Failure (Quickly)

!

!

Ship often. Ship lousy stuff, but ship. Ship constantly.

http://99u.com/tips/6249/Seth-Godin-The-Truth-About-Shipping

Page 25: Pushing Through Failure (Quickly)
Page 26: Pushing Through Failure (Quickly)

Spend too much time planning?

DOn’t talk with your customers?

Find it hard to strip out what’s not valuable?

- problem -

Page 27: Pushing Through Failure (Quickly)

http://www.startupvitamins.com/products/startup-poster-the-longer-it-takes-to-develop-the-less-likely-it-is-to-launch

Page 28: Pushing Through Failure (Quickly)

“The timing of long- range plans is screwed up too. You have the most information when you’re doing something, not before you’ve done it. Yet when do you write a plan? Usually it’s before you’ve even begun. That’s the worst time to make a big decision.”

http://37signals.com/rework

Page 29: Pushing Through Failure (Quickly)

Large team

- problem -

Page 30: Pushing Through Failure (Quickly)

Keep your team small. Smaller than that. No team at all if you can help it.

http://99u.com/tips/6249/Seth-Godin-The-Truth-About-Shipping

Page 31: Pushing Through Failure (Quickly)

A throwback to their days with Jeff Bezos at Amazon, projects are assigned to "two pizza teams," groups of engineers small enough for them to be fed on two large pies. "We want the team to be flat and allow everyone to communicate with each other," Rajaraman says.

http://www.fastcompany.com/1811934/walmartlabs-brings-two-pizza-team-startup-culture-walmart-empire

Page 32: Pushing Through Failure (Quickly)
Page 33: Pushing Through Failure (Quickly)

http://techcrunch.com/2012/11/17/heres-how-spotify-scales-up-and-stays-agile-it-runs-squads-like-lean-startups/

Page 34: Pushing Through Failure (Quickly)

Only launch x times a year?

Looking for perfection?

Try to jam too much into a product?

- problem -

Page 35: Pushing Through Failure (Quickly)

https://twitter.com/tbisaacs/status/387716257283596288

Page 36: Pushing Through Failure (Quickly)

https://frontdeskhq.com

Page 37: Pushing Through Failure (Quickly)

“Great companies focus on their users and ship great products.”http://www.aaronklein.com/2012/02/why-facebook-is-worth-100-billion/

Page 38: Pushing Through Failure (Quickly)

http://fab.com/inspiration/posters-getting-things-done

Page 39: Pushing Through Failure (Quickly)

http://www.startupvitamins.com/products/startup-poster-stay-focused-and-keep-shipping

Page 40: Pushing Through Failure (Quickly)

http://www.startupvitamins.com/products/startup-poster-done-is-better-than-perfect

Page 41: Pushing Through Failure (Quickly)

“real artist ship”- steve jobs

http://gloriamarie.com/stay-focused-and-keep-shipping

Page 42: Pushing Through Failure (Quickly)

It’s going to cost too much to try

that out.

- problem -

How do we know our customers will want this?

Page 43: Pushing Through Failure (Quickly)

The Wizard Of Oz Techniques For Social Prototyping – You don’t need to build everything at first. You can be the man behind the curtain. Krieger says him and Systrom tested an early version of a feature which would notify you when friends joined the service. Instead of building it out, they manually sent people notifications “like a human bot” saying ‘your friend has joined.’ It turned out not to be useful. “We wrote zero lines of Python, so we had zero lines to throw away.”

http://techcrunch.com/2012/11/30/instagram-co-founder-mike-kriegers-8-principles-for-building-products-people-want/

- Mike Krieger, Instagram’s founder

Page 44: Pushing Through Failure (Quickly)

http://techcrunch.com/2012/11/30/instagram-co-founder-mike-kriegers-8-principles-for-building-products-people-want/

Page 45: Pushing Through Failure (Quickly)

404 testing

NEW FEATURE X

Page 46: Pushing Through Failure (Quickly)

http://jeremyjohnsononline.com/2012/12/19/answering-the-question-would-they-use-it-before-you-build-it/

Page 47: Pushing Through Failure (Quickly)
Page 48: Pushing Through Failure (Quickly)

http://www.leemunroe.com/lean-product-development-validate-feature-ideas/

Page 49: Pushing Through Failure (Quickly)

It was an MVP (Minimal Viable Product). I skipped a bunch of features I figured I would implement later. First I wanted to see if people would use it and how they would use it.

Implementing user accounts (in Rails) would take me 2 weekends of work; registration, accounts, saving lists, removing lists, tracking, designing screens, edge cases etc.

I didn’t want to spend the time if it turned out no one signed up so I ran an experiment.

I dropped in a link on the top of the page that said “Sign up to save multiple lists.” and tracked the number of clicks it got with Mixpanel.

(...)

http://www.leemunroe.com/lean-product-development-validate-feature-ideas/

Page 50: Pushing Through Failure (Quickly)

http://www.leemunroe.com/lean-product-development-validate-feature-ideas/

Page 51: Pushing Through Failure (Quickly)

What is the cheapest,

fastest way to learn?

Page 52: Pushing Through Failure (Quickly)

“I dropped over $40k when I could have spent $100”

http://boondainc.wordpress.com/2013/04/18/i-dropped-over-40-grand-when-i-could-have-spent-100/

Page 53: Pushing Through Failure (Quickly)
Page 54: Pushing Through Failure (Quickly)
Page 55: Pushing Through Failure (Quickly)
Page 56: Pushing Through Failure (Quickly)

http://www.savourytable.com/2011/05/mothers-day-and-food-truck-or-two.html

Page 57: Pushing Through Failure (Quickly)

valuable !

!

!

Usable

Enjoyable

Page 58: Pushing Through Failure (Quickly)

Enjoyable

Usablevaluable !

!

!

trying to determine what is…

Page 59: Pushing Through Failure (Quickly)

http://marks.dk/the-post-functional-paradigm-why-all-designs-are-compensations-for-telepathy-and-teleportation

Page 60: Pushing Through Failure (Quickly)

http://bhc3.com/2013/10/31/uncover-latent-needs-with-a-simple-question/

Page 61: Pushing Through Failure (Quickly)

http://thereboot.org/blog/2012/02/19/design-research-what-is-it-and-why-do-it/

Page 62: Pushing Through Failure (Quickly)

http://www.uxmatters.com/mt/archives/2009/07/laddering-a-research-interview-technique-for-uncovering-core-values.php

Page 63: Pushing Through Failure (Quickly)

http://www.shmula.com/jeff-bezos-5-why-exercise-root-cause-analysis-cause-and-effect-ishikawa-lean-thinking-six-sigma/987/

Why did the associate damage his thumb? !Because his thumb got caught in the conveyor. !Why did his thumb get caught in the conveyor? !Because he was chasing his bag, which was on a running conveyor. !Why did he chase his bag? !Because he placed his bag on the conveyor, but it then turned-on by surprise !Why was his bag on the conveyor? !Because he used the conveyor as a table !So, the likely root cause of the associate’s damaged thumb is that he simply needed a table, there wasn’t one around, so he used a conveyor as a table. To eliminate further safety incidences, we need to provide tables at the appropriate stations or provide portable, light tables for the associates to use and also update and a greater focus on safety training. Also, look into preventative maintenance standard work.

Page 64: Pushing Through Failure (Quickly)

valuable !

!

!

Usable

Enjoyable

latent needs

Page 65: Pushing Through Failure (Quickly)

Racing to the right ideas during development

Page 66: Pushing Through Failure (Quickly)
Page 67: Pushing Through Failure (Quickly)
Page 68: Pushing Through Failure (Quickly)

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

Idea or discovery backlog

Page 69: Pushing Through Failure (Quickly)

The Discovery track is all about quickly generating validated product backlog items, and the Delivery track is all about generating releasable software.

http://www.svproduct.com/dual-track-scrum/

- marty cagan

Page 70: Pushing Through Failure (Quickly)

http://www.sebastiangreger.net/writings/concept-design-in-agile-environment/

Iteration Iteration Iteration Iteration

discovery discovery discovery discovery

Implement Implement Implement Implement

design

build

discovery backlog

Page 71: Pushing Through Failure (Quickly)

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

Page 72: Pushing Through Failure (Quickly)

http://www.kontain.com/plat4m/entries/143623/update-to-our-scrum-board/

Page 73: Pushing Through Failure (Quickly)

prototype

Page 74: Pushing Through Failure (Quickly)

fast rough keep moving

Page 75: Pushing Through Failure (Quickly)

test rough prototypes(usually built within a week or less)

Page 76: Pushing Through Failure (Quickly)

(literally 100s) http://looksgoodworkswell.blogspot.com/2012/11/list-of-mockupprototyping-tools.html

http://www.adaptivepath.com/ideas/rapid-prototyping-tools#thelist

Page 77: Pushing Through Failure (Quickly)

lab setting - 6 participants

9:30am

10:30am

11:30am !

1:30pm

2:30pm

3:30pm

Page 78: Pushing Through Failure (Quickly)
Page 79: Pushing Through Failure (Quickly)
Page 80: Pushing Through Failure (Quickly)

valuable Usable

Enjoyable !

determine

Page 81: Pushing Through Failure (Quickly)

clicktest / survey / Etc...

Page 82: Pushing Through Failure (Quickly)

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

ideas

Page 83: Pushing Through Failure (Quickly)
Page 84: Pushing Through Failure (Quickly)
Page 85: Pushing Through Failure (Quickly)

x

x

Page 86: Pushing Through Failure (Quickly)

Core team makes decisions

Done!

the core team

Page 87: Pushing Through Failure (Quickly)

...it is collaborative – the product manager, designer and lead engineer are working together, side-by-side, to create and validate backlog items.

http://www.svproduct.com/dual-track-scrum/

- marty cagan

Page 88: Pushing Through Failure (Quickly)

ideas

failed usability failed to understand failed to find value

ideas

ideas

Page 89: Pushing Through Failure (Quickly)

http://www.startupvitamins.com/products/startup-poster-experiment-fail-learn-repeat

Page 90: Pushing Through Failure (Quickly)

ideas

refine retest

Page 91: Pushing Through Failure (Quickly)

ideas

ideas

Ready for development

Page 92: Pushing Through Failure (Quickly)

ideas

ideas

What’s your kill rate? Ship that bad boy!

Page 93: Pushing Through Failure (Quickly)

Did I mention this happens within a week?

(or less)

Page 94: Pushing Through Failure (Quickly)

Get moving!

Page 95: Pushing Through Failure (Quickly)

LEARNLEAN

Page 96: Pushing Through Failure (Quickly)
Page 97: Pushing Through Failure (Quickly)

combined product teams

#1

Page 98: Pushing Through Failure (Quickly)

core product team

product owner

ux designerdevelopers

Page 99: Pushing Through Failure (Quickly)

one ux designer per team

#2

Page 100: Pushing Through Failure (Quickly)

rough, fast, iterative prototyping

#3

Page 101: Pushing Through Failure (Quickly)

Getting in front of customers weekly

#4

Page 102: Pushing Through Failure (Quickly)

build/test/learn

#5

Page 103: Pushing Through Failure (Quickly)

lean, agile, prototyping, shipping,

ux design master.

in no time at all, you too can be a...

Page 104: Pushing Through Failure (Quickly)

http://blog.web2expo.com/2011/08/interview-with-eric-ries-part-2-what%E2%80%99s-next-for-the-lean-startup-movement-startup-visa-and-lessons-learned/

Page 105: Pushing Through Failure (Quickly)

thanks!@jeremyjohnson

www.jeremyjohnsononline.com