3 ms·

You're only identifying a problem, what do you do once you have that idea other than build an MVP to solve it?

owebmaster 10y ago
You build or use an already built proven work tool for the job. The first can take months or years, the second can be immediate. A MVP vaporware is a third but worst strategy, imo. The internet is already full of non-functional & clunky apps, it is difficult to get traction with one more (but can happen, for sure, I just don't think it is a good advice).
- benologist 10y ago
  I can see the value in selling other people's software to solve a problem you've identified but I think that is not really the theme of this thread which is honing in on what your users want. If you are building something to test your nascent idea then is that really any different to building an MVP or "Minimum Viable Product"?
  - owebmaster 10y ago
    benologist, what I was pointing is exactly this. Why do OP wants to know what users want? Is it to make money? If so, I suggest to use an already built technology in place of developing a MVP, because if he is chasing ideas randomly, he probably will not be the best guy to develop a good product around it in a few months, as a lot of startup teams thinks they can and keep failing miserable. It is time to give advices in a different direction :)
    - benologist 10y ago
      I think you're covering pre-launch 'find out what users want' while an MVP and iteration focuses on the next phase of that question, after you launch something and want to start getting into the specifics, 'find out what my users want'.
      - owebmaster 10y ago
        And your point is that any next step after wondering would be a MVP. I don't think it is logically wrong, but I'm talking about "lean startup MVP's" that every student is shipping like crazy nowadays, flooding the internet with useless stuff. I don't mean that this should not be allowed, just that I don't think this proccess is a good approach to create a well succeded technology project. But it is good to learn more about tech, development, and fail fast :)
        benologist 10y ago
        I guess it's more accurate to say the next step is the P from MVP, or the execution of the idea, the MV are optional. MVP advocates putting your product out there at such an early stage to find out if it's actually a terrible idea before you commit to the entire upfront cost of building the complete product. The iteration enables your users and customers to influence product decisions as they arise. These can be positive additions to a project, or just as importantly signal it's a bad idea that isn't worth pursuing further.

You build or use an already built proven work tool for the job. The first can take months or years, the second can be immediate. A MVP vaporware is a third but worst strategy, imo. The internet is already full of non-functional & clunky apps, it is difficult to get traction with one more (but can happen, for sure, I just don't think it is a good advice).

benologist 10y ago
I can see the value in selling other people's software to solve a problem you've identified but I think that is not really the theme of this thread which is honing in on what your users want. If you are building something to test your nascent idea then is that really any different to building an MVP or "Minimum Viable Product"?
- owebmaster 10y ago
  benologist, what I was pointing is exactly this. Why do OP wants to know what users want? Is it to make money? If so, I suggest to use an already built technology in place of developing a MVP, because if he is chasing ideas randomly, he probably will not be the best guy to develop a good product around it in a few months, as a lot of startup teams thinks they can and keep failing miserable. It is time to give advices in a different direction :)
  - benologist 10y ago
    I think you're covering pre-launch 'find out what users want' while an MVP and iteration focuses on the next phase of that question, after you launch something and want to start getting into the specifics, 'find out what my users want'.
    - owebmaster 10y ago
      And your point is that any next step after wondering would be a MVP. I don't think it is logically wrong, but I'm talking about "lean startup MVP's" that every student is shipping like crazy nowadays, flooding the internet with useless stuff. I don't mean that this should not be allowed, just that I don't think this proccess is a good approach to create a well succeded technology project. But it is good to learn more about tech, development, and fail fast :)
      - benologist 10y ago
        I guess it's more accurate to say the next step is the P from MVP, or the execution of the idea, the MV are optional. MVP advocates putting your product out there at such an early stage to find out if it's actually a terrible idea before you commit to the entire upfront cost of building the complete product. The iteration enables your users and customers to influence product decisions as they arise. These can be positive additions to a project, or just as importantly signal it's a bad idea that isn't worth pursuing further.