my dad recently asked me what he should actually use an ai assistant for. i’ve spent years building in the ai space, and i honestly couldn’t answer him.
he recently started trying out ai assistants like instinct, muse, dots, etc.
for most of them, you can send a text, and they'll go off and do different tasks for you. the catch is you have to tell them exactly what you want.
my dad doesn’t really have a list of jobs waiting to be handed to an assistant. he also doesn't know what they're capable of, so he doesn't know the right place to start.
people in tech don't have this problem, because we use these tools every day. we connect them to fifty apps and hand them half our tasks.
but people like us are maybe 1% of the world. most people just want something that can solve one clear problem for them, not fifty.
i’ve seen this problem before. when we started wispr, some of the early dictation tools in the market worked decently well, but they were complicated to setup and use. anyone like my dad was never going to do that.
flow took all the setup away and made it something you never have to think about. that’s what made it usable for people like my dad.
before you build technical products, you should be confident that a parent, grandparent, or someone non-technical can understand the problem it solves.
that's how you build tools for the other 99% of people.
- written with @WisprFlow
he recently started trying out ai assistants like instinct, muse, dots, etc.
for most of them, you can send a text, and they'll go off and do different tasks for you. the catch is you have to tell them exactly what you want.
my dad doesn’t really have a list of jobs waiting to be handed to an assistant. he also doesn't know what they're capable of, so he doesn't know the right place to start.
people in tech don't have this problem, because we use these tools every day. we connect them to fifty apps and hand them half our tasks.
but people like us are maybe 1% of the world. most people just want something that can solve one clear problem for them, not fifty.
i’ve seen this problem before. when we started wispr, some of the early dictation tools in the market worked decently well, but they were complicated to setup and use. anyone like my dad was never going to do that.
flow took all the setup away and made it something you never have to think about. that’s what made it usable for people like my dad.
before you build technical products, you should be confident that a parent, grandparent, or someone non-technical can understand the problem it solves.
that's how you build tools for the other 99% of people.
- written with @WisprFlow