image

Whose issues are you trying to solve and what issues are you trying to solve with what you are trying to create?

  • It doesn’t matter who the “who” is, it can be “me.”
  • When solving “issues” for “others,” ask yourself, “How is that person solving the issue right now?” Think about
    • If it’s resolved, there’s a competitor.
    • If it’s not resolved, then that person isn’t in much trouble if it’s not resolved.

from /villagepump/2024/10/09

  • However, it’s possible that people don’t really think “it’s technically solvable” when it comes to something new and possible, and if that’s the case, it’s also possible that there is no competition to solve it at this point in time.
    • I’m starting to think this is chasm after all.
    • The “people who are enthusiastic when shown that they can do something they thought they couldn’t do (the minority)” and the “people who decide whether or not to hire someone based on whether or not they are useful to them (the majority).”
    • [I guess the latter is the case, but I wonder if this can be designed in advance.
      • I don’t know
      • Maybe I just don’t know because I’ve never created a service that would be popular with the masses.
    • There are those who say, “If you asked the customer what he wanted, he would have said he wanted a fast horse,” and there are those who say, “No individual can represent the market.”

This page is auto-translated from /nishio/ç«¶ćˆăŻă„ăŸă›ă‚“ using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.