Solo founders: how do you decide what NOT to build?

by•

I have two bad habits that make this harder. I procrastinate, and I give up on things too easily. So I'll put off the boring task that matters, start something new and more fun instead, and then drop that one halfway through too.

I'm trying to fix it by deciding up front what I won't build, so there's less to wander off into. I haven't found a rule that sticks yet.

How do you decide? Do you have a hard rule, a list you check, or do you just go with your gut? And if you've dealt with procrastination as a solo founder, what actually helped?

9 views

Add a comment

Replies

Best

Anything I wouldn't use myself. If I'm not a user, I honestly have no idea what the customer needs.

 That's a good filter. It would've saved me from a few features I built because they seemed cool, not because I needed them. Do you ever make an exception, like when a user keeps asking for something you'd never use yourself?