Finding Ideas For Your Next Project
nathanbarry.com
nathanbarry.com
I would recommend reading Paul Graham excellent post on "startup ideas" (which could easily translate to "project ideas"):
"The way to get startup ideas is not to try to think of startup ideas. It's to look for problems, preferably problems you have yourself." http://paulgraham.com/startupideas.html
Sometimes asking around about pain points in other peoples lives/businesses can also be very fruitful
So to increase the ways of gaining problem to solve, getting out there to experience different aspects of life and talking to other folks are two sure way of find problems to solve. The side effect is that you will be a more rounded character and will, most probably, enjoy life much more.
Basically, this is what Nathan is saying.
For Nathan his pain point could be something related to writing and publishing books. I think this would be a much better problem domain since he is a user and I am sure he has some problems regarding this process that could be improved.
I think you would be surprised at how many people get confused by "software." I've received answers like "Safari" to this same exact question.
Just a thought, but instead of focusing on providing another piece of software (and phrasing it that way), look to provide business value. I know that's your end result, but I would present it that way from the first interaction.
Also, when you've picked the market/client base you want, I highly recommend seeing if you can visit the business for a day or two (if you can find time.) There's nothing better than immersing yourself...it will lead to better insight.
As to your last paragraph; this is solid advice. I've picked up a few software ideas by viewing businesses "in action" and observing the pain points.
Ditto on the added insight. It also produces a setting where you can ask different questions, on my mind right now are the ones that might have a historical reference. Meaning: was there some reason in the past that made you do things this way now?
Personally, I have seen interesting habits when people switch software and technologies, so they do things a "legacy" way that complicate their process.
Not that I want to advocate for NOT selling a final product, but I find people are sometimes just as happy if you can show them an alternate way of using their current tools. And other times, they end up giving you better feedback on what they really want vs what they think they want.
You can also focus on how much a problem costs them in wasted time or lost revenue.
They are all part of the same thing.
You can choose to be the gold digger or the merchant. It doesn't matter. One is filled with risk but great fortune. The other is more secure but the prospects of making it big are much less.
And the likelihood that the idea and execution will make you insanely rich is so small that I have removed it from my equations these days. Just keep executing though.
My goal for the post series is to create a web app and be transparent about the process. So finding an idea and validating it matches that goal perfectly.
...but only slightly, and i'm still eager to read follow-ups on this experiment!
1) U.S. Bureau of Labor Statistics (www.bls.gov) 2) and FreeLunch.com - http://www.economy.com/freelunch/default.asp
These are tangentially related: - http://blog.eladgil.com/2012/02/entrepreneurial-turbulence.h... - http://500hats.com/niche-to-win
I have more general "starting a startup" links here: http://bitly.com/bundles/o_7ki5mkvgf8/1