It isn't always hard to know when to move on. I think a lot of it depends on how big the exploration space is around the product you are trying to build. Build

It isn't always hard to know when to move on. I think a lot of it depends on how big the exploration space is around the product you are trying to build. Building a "I'm confused" feedback button for students attending college lectures doesn't provide much roadway for exploration. You can find out pretty fast whether the product has legs. When the product is something like "a low code developer platform", the space of building is so rich it would be worth building for long stretches of time to learn the right thing to make. The difficult part is in nailing the right product. I would keep working on something like this until someone else has won the market. I am not judging ideas by saying one of the above is better than the other. It's quite possible discovering the lecture solution gets you to a bigger business faster and can create more impact and a bigger company. It just seems like it's easy to weigh the design space of the product, the current state of the market to figure out how long you should work on it.