What came first, the mission or a problem? In your product...
Curious to learn more about how makers approach the 'need' to make a product. I can relate to three ways in which makers say to themselves 'I'm going to invest my time and money into this idea'. 1. You solve a problem for someone. Maybe you're a freelance web developer and you fix one problem for one person because they asked you to and you thought, cool, let's solve that for more people. 2. You invent a problem and then find people that have that problem and give them your solution. This seems to be were missions take the focus. i.e. 'we're on a mission to make X better' - oh cool, I didn't know until just now how much better X could be! 3. You have a problem which you fix for yourself and you find others that also have that problem as you go along. Are there other ways in which you can approach this? Which approach works best? Is there a hybrid? Should the problem (like 1 or 3) come first or the mission (2)?