Hacker News new | past | comments | ask | show | jobs | submit login

We need to teach the highly educated man that it is not a disgrace to fail and that he must analyze every failure to find its cause. -- Charles Kettering

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...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: