AI can create the feature. Is there any way for AI to know when the feature shouldn’t be created?
by•
I have realized that AI code generators make it extremely simple to take my ideas and bring them to life. However, the issue with this approach is that having functioning software does not guarantee that the software is actually useful.
The more features we add to our products just because it is easier to do so, the more complex our products will become.
I try to ask myself one question every time I want to create something new: what exact problem would this solve for users that the current product does not?
How do you know whether or not a feature should be created?
10 views
Replies
The sales team listens to the requests of the customers they are contacting. We recently developed an AI chatbot tailored to our customers' needs.
This customer did not sign a contract with us, and ironically, the customers who made this request also did not use the chatbot service.
In today’s fast-changing environment, I believe it is important to quickly test with prototypes, observe the response, and if necessary, change and test again to verify.
It takes a long time to create the perfect product. By then, it feels as if the era has already passed, and products that were once essential seem no longer necessary.
Set a stop rule before testing the prototype such as users no longer needing a particular spreadsheet or manual step
Then check whether that workaround actually disappears rather than counting clicks on the new feature