3 ms·
The problem probably wasn't that you didn't have enough features. The problem was that your minimalist feature set didn't solve any real problems for anyone.
by huhtenberg 7y ago
The problem probably wasn't that you didn't have enough features.
The problem was that your minimalist feature set didn't solve any real problems for anyone.
You must've been aiming at people with complex problems, which required complex solutions, so it's unsurprising that that you had to have a feature set to match to be actually useful.
- meerita 7y agoYou don't need to solve problems too. You can create needs instead and they're much more stronger than problems http://minid.net/2019/07/30/on-building-products-for-necessities-instead-for-solving-a-problem/ http://minid.net/2019/07/30/on-building-products-for-necessi...
- jmatthews 7y agoIt's a good concept but needs fleshing out I think. I understand the thrust of the idea but it could also be seen as just playing word games. What specifically is the difference between a need and a problem? What methodology might one use to search for needs? I wish this idea were a bit more developed.
- meerita 7y agoSemantically are different things. A problem is a doubt and a need is driven feeling. Both things can cross in a situation but isn't apply 100% of the times. Since both need and problems can be subjective, the idea is to trigger the need instead of finding posible problems to solve. As the rule #1 say: not everyone has a problem, but you can create a need in everyone.