77
blog: jabe.co FAILING principles and practices of Vanity Validation a Paradox of Passionate Commitment WELL

Failing Well Agile 2013

Embed Size (px)

DESCRIPTION

There is a trap hidden inside Lean Startup's CustDev cycle. If entrepreneurs want to be successful, they have to be passionate about their ideas. They need to understand more about their customers than anyone else. I’ve spent the last year lecturing to and teaching entrepreneurs and I've observed that their passion for their idea and their belief that they already DO know everything about their customers can prevent them from actually LEARNING what they need to know in order to create as successful business. The same passion and positive psychology required to succeed in the face of uncertainty is hindering them from learning fast enough to survive. How can we take our passion, our vision, a couple “wild ass guesses”, and produce meaningful, validated learning? The question of how to learn as an organization and how to DEMONSTRATE learning has been explored by philosophers of science and by business theorists for years. What can the Lean Startup Community learn about creating scientifically valid experiments that create actionable knowledge? Learn how to fail well and fail faster by keeping your passion focused on the vision and our dispassionate logic focused on the assumptions.

Citation preview

Page 1: Failing Well Agile 2013

blog: jabe.co

FAILINGprinciples and practices of

Vanity Validation a Paradox of Passionate Commitment

WELL

Page 2: Failing Well Agile 2013

@cyetain

What was the last thing you failed at?

What did you learn?

Did you share your failure with anyone?

Pre-Talk Questions

Page 3: Failing Well Agile 2013

blog: jabe.co

FAILINGprinciples and practices of

Vanity Validation a Paradox of Passionate Commitment

WELL

Page 4: Failing Well Agile 2013

HELLLOOOO McFLYTLC LABS

blog http://jabe.co

Send Anonymous Feedback

http://sayat.me/jabebloom

Joshua (Jabe) BloomCTO : The Library Corporation

& Consulting Practioner TLC Labs

#agile2013

Page 5: Failing Well Agile 2013

@cyetain

Fail Fast

Page 6: Failing Well Agile 2013

@cyetain

Page 7: Failing Well Agile 2013

@cyetain

Learning occurs when we detect and correct error. Error is

any mismatch between what we intend an action to produce

and what actually happens when we implement that action.

-Chris Argyris

Page 8: Failing Well Agile 2013

@cyetain

How Do We Make Better Choices?

Why is it so hard to Fail?

Could we design a system to help?

Page 9: Failing Well Agile 2013

@cyetain

One must treat his theory-in-use as both a psychological certainty and an intellectual

hypothesis.-Chris Argyris

Page 10: Failing Well Agile 2013

@cyetain

How wonderful that we have met with a paradox. Now we have some hope of making

progress.-Niels Bohr

Page 11: Failing Well Agile 2013

@cyetain

Page 12: Failing Well Agile 2013

@cyetain

fake dictionary page from colbertnation.com

Page 13: Failing Well Agile 2013

@cyetain

Although theory without experiment is empty,

experiment without theory is blind.

-Paul Thagard

Page 14: Failing Well Agile 2013

@cyetain

3 Things To Leave With

• Failing Well Produces more Information than Failing Poorly

• “Passionate Beliefs, Loosely Held”

• Reducing Variability too, Soon risks suboptimal result, too Late increases Failure blindness

Page 15: Failing Well Agile 2013

@cyetain

We simply cannot rely on randomness to correct

the problems that randomness creates.

-Don Reinertsen

Page 16: Failing Well Agile 2013

@cyetain

undifferentiated streams of data

Page 17: Failing Well Agile 2013

@cyetain

Page 18: Failing Well Agile 2013

@cyetain

“Research is what I’m doing when I don’t know what

I’m doing.”-Wernher von Braun

Page 19: Failing Well Agile 2013

@cyetain

Page 20: Failing Well Agile 2013

@cyetain

The Principle of Optimum Failure Rate

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Page 21: Failing Well Agile 2013

@cyetain

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Greater Asserted Information

Greater Asserted Information

Page 22: Failing Well Agile 2013

@cyetain

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Greater Asserted Information

Greater Asserted Information

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting Ideas

Page 23: Failing Well Agile 2013

@cyetain

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Greater Asserted Information

Greater Asserted Information

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting Ideas

Uncomfortable

Confident

Page 24: Failing Well Agile 2013

@cyetain

Experience of Failure

Num

ber

of S

ampl

esThe Competency Trap

Page 25: Failing Well Agile 2013

@cyetain

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Page 26: Failing Well Agile 2013

@cyetain

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting IdeasHidden

RiskHidden Value

The Line of SURPRISE!

Page 27: Failing Well Agile 2013

@cyetain

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting IdeasHidden

RiskHidden Value

1

2

3

During Customer Development Focus on Interesting Ideas

Before Scaling Validate Your "We Know This Assumptions" to reduce risk of Failure Demand

After Customer Validation Run experiments to Validate Assumptions of Failure

2 3

1

Page 28: Failing Well Agile 2013

@cyetain

“The typical sequence of coin tosses has high information content but little value; an

ephemeris, giving the positions of the moon and

planets every day for a hundred years, has no more

information than the equations of motion and

initial conditions from which it was calculated, but saves

it’s owner the effort of recalculating these positions.”

-Charles H. Bennett

Page 29: Failing Well Agile 2013

@cyetain

Based on what we know right now, what problems

do we have the least amount of information

about that we can reasonably expect to

understand?

Page 30: Failing Well Agile 2013

@cyetain

Page 31: Failing Well Agile 2013

@cyetain

Risk vs Uncertainty

Page 32: Failing Well Agile 2013

@cyetain

Alteaory vs Epistemic

Uncertainties

Page 33: Failing Well Agile 2013

@cyetain

Gamble Invest

Page 34: Failing Well Agile 2013

@cyetain

Justified MVP

Value of Information

Cost of Acquisition

Cost of MVP

UnjustifiedMVP

Over JustifiedMVP

JustifiedMVP

Page 35: Failing Well Agile 2013

@cyetain

The first principle is that you must not fool

yourself--and you are the easiest person to fool.

-Richard Feynman

Page 36: Failing Well Agile 2013

@cyetain

“Most people don’t know how to learn. What’s more, those

members of the organization that many assume to be the best at learning are, in fact, not very

good at it. I am talking about the well-educated, high-powered, high

commitment professionals” -Chris Argyris

Page 37: Failing Well Agile 2013

@cyetain

“Expertise … breeds an inability to accept new

views.” -Laski

Page 38: Failing Well Agile 2013

@cyetain

Page 39: Failing Well Agile 2013

@cyetain

Vanity Validation

Page 40: Failing Well Agile 2013

@cyetain

I need to be right even if I'm wrong.

Page 41: Failing Well Agile 2013

@cyetain

Defensive Reasoning

Page 42: Failing Well Agile 2013

@cyetain

Remain in unilateral control

Page 43: Failing Well Agile 2013

@cyetain

Maximize "winning"

Minimize "losing"

Page 44: Failing Well Agile 2013

@cyetain

Suppress negative feelings

Page 45: Failing Well Agile 2013

@cyetain

Be as "rational" as possible -- by which people mean

defining clear objectives and evaluating their behavior in

terms of whether or not they have achieved them

Page 46: Failing Well Agile 2013

@cyetain

Mindset Actions

Results Match

Results Mismatch

Single-loop

Double-loop

Page 47: Failing Well Agile 2013

@cyetain

Valid Public Information

Page 48: Failing Well Agile 2013

@cyetain

Page 49: Failing Well Agile 2013

@cyetain

whenever we propose a solution to a problem, we ought to try as hard as we

can to overthrow our solution, rather than defend it.

-Karl Popper

Page 50: Failing Well Agile 2013

@cyetain

• Identify Your Assumptions and Conclusions CLEARLY AS POSSIBLE PUBLICLY

• Question Your Assumptions and Conclusions

• Seek Contrary Data

• Learn when to correct your Actions and when to correct your Mindset

Page 51: Failing Well Agile 2013

@cyetain

http://xkcd.com/

Page 52: Failing Well Agile 2013

@cyetain

Page 53: Failing Well Agile 2013

@cyetain

Abductionnot just for

Aliens

@cyetain

Page 54: Failing Well Agile 2013

@cyetain

[Abduction] goes upon the hope that there is sufficient affinity between the reasoner's mind and nature's to render

guessing not altogether hopeless, provided each guess is checked by comparison with observation... The effort should therefore be to make

each hypothesis... as near an even bet as possible.

-Charles Peirce

Page 55: Failing Well Agile 2013

@cyetain

ABDUCE

DEDUCE

INDUCE

Predictive

Probable

Plausible

The Way

Computers "Think"

The Way

Humans Think

Binary

Probability

Analogue

Justifiable

Page 56: Failing Well Agile 2013

@cyetain

ABDUCE

DEDUCE

INDUCE

Experiences Hypothesises

ExpectedOutcomes

If Coherent

If Expected Outcomes Match Reality

EffectiveMatch

Page 57: Failing Well Agile 2013

@cyetain

ABDUCE

DEDUCEINDUCE

Page 58: Failing Well Agile 2013

@cyetain

ABDUCE

DEDUCEINDUCE

SURPRISE!!!

Page 59: Failing Well Agile 2013

@cyetain

Multi-Hypothesis Research

!=

Page 60: Failing Well Agile 2013

@cyetain

BRAINSTORM

Page 61: Failing Well Agile 2013

@cyetain

TheoriesOpinions

Hypothesizes

The Facts and Just the Facts

Page 62: Failing Well Agile 2013

@cyetain

TheoriesOpinions

Hypothesizes

ConstraintsCriteria

Page 63: Failing Well Agile 2013

@cyetain

TheoriesOpinions

Hypothesizes

QuestionFacts

Page 64: Failing Well Agile 2013

@cyetain

TheoriesOpinions

Hypothesizes Request More Information

Page 65: Failing Well Agile 2013

@cyetain

NO TALKING!

Page 66: Failing Well Agile 2013

@cyetain

How Would I Validate my

understanding of this

problem?How Would I

solve this

Problem?

•Based on your experiences, what would you do to solve this problem? This is your Hypothesis.•Identify What Needs to Be True if your Hypothesis is true.•Assert, Presume, Assume Truth•Imagine Experiments that would justify the Assumptions

Page 67: Failing Well Agile 2013

@cyetain

I Assert that this I know this

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting Ideas

I Presume Somebody knows this

I am going to Assume

this is true for my

Hypothesis to be true

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting Ideas

0% 100%

Probability of Failure

50%

Pote

ntia

l Inf

orm

atio

n

Pretty Sure

theory is wrong

Pretty Sure

theory is right

Interesting Ideas

Page 68: Failing Well Agile 2013

@cyetain

This is my Hypothesis,

Assumptions and

Experiments

ChallengeAssumptions & Experiments

Rotate Pairs 2-3 TimesAllow Time for Revision Between Rounds

Page 69: Failing Well Agile 2013

@cyetain

This is my Hypothesis,

Assumptions and

Experiments

Page 70: Failing Well Agile 2013

@cyetain

Multiple Smaller Experimentsagainst

Multiple Abductive Hypotheses

instead of

Single Large Experimentagainst

Single Hypotheses

Page 71: Failing Well Agile 2013

@cyetain

Failing Well Produces more Information than Failing

Poorly

Page 72: Failing Well Agile 2013

@cyetain

What are You Doing w All that Information?

Incremental: Confirm. Disconfirm.

Iteratively: Select Next Step. Generate More Options

Page 73: Failing Well Agile 2013

@cyetain

Having “Passionate Beliefs, Loosely Held”

FAILURE

MUST

BE AN OPTION

Page 74: Failing Well Agile 2013

@cyetain

Reducing Variability too soon risks suboptimal

result, too late increases failure demand

Page 75: Failing Well Agile 2013

@cyetain

Page 76: Failing Well Agile 2013

@cyetain

Influences &

Sources of More Information

Page 77: Failing Well Agile 2013

@cyetain

Joshua (Jabe) BloomCTO : The Library Corporation

& TLC Labs

blog http://jabe.coSend Anonymous Feedback

http://sayat.me/jabebloom