Get your free personalized podcast brief

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

Amazon's 'Working Backwards' process begins with the end: a press release (PR) and frequently asked questions (FAQ). This low-cost exercise forces teams to be hyper-focused on customer problems and value proposition from the outset, long before any code is written. It helps filter ideas based on customer impact.

Related Insights

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.

Instead of a traditional product roadmap, give engineers ownership of a broad "problem space." This high-agency model pushes them to get "forward deployed" with customers, uncover real needs, and build solutions directly. This ensures product development is tied to actual pain points and fosters a strong sense of ownership.

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.

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.

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.

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.

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.

Your audience will dictate your product roadmap if you listen. Porterfield's evolution was a direct response to customer feedback. They finished her webinar course and asked what to sell. They finished her product course and asked how to market it. The path to her flagship product was paved with their questions.

Instead of a generic 'ideation' phase, Rainbird's stage-gate process begins with a 'Basis of Interest.' This forces teams to articulate *why* a problem is interesting and worth solving for customers and the business before defining a solution.

A simple but powerful framework for any product initiative requires answering four questions: 1) What is it? 2) Why does it matter (financially)? 3) How much will it cost (including hiring and ops)? 4) When do I get it? This forces teams to think through the full business impact, not just the user value.