flâneur

LukeW | What Do You Want To AI?

lukew.com · 232 words · saved by 1 readers

Alongside an increasing sameness of features and user interfaces, AI applications have also converged on their approach to primary calls to action: "What Do You Want To ___?" But is there a better way... especially for more domain specific applications? Looking across AI products today, most feature an open-ended text field with an equally open-ended call to action: So many questions. I've even turned them into a running joke. When a financial company integrates their AI: "What do you want to bank?" or "What do you want to accountant?" Silly I know, but it illustrates the issue. People often don't know what AI products can do nor how to best instruct/prompt them. Questions just exacerbate the issue. It may be a small detail but instead of asking, how about instructing? Reve's image creation call to action says: "Describe an image or drop one here...". Bench's AI-powered workspace starts with: "Describe the task you want Bench to do...". Both calls to action are still open ended enough

Alongside an increasing sameness of features and user interfaces, AI applications have also converged on their approach to primary calls to action: "What Do You Want To ___?" But is there a better way... especially for more domain specific applications? Looking across AI products today, most feature an open-ended text field with an equally open-ended call to action: What do you want to know? What can I help with? What do you want to create? What do you want to build? What will you imagine? Ask anything... Ask a question... Ask [AI tool]... So many questions. I've even turned them into a runnin

related reading