Investigate why conversion fell after a Host Tools launch

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 recently launched an update to Host Tools intended to help hosts better manage their listings, availability, pricing, and guest expectations. Shortly after launch, the team observes a decline in conversion. For this RCA, treat “conversion” as a marketplace outcome that may be affected by both host-side changes and guest-side booking behavior, especially for remote workers looking for longer or more flexible stays.

Your task is to investigate what may have caused the drop, determine whether the Host Tools launch is likely responsible, and outline how you would narrow the issue using data, product understanding, and marketplace reasoning. Consider that Airbnb operates a two-sided marketplace where changes to host workflows can affect listing quality, availability, price competitiveness, search results, guest trust, and ultimately booking completion.

Frame the problem as if you are the PM responsible for understanding the anomaly and coordinating with analytics, engineering, design, data science, and operations. The focus is not to jump to a fix, but to structure a credible investigation that separates instrumentation issues, seasonality, segment mix, host behavior changes, guest demand shifts, and true product regressions.

The experience should consider:

- How conversion is defined, including funnel step, numerator, denominator, time window, and whether the drop is in search-to-book, listing-view-to-book, checkout completion, or another step.

- Which segments to compare, such as remote workers, long-stay guests, geographies, device types, new vs. returning guests, host cohorts, listing types, and hosts who adopted the new tools versus those who did not.

- Whether the decline began exactly at launch, during rollout, after host adoption, or alongside other marketplace, pricing, traffic, or seasonality changes.

- Instrumentation checks, including event tracking, attribution, experiment assignment, logging changes, data latency, and dashboard definition changes.

- Host-side hypotheses, such as accidental availability changes, pricing recommendations, minimum-stay settings, calendar sync issues, listing quality changes, or host response behavior.

- Guest-side hypotheses, such as reduced inventory relevance, confusing listing information, price changes, trust signals, cancellation policies, or checkout friction.

- Marketplace and competitive context, including supply health, demand shifts, alternative accommodation options, and whether affected guests are moving to hotels, Vrbo, or other platforms.

- Mitigation and prevention thinking, including how to size impact, decide urgency, communicate findings, monitor recovery, and reduce the risk of similar regressions in future launches.

The goal is to demonstrate a clear RCA approach: define the anomaly precisely, validate the data, segment the impact, generate and test hypotheses, identify the most likely root cause, and recommend an evidence-based path for mitigation without assuming the launch is automatically at fault.