Resolve a cross-functional conflict blocking Guest App at global scale

Problem Statement Description

Product context: Airbnb is a travel marketplace connecting guests and hosts; its products include stays, experiences, host tools, guest booking, trust and safety, payments, and reviews.

Airbnb’s Guest App team is preparing a global-scale initiative focused on improving the family travel experience, from discovery and trip planning through booking, arrival, and support. The work is blocked by a cross-functional conflict: product, engineering, design, data science, trust and safety, legal/policy, host operations, customer support, and regional teams are not aligned on whether the experience is ready to launch broadly, which risks to accept, and who owns key decisions.

The candidate should frame how they would unblock the organization while protecting Airbnb’s marketplace quality, guest trust, host supply health, and global operational readiness. The scenario involves real execution complexity: families may have higher expectations around safety, amenities, cancellation flexibility, listing accuracy, accessibility, payments, and support responsiveness, while hosts and regional teams may face uneven readiness across markets.

This is not a request to design the family travel product itself. The focus is on how to diagnose the source of conflict, establish decision-making structure, sequence work, align stakeholders, manage trade-offs, and drive a launch or no-launch decision for a high-stakes Guest App initiative at global scale.

The execution plan should consider:

- The specific stakeholder groups involved, their incentives, concerns, decision rights, and potential points of disagreement.

- How to separate opinion-based conflict from evidence-based risks using data, customer insights, operational readiness, and market feedback.

- Ownership across product, engineering, design, legal, trust and safety, support, host teams, regional operations, marketing, and analytics.

- Dependencies such as localization, policy differences, host education, support tooling, quality standards, experimentation, and app release cycles.

- Sequencing options, including pilots, phased market rollout, limited cohort launches, or feature gating where appropriate.

- Go/no-go criteria, launch readiness reviews, escalation paths, and how unresolved risks would be documented and decided.

- Rollback, mitigation, incident response, customer communication, and host communication plans if the rollout creates marketplace or trust issues.

- How to maintain momentum and team trust without ignoring legitimate concerns from functions responsible for safety, compliance, or operational quality.

The goal is to show how you would lead through ambiguity and conflict as a product leader at Airbnb: creating clarity, forcing the right decisions at the right level, balancing speed with trust, and establishing an execution path that can scale across global markets without compromising the guest, family, or host experience.