What’s the best (or worst) decision you’ve made as a maker?
The past few months, I’ve been deep in the weeds building my product. A few choices, some risky, some intuitive, completely changed the direction of the project.
One that stands out: launching before I felt “ready.” Terrifying at the time, but the flood of real feedback saved me months of guessing.
What’s a decision you’ve made that seriously impacted your product or journey?
There’s a lot of quiet wisdom in this community. Let’s surface some of it.
31 views
Replies
@johannagoulart One big lesson for me: I try not to rely too much on feedbacks from friends or family. They usually mean well, but they’re rarely 100% honest. either too positive or holding back from saying what they really think. The most valuable input almost always comes from actual users.
First Answer
@amraniyasser Totally agree! Honest input from real users is where the real growth happen, it’s the same mindset we follow while building First Answer
Honestly, deciding to share my build publicly way earlier than I felt comfortable completely changed things. I had that huge block initially of wanting to do it all privately because what if someone took the idea? It sounds so juvenile now + the feedback I got in the process of doing this shaped the product so much more than my own assumptions.
Risky, but probably the smartest move I’ve made so far.
First Answer
@dheerajdotexe Relatable! Putting the product out there early always feels risky, but the real-world feedback is priceless. Glad it paid off for you, same approach shaped a lot of First Answer too
IXORD
When I first created my product, I built a simple interface for the user. However, later on I decided to change my approach and developed a more complex system, allowing users to fully achieve their goals within the product. This was a significant step, since some users might not be willing to figure out the product, which could reduce conversion. At the same time, it helps reveal the actual number of people who truly need the product.
First Answer
@ixord That’s a really interesting balance, simplicity vs. depth. Sometimes making the product more powerful inevitably raises the learning curve, but like you said, it also surfaces the users who really need it. Valuable insight!