Company Context

Meta operates global social platforms including Instagram, Facebook, Messenger, and WhatsApp, with billions of users and strong network effects around identity, communication, and content sharing. Travel is already a common behavior across Meta surfaces, but it is fragmented: people discover destinations on Instagram, coordinate plans in WhatsApp or Messenger, and share memories after the trip.

Problem

Meta wants to improve social travel: helping people plan, coordinate, experience, and share trips with others. Internal research shows that group travel planning is highly fragmented, with users switching across chat apps, shared docs, maps, and booking sites. Users report three recurring pain points: deciding where to go, aligning on itinerary and budget, and keeping everyone coordinated during the trip. Meta believes it can win by connecting discovery, planning, and coordination across its existing social graph rather than building a full booking platform.

Assume you are the PM responsible for defining an MVP that could live primarily in Instagram and/or WhatsApp. The goal is to increase meaningful social engagement around travel without creating a heavy, enterprise-style planning tool.

Deliverables

1. Define the target user segment(s) and the highest-priority travel job to be done.
2. Identify the biggest unmet user needs in social travel and explain why Meta is well positioned to solve them.
3. Propose the product vision and MVP, including the core user flow and 2-3 key features.
4. Prioritize what you would build first versus defer, with clear trade-off decisions.
5. Define success metrics and explain how you would assess product-market fit after launch.

Constraints

• MVP must launch within 6 months using existing Meta surfaces rather than a brand-new standalone app.
• Team capacity is limited to one cross-functional squad; assume modest engineering and design resources.
• The product should not depend on handling payments or bookings in the first release.
• Privacy and trust matter: users may not want all travel plans broadly visible across their network.
• The solution should work for both trip planning before departure and lightweight coordination during the trip.