Perhaps we should decide what to build deciding who will use it and why they'll use this instead of something else. Then when building the team, maybe we start

Perhaps we should decide what to build deciding who will use it and why they'll use this instead of something else. Then when building the team, maybe we start with who we want working on it and then show them why it needs to be built. When selling it to the decision makers, start with why they should choose it, which is part of choosing who to target for the sale (apart from targeting for the use). The two really go hand in hand, but starting from one or the other in various circumstances makes a lot of sense. Now, if I was selling directly to end users, like home users, I could try to start with target audience (who) first, or start with why people would want the product first. If I don't know who I'm building it for or what those people need, I have to build something pretty general. If I have a market in mind before a prototype to turn into a product, then I can reason more about what niche I'm filling. I guess one can succeed or fail either way, and surely many have.