This document discusses hypothesis-driven development, which involves identifying opportunities, articulating solutions, and minimizing risk. It emphasizes the importance of: 1. Clearly defining the problem and proposed solution through user stories and job stories. 2. Testing solutions quickly through methods like design sprints to collect data and identify assumptions. 3. Getting out of the office to test assumptions and solutions with real users.

1. Hypothesis
Driven
Development
This bit intentionally left blank

2. Me
@ Documaster
x Schibsted
x FINN.no
x Opera Software

3. Vision

4. Execution

5. In this presentation
1. identifying an opportunity
2. articulating a solution
3. minimising the risk of running
off a cliff

6. “A hypothesis is a
proposed
explanation for a
phenomenon”
https://commons.wikimedia.org/wiki/File:Lennuliiklust_uurimas.jpg

7. 1. What game are we
playing?
2. How do we keep
score?
3. What are the next
three things to nail?
*Adam Nash
Product Mgmt 101

8. Insight
Solution
Execution

10. “The horse was the dominant form of human
transportation for 5000 years. [...] So for 5000 years, if you
wanted to make a contribution to personal transportation
it was a better saddle, better breeding, better hooves. And
then in one generation everything changes with the
internal combustion engine.
Much of the time the right strategy is to improve what
you’ve got, and some of the time everything changes.”
Reed Hastings / CEO Netflix

11. By Business Model Alchemist - http://www.businessmodelalchemist.com/tools, CC BY-SA 1.0, https://commons.wikimedia.org/w/index.php?curid=11892574

12. Leadership group
We should
have an app

13. 90% of startups fail
No market need 42%
Ran out of cash 29%
Not the right team 23%
Get outcompeted 19%
Pricing issues 18%

14. What’s so hard about this?

15. 1. The observation
https://hiveminer.com/Tags/bike%2Cchecking

16. (is it worth solving?)
Reach
Impact
Confidence
Effort
(and what’s the consequence of not
doing it?)
https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/

17. 2. The proposed solution

18. User story: As a user, I can backup my entire hard drive.
Job story: When I’m looking for something on FINN.no I want to save my search
be notified of new entries so I can be among the first to know and get a good deal
Problem / solution proposal: Going to the grocery shop is a pain. Let people shop
from home and get their orders delivered.

19. 3. Testability and measurement
(failing early)

20. Measure
and test.
There’s not one, but
many ways of collecting
data points
GV’s design sprint

21. Identify leap of faith assumptions

23. Faking it

24. The law of large
numbers

25. Don’t get stuck in the office
(NIHITO and GO APE)

26. What’s so hard about this?
Execution.