Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Instead of focusing on the 'how' (chat vs. voice), DoorDash's AI strategy starts with the 'what': the customer's complete, end-to-end job. For DoorDash, that's getting a physical item delivered. This grounds AI development in solving a real problem, preventing teams from chasing shiny tech without purpose.

Related Insights

To discover high-value AI use cases, reframe the problem. Instead of thinking about features, ask, "If my user had a human assistant for this workflow, what tasks would they delegate?" This simple question uncovers powerful opportunities where agents can perform valuable jobs, shifting focus from technology to user value.

Amazon's "Working Backwards" method requires teams to write a future press release and FAQ before building. This frames complex AI products from the customer's viewpoint, simplifying the value proposition and ensuring the end goal is always clear.

When building complex AI systems that mediate human interactions, like an AI proctor, start by creating a service map for the ideal human-to-human experience. Define what a great real-world proctor would do and say, then use that blueprint to design the AI's behavior, ensuring it's grounded in human needs.

Successful AI strategy development begins by asking executives about their primary business challenges, such as R&D costs or time-to-market. Only after identifying these core problems should AI solutions be mapped to them. This ensures AI initiatives are directly tied to tangible value creation.

The traditional SaaS method of asking customers what they want doesn't work for AI because customers can't imagine what's possible with the technology's "jagged" capabilities. Instead, teams must start with a deep, technology-first understanding of the models and then map that back to customer problems.

Don't let the novelty of GenAI distract you from product management fundamentals. Before exploring any solution, start with the core questions: What is the customer's problem, and is solving it a viable business opportunity? The technology is a means to an end, not the end itself.

Shift the AI development process by starting with workshops for the people who will live with the system, not just those who pay for it. The primary goal is to translate their stories and needs into tangible checks for fairness and feedback before focusing on technical metrics like accuracy and speed.

In the rush to adopt AI, teams are tempted to start with the technology and search for a problem. However, the most successful AI products still adhere to the fundamental principle of starting with user pain points, not the capabilities of the technology.

Instead of writing a traditional spec, the product team at Yelp starts by writing an ideal sample conversation between a user and the AI assistant. This "golden conversation" serves as the primary artifact to work backward from, defining the desired user experience before any technical requirements.

It's easy to get distracted by the complex capabilities of AI. By starting with a minimalistic version of an AI product (high human control, low agency), teams are forced to define the specific problem they are solving, preventing them from getting lost in the complexities of the solution.