Exposing Myself To Failure
mrmilksblog.tumblr.com
mrmilksblog.tumblr.com
When hacking tech, this kind of failure analysis happens all the time. In fact, it's not even recognized as failure; it's all flow, most of the time anyway.
When going into business, when I build and they don't come -- that's different, right? Social rejection. A slap in the face. YOW!
Nothing to analyze.
Or is there?
Sometimes, a product launch fails because of a lack of awareness of how people actually buy things:
In [1], we read "The typical potential customer is full of doubt:
* They’re unsure if they want what you’re selling.
* They’re unsure how it would help them.
* They’re unsure if they should trust you, if you’ll deliver.
* They’re unsure if the price is reasonable.
* They’re unsure if they should buy now or wait til later, when the need seems more pressing, or when they remember it again."
Faced with this reality, what hacks are possible?
[1] http://unicornfree.com/2013/3-critical-non-obvious-ingredien...
I built a visual remote designer for the mobile app Unified Remote because I felt remotes should be designed visually rather than with XML (I also wanted to play with using KnockoutJS to generate XML.) No one seemed to care until I posted to the company's Facebook wall. I also emailed the company to let them know and they've since recommended it to people having trouble understanding the XML. I'm also telling you guys :) http://remote-creator.appspot.com
You have to put it out everywhere you can if you want it to succeed. I tried posting my Chrome extension for injecting reviews for doctors into insurance company pages on here and it immediately dropped out of site. It's more universally useful than my other projects: http://github.com/csmatt/doctorratings .
Don't give up!