#validatedlearning

So I have [another] idea for a product.

The Lean Canvas app on my phone is my go-to when this happens since it's easy and it's been my assumption that it's a good starting point. Here's one for a previous idea I had:

But since I started listening to The Lean Startup again (instead of reading my book), I thought I should start with the hypothesis instead of a lean canvas. I'm thinking that there may even be waste in some of that canvas. Maybe even spending the mind energy on many of those aspects is futile when I haven't validated the primary value proposition.

So here is my value proposition for one of my latest ideas:

Home owners in WA who are in bushfire risk areas would get value from more advanced warning than is currently possible through checking the DFES Alerts Map. Specifically, they would get value from having a service that could push the alerts/warnings from DFES to their mobile device, when the alert is within a certain distance of their property; a distance which they can control. Thus, the home owner can control the degree of advanced warning.

Here are some of my assumptions with regard to the above (let me know if I've missed any):

Home owners are not satisfied with the ways they currently get warnings/alerts (tv, radio, twitter, friends/neighbours, checking the DFES Alerts Map manually, Emergency Alert).

Home owners want alerts on their mobile device.

Home owners want alerts pushed to them, rather than having to go and "pull" alerts themselves.

Home owners want to control the degree of advanced warning.

Out of those, the "leap of faith" assumption is probably this:

Home owners are not satisfied with the ways they currently get warnings/alerts.

Because if they are, then the whole thing falls over.

So let's start there. I need to test whether home owners in WA who are in bushfire risk areas are not satisfied with the ways they currently get bushfire warnings/alerts. It's funny how planning seems easier than testing. This time I'll try the testing first. Stay tuned.