During product discovery, Amazon teams ask, "What would be our worst possible news headline?" This pre-mortem practice forces the team to identify and confront potential weak points, blind spots, and negative outcomes upfront. It's a powerful tool for looking around corners and ensuring all bases are covered before committing to build.

Before committing engineering resources, Ather's product team creates a high-quality ad film for a new concept. They then host a full internal launch event, complete with mock media Q&A, to sell the vision to the whole company and create internal accountability before building begins.

Instead of waiting for features to build a story, develop the compelling narrative the market needs to hear first. This story then guides the launch strategy and influences the roadmap, with product functionality serving as supporting proof points, not the centerpiece.

In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.

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.

Amazon intentionally combines "Invent" and "Simplify" into a single leadership principle. This cultural tenet mandates that any new invention must be simplified as it's being developed. The two actions are not sequential or separate; they are fundamentally linked to create a great customer experience.

When handed a specific solution to build, don't just execute. Reverse-engineer the intended customer behavior and outcome. This creates an opportunity to define better success metrics, pressure-test the underlying problem, and potentially propose more effective solutions in the future.

The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.