←back to thread

721 points ralusek | 1 comments | | HN request time: 0.204s | source
Show context
ryandrake ◴[] No.41870217[source]
I'm making some big assumptions about Adobe's product ideation process, but: This seems like the "right" way to approach developing AI products: Find a user need that can't easily be solved with traditional methods and algorithms, decide that AI is appropriate for that thing, and then build an AI system to solve it.

Rather than what many BigTech companies are currently doing: "Wall Street says we need to 'Use AI Somehow'. Let's invest in AI and Find Things To Do with AI. Later, we'll worry about somehow matching these things with user needs."

replies(15): >>41870304 #>>41870341 #>>41870369 #>>41870422 #>>41870672 #>>41870780 #>>41870851 #>>41870929 #>>41871322 #>>41871724 #>>41871915 #>>41871961 #>>41872523 #>>41872850 #>>41873162 #
1. kenjackson ◴[] No.41872850[source]
That approach makes sense for very specific domain-tethered technologies. But for AI I think letting it loose and allowing people to find their own use cases is an appropriate way to go. I've found valuable use cases with ChatGPT in the first months of its public release that I honestly think we still wouldn't have if it went through a traditional product cycle.