Is it truly painful 😣 for users? Not just inconvenient—does it actually hurt their workflow or pocket?
Does it happen constantly 🔁? If it's a one-time headache, probably not worth the engineering effort. You need recurring friction.
Can you describe it precisely 🎯? Vague problems get vague solutions. If you can't pin down the exact pain point in one sentence, you're not ready to build yet.
Build only when all three align. The graveyard of crypto projects is full of solutions to problems nobody really had.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
6 Likes
Reward
6
6
Repost
Share
Comment
0/400
BearMarketBuilder
· 9h ago
Well said. Many projects die because of the phrase "I think users need it"... Really, think through the pain points carefully before taking action, or else it's just a waste of gas fees.
View OriginalReply0
MEVictim
· 9h ago
Well said. Many projects die because of "I think someone needs this"... They only think about making quick money and never ask if users really need it.
View OriginalReply0
airdrop_huntress
· 10h ago
Well said, many projects die in this trap... I've seen too many "solutions" that no one actually wants to use.
View OriginalReply0
4am_degen
· 10h ago
That's so true, which is why most crypto projects ultimately fail... There aren't many issues that can be clearly articulated.
View OriginalReply0
YieldWhisperer
· 10h ago
That's right, these three points are especially important in crypto. I've seen too many projects that are just brainstormed on a whim.
View OriginalReply0
SchrodingerWallet
· 10h ago
Oh my God, these three questions really should be memorized by those who randomly create coins... Honestly, nine out of ten projects that fail in the crypto space are just thought up on a whim.
Before you code, ask yourself three things:
Is it truly painful 😣 for users? Not just inconvenient—does it actually hurt their workflow or pocket?
Does it happen constantly 🔁? If it's a one-time headache, probably not worth the engineering effort. You need recurring friction.
Can you describe it precisely 🎯? Vague problems get vague solutions. If you can't pin down the exact pain point in one sentence, you're not ready to build yet.
Build only when all three align. The graveyard of crypto projects is full of solutions to problems nobody really had.