Why unvalidated assumption is the enemy of good product

Preview:

Citation preview

Why un-validated assumption is the enemy

of good product?

Quick intro…

What are we trying to achieve in building a

product?

Solutions which meet these criteria

Making assumptions along the way

Why are un-validated assumptions a problem?

Sometimes we get it totally wrong!

So many problems, not enough developers

Validating assumptions maximises our chances of getting to the best user outcome in the

shortest time possible

Creating a culture and process around experimentation

Process should answer key questions

Best way to answer these Q’s is through experimentation and research

Experimentation does not need to be technical

It should be the minimum thing we can do to learn the most of something

How do we validate if something is

desirable/viable?

Qualitative research is critical

‘Talk me through the

last time you did ‘X’’

Concierge

Wizard of Oz

Landing page/video explainer

Fake feature test

How do we validate feasibility?

Define success metrics/criteria up front

Don’t be afraid to change tact

• Start with user problems• List your biggest assumptions• Look to validate your riskiest assumptions before

committing to deliver• Validation should be focused on the minimum thing we

can do to learn the most of something• Define success criteria up front• Don’t be afraid to make tough decisions