Effective product development starts with internal alignment. Using exercises like Instagram's "Stories Mad Libs" creates a shared, candid understanding of the product's current state. This "organizational therapy" is a prerequisite for overcoming team biases and conducting successful user research.

Related Insights

When research stalls, the bottleneck is often not the methodology or recruiting but a lack of internal consensus on the target audience. The first step should always be audience definition. If the team can't agree, then the initial research project must be to define and validate the audience itself.

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.

The "Owner's Delusion" is the inability to see your own product from the perspective of a new user who lacks context. You forget they are busy, distracted, and have minimal intent. This leads to confusing UIs. The antidote is to consciously step back, "pretend you're a regular human being," and see if it still makes sense.

To create a cohesive product across multiple teams, GitHub uses a framework that forces alignment upfront. By ensuring all teams first deeply understand the problem and collectively identify solutions, the final execution is naturally integrated, preventing a disjointed experience that mirrors the org structure.

Product teams often use placeholder text and duplicate UI components, but users don't provide good feedback on unrealistic designs. A prototype with authentic, varied content—even if the UI is simpler—will elicit far more valuable user feedback because it feels real.

To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.

Instead of debating whether Product Management or Product Marketing "owns" positioning, teams should treat it as a critical point of shared alignment. It's a collaborative space where the entire team agrees on the product's value and market strategy.

The true power of UX research is aligning the entire product team with a common understanding of the user. This shared language prevents working at cross-purposes and building a disjointed product that users can feel.

To bridge cultural and departmental divides, the product team initiated a process of constantly sharing and, crucially, explaining granular user data. This moved conversations away from opinions and localized goals toward a shared, data-informed understanding of the core problems, making it easier to agree on solutions.

Instead of faking expertise, openly admitting ignorance about technical details builds trust and empowers specialists. This allows you to focus on the 'what' and 'why' of the user experience, giving engineers and designers the autonomy to own the 'how', which fosters a more collaborative and effective environment.