Deciding what is enough to include in a feature - is easy to go down a rabbit hole wanting to add more and more complexity. We have had to step back and discuss what is enough for MVP.
I have two:
1. Starting up full time at a very early stage without a fallback
2. [The harder one] To decide to wind up the startup when we realized we things are not working.
Stick with one idea. There are too many thoughts in my head. Focusing on one direction has always felt like a sacrifice for everything else. So I constantly ask myself why this particular product is more important for me than anything else. And I'd better have a good answer for that.
Report
@mary_rumyantzeva i love this! Before I work with founders I always give this as a HW assignment lol for them to answer - why is this particular problem worth solving? X what is your personal connection to the problem / what makes you uniquely equipped to solve it? (What edge/insight/expertise do you have over any competitors) I think doing this always helps founders feel more confident PLUS having a personal connection will keep you motivated in the many lows as you work towards product market fit!
I love a problem obsessed vs a product obsessed founder!
@ashleylivingagile, thank you! So well said! Love your points about obsession and personal connection!
Report
Deciding when to pivot was tough. Initially, I built a feature-packed solution, but customer feedback was lukewarm. Realizing I was solving the wrong problem stung, but in hindsight, pivoting was the right call.
Replies
Gauge.it
Dezan.cc
Pythia World
Pythia World
Steppy by StageKeep
Making Today
Gradienty
SigmaRemote