Before committing to an outcome, teams should ask: "If we achieved this number via methods I'd be embarrassed to see in a news headline, is it a worthy goal?" This simple thought experiment acts as a powerful, practical guardrail against unethical tactics.

As AI lowers the barrier to building, product teams spend less time on execution ('how') and more on strategy and ethics ('should we'). This shift elevates the conversation to focus on consequences, bias, and building the right thing, making product taste a shared responsibility across the entire team.

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 a major initiative, run a simple thought experiment: what are the best and worst possible news headlines? If the worst-case headline is indefensible from a process, intent, or PR perspective, the risk may be too high. This forces teams to confront potential negative outcomes early.

AI tools accelerate development but don't improve judgment, creating a risk of building solutions for the wrong problems more quickly. Premortems become more critical to combat this 'false confidence of faster output' and force the shift from 'can we build it?' to 'should we build it?'.

Treating AI risk management as a final step before launch leads to failure and loss of customer trust. Instead, it must be an integrated, continuous process throughout the entire AI development pipeline, from conception to deployment and iteration, to be effective.

Features designed for delight, like AI summaries, can become deeply upsetting in sensitive situations such as breakups or grief. Product teams must rigorously test for these emotional corner cases to avoid causing significant user harm and brand damage, as seen with Apple and WhatsApp.

Leverage AI to gain external perspectives without meetings. Prompt it to act as a specific persona—like a skeptical CEO, an enthusiastic user, or a New York Times reviewer—to critique your work. This reveals blind spots and strengthens your idea before sharing it.

Before starting a project, ask the team to imagine it has failed and write a story explaining why. This exercise in 'time travel' bypasses optimism bias and surfaces critical operational risks, resource gaps, and flawed assumptions that would otherwise be missed until it's too late.