We scan new podcasts and send you the top 5 insights daily.
Anne Griffin repeats that whether a product uses AI or not, the work starts with who the customer is, what they are trying to do, and their level of understanding. In cyber risk, that meant turning a wall of vendor data into plain-language highlights and a ready-to-send email.
Anne Griffin warns against adding AI just to say a product is AI, especially when the team has existing customers. She argues that unless you are a frontier lab, copying features without knowing which user and value you are targeting makes the product hard to market and risks leaving customers behind.
A common trap is starting with the assumption that AI must be used, leading to a search for a place to tack it on. This results in superfluous features like a generic "AI assistant," rather than solving a real user need. The correct approach begins with the user's pain.
Many AI initiatives fail because they focus on implementing technology rather than understanding and enhancing the specific customer interactions they aim to improve. A 'customer moment-first' approach grounds the strategy in real-world business outcomes and value.
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.
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.
Anne Griffin says the right UI for the customer gets left behind, and building it is a bigger challenge than people give credit. She points to the wave of AI companies hiring designers because a good model does not automatically make a workflow usable for non-technical users.
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.