How to evaluate and implement startup ideas using Hypothesis Driven Development
1–10 of 15 posts
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#2This gives a fresh perspective on the matter. Never thought about evaluating questions this way. Ill give it a try !
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#3The ACH method would be useful in conjunction with this:
http://en.wikipedia.org/wiki/Analysis_of_Competing_Hypothese...
(once you gather data to back your hypothesis)
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#4Seems very much like the practices of customer development part of Lean startups. But leaner.
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#5Seems very much like the practices of customer development part of Lean startups. But leaner.
Thanks, I'll take that as a compliment!
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#6Even better is to aim not for something you can get people to use, but instead try to build something you can charge for immediately
I don't get this. If no one can use it, what are they paying for?
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#7Even better is to aim not for something you can get people to use, but instead try to build something you can charge for immediately I don't get this. If no one can use it, what are they paying for?
Convincing people to pay for something generally entails providing them with something they can use, or at least with the pledge of something they can use.
One common way to go about this is to create a paper prototype, pitch it to potential clients, get them to sign a non-binding letter of intent to buy the product if you develop it as per the specs, and then develop the product and sell it to those people who already told you they'd buy it.
This is as contrasted with the somewhat more common, but often less successful approach of building something useful to a bunch of users, letting them use it for free while you develop the offering, and then asking them to pay.
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#8A fourth question that came up for me was "Will I enjoy doing it if it is a success?" I only focused on this aspect after I asked the question can I make money from it and realized that it was not something I wanted to sustain in the long run.
Once the will I enjoy it question is answered, then Swombat's three questions are definitely the way to go.
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#9A fourth question that came up for me was "Will I enjoy doing it if it is a success?" I only focused on this aspect after I asked the question can I make money from it and realized that it was not something I wanted to sustain in the long run. Once the will I enjoy it question is answered, then Swombat's three questions are definitely the way to go.
That's definitely important for some people. As I said, the exact questions are unique per person/idea combination. What you prioritise first will depend on your skills, your concerns and fears, your past experiences, etc.
For example, if you got burned by building something great that no one actually used, "Can I find users?" will be pretty high up the list.
This is not a method for avoiding all mistakes - it won't save you from all your blind spots. But it gives you a better chance of leveraging your experience and getting somewhere.
I'll write another article at some point about how to generate those questions.
Re: How to evaluate and implement startup ideas using Hypothesis Driven Development
#10A fourth question that came up for me was "Will I enjoy doing it if it is a success?" I only focused on this aspect after I asked the question can I make money from it and realized that it was not something I wanted to sustain in the long run. Once the will I enjoy it question is answered, then Swombat's three questions are definitely the way to go.
That's definitely important for some people. As I said, the exact questions are unique per person/idea combination. What you prioritise first will depend on your skills, your concerns and fears, your past experiences, etc. For example, if you got burned by building something great that no one actually used, "Can I find users?" will be pretty high up the list. This is not a method for avoiding all mistakes - it won't…
Looking forward to reading your article on how the questions are generated and what else goes forward. I have been thinking about this quite a bit after doing a failed startup, working at a startup with funds, and pursuing a startup currently. Thanks for the great blog post.