Presenter: Patrick Goodman Title: Fake it before you make it: Scheduling ‘failure’ in your Project PlanDate: Wednesday, September 30, 2015

2015 PMI Information Systems Technology Symposium

What is Red e App?

The Red e App Journey- January 2012: Business- to- Consumer

secure messaging

- April 2012: Why is there a lack in adoption?...We ask our customers

Failure/Pivot #1

Should we shift our target market?

LessonTalk to users and look for

trends. Be open to a pivot

(Obvious, but often overlooked)

Failure/Lesson #2Not every target

market/user group is the best fit

Failure/Lesson #3Be prepared to adjust

features based on user feedback

Topic-How to build a prototype

-Why to build a prototype

-How to sell failure to stakeholders

-Failure can make you faster

Build a PrototypeMobile-optimized website

-Gather requirements based on user scenarios

-Design and build a skinny prototype

-Review prototype with stakeholders and users

-Watch user interactions

Build a Prototype“The sooner you know how to build a product

that people want to use, you’re ultimately going to

save money and be successful”

The title of this session is

Fake it before you make it and planning to fail

Are you serious?

You talked about faking a prototype, what part of Red e App did you use

this process for?

In Summary-Ask a lot of questions

-Build a prototype

-Get user feedback

-Document and evaluate

What are some of the tools that you used to

build and make your app?

Why did you choose those tools?

How do you gauge success or failure?

Does this process only work for startup companies?

How do you implement this process in a large

corporation?

How do you incorporate speed into product

development?

Should there be consequences for failure?

What is the benefit of having a consequence?

In conclusion-Go fast

-Plan to fail

-Encourage failure

Thank you

Questions?www.PMI.org

@ MarketingMusing

Patrick Goodman