lean prototyping - presentation - redesign

THE LEAN PROTOTYPING

PLAYBOOKPresented By: Kristian Bouw

former co-founder of a failed startupBuilt product without validating assumptions

Could have saved 2 years and 6 figures with the shit I know now

Current founder at notion theoryLean startup consultancy helping startups build and launch their web/mobile product in 3 weeks

Launched with $20k in pre-sales

Solving Design + Product Problems Solving Business + Product Problems

what you thinkyour product looks like

REALITYthe hARSH

a minimum viable product isn’t just the product

it’s an approach to building the product

ask yourself

“What are the minimum features required to

provide tangible value to a single customer?”

mvp product

nail it beforeyou scale it.

IDENTIFY CUSTOMER’S PAIN POINTS1

2 VALIDATE POTENTIAL SOLUTIONS

your greatest fear should be

solving the wrong problem

(or even worse)

solving nothing at all

Their time

stopwasting

(but more importantly)

please stop

your ownwasting

time

turning your ideas into

testable productsSketches Wireframes Prototype

GOALHelp you conceptualize your idea and validate internally

SKETCHES

SKETCHES (aka freestylin’)

GOALHelp you visualize your

idea and validate externally

wireframes

wireframes

wireframes (low-fidelity design)

GOALHelp you give your

application an accurate sense of look and feel

mockups (hi-fidelity design — optional)

mockups

GOALCreate a mock application

(with dummy data) that simulates a working product to get

real user feedback

prototype

Your prototyping

toolboxSketches wireframes

mockups prototypes

Balsamiq

UXPin

Mockflow

InvisionApp

MarvelApp

Proto.ioBalsamiq

Proto.io

Photoshop

Pen & paper

Spaghetti-O’s

iPad & stylus

everything is an

experiment

changeperspective

fail fast, fail often learn fast, learn often

and don’t

forget

build measure learn

what you should do right now

step 1

step 2

Setup 30 meetings with potential customers

These are people you have identified as having the core problem you’re trying to solve

Use first 10 meetings to extract ideas and sketch potential solutions

You should be listening 90% of the time and sketching potential solutions

step 3 Build product wireframes and externally validate with next 10 meetings

Wireframes give your product the tangibility and context needed to test as a viable solution

step 4 Build prototype and get traction with last 10 meetings

Prototypes give you the best opportunity for feedback b/c they simulate the real application

(thanks)

say hellokristian@notiontheory.com

!@kristianbouw

!www.notiontheory.com