Live data from Hacker News

How do you come up with your ideas for startups?

news.ycombinator.com

1–10 of 15 posts

Re: How do you come up with your ideas for startups?

#2
I've found that the most effective way to come up with ideas is to spend some time alone writing down ideas, usually "aha!" moments that occur while I am doing something completely unrelated. Usually the idea scratches a personal itch I have. After that, I've found that bouncing the idea off of co-founders helps to assert (or reject) that it is a valid business opportunity. How about you guys? What methodology works best for you?

Re: How do you come up with your ideas for startups?

#4
Idea praxis:

There are many ways ...

- make things for yourself & solve your own problems

- take notes in notebook

- observe from nature

- don't be obstinate (in-flexible)

- revise your ideas & filter

- listen to your users

The thing is some ideas are crap. Others maybe ok. But it's what you do with the idea that matters. Turn the idea to a demo. Release the demo and see how many users pick it up. Re-visit your old ideas

It's how quickly you can turn idea to demo. Unleash your ideas in the form of a demo on your users. You'll find out quickly if they are crap or not.

Re: How do you come up with your ideas for startups?

#7
post #5

Notice things that seem broken-- things that should be possible, but aren't (yet).

Or questions that shouldn't be answerable but aren't.

Also, mashing up two abstractions is a good way to narrow down the solution space you are interested in.

For example, IT combines information with technology. PT combines people with technology. CP combines communication with people. TT combines two technologies.

Each mashup has a different set of value propositions that work well with it. IT generally uses tech to manipulate information to answer a question or help people make sense of something. PT generally revolves around augmenting human ability. etc.

Re: How do you come up with your ideas for startups?

#9
post #5

Notice things that seem broken-- things that should be possible, but aren't (yet).

A good place to start this is things you're personally dissatisfied with. Develop a healthy sense of annoyance with the things you use. Start to look for things thought you ought to find really annoying but don't because you've gotten used to them.

I've found it surprising how much this can be honed like any other skill. At first thinking up ideas seems difficult, then suddenly you've got a queue of things you want to build because you're annoyed. Then you go through the queue for things that other people are likely to be dissatisfied with as well.

Hopefully once you're at that point you're better equipped to spot broken stuff that you don't necessarily use (or even want to use). My guess is that not being put up their own online store was not a pain point for Paul and Robert but years of building whatever tools like lacked helped them spot it as a problem others were having.

Post reply on HN