Live data from Hacker News

Ask HN: How do you know when to run with an idea?

news.ycombinator.com

1–10 of 11 posts

Re: Ask HN: How do you know when to run with an idea?

#7
Besides the common responses like pick an idea you actually want to work on and will enjoy doing and where you have the skills to do the work needed...

I recommend doing some research into how large companies vet new product ideas and borrowing some concepts from that. I realize MBA-type practices taught in business schools get a bad rap from many folks and frankly a lot of the bad reputation of MBAs is deserved. But there are tools and procedures for how bigger companies decide whether to start a new product line and these are worth learning about. For example, how does Apple decide to launch the iPad or how did they decide to launch the Apple Watch? And how does Apple decide to cancel/not launch the dozens of other internal product ideas they have that don't see the light of day?... Testing the idea, it's market potential and digging into the overall pros and cons and risks of an idea, all have known steps and processes that can work at a startup-level idea too. Nothing is 100% for sure a good idea or bad idea - Plus you don't have to listen to the results of your product vetting, you can launch an idea with low support for it or decide not to launch an idea that has tons of potential, either way I think it's worth taking the time to understand these factors.

Re: Ask HN: How do you know when to run with an idea?

#9
I heard something on the Tim Ferris podcast the other day about how Kevin Kelly (founder of Wired) tries to give away or kill as many of his ideas as possible. If no one takes the idea or he can't kill the idea with a fatal flaw, he knows that he needs to work on that particular idea. That said, ideas are a dime a dozen while execution is priceless.
Post reply on HN