Problem
Family trips break down when one generic itinerary ignores different ages, mobility needs, energy levels, stairs and meal routines.
Product × Engineering case study
Travel Planner
Constraint-aware travel planning for families moving at different paces.
The product question
How might a family plan a trip that works for elders, children, mobility needs, pace, stairs, meals and the ordinary compromises of travelling together?
The answer was not another fixed itinerary. It was a planning workflow where people could see the constraints, start with structure and remain in control of every change.
From constraints to validation
Constraints
Capture pace, accessibility, children and elders, meal preferences, and practical travel limits before suggesting a route.
Planner
Turn research and positioning into PRDs and a domain architecture that gives these constraints a first-class place.
Editable itinerary
Start with a structured draft, then let people use manual CRUD and reordering, plus import or export, to make the itinerary their own.
Validation
Test the MVP with families, learn from use, and keep validating the product rather than treating launch as the finish line.
A tested, editable MVP
The core experience is an editable structured itinerary: people can create, update and remove items manually, reorder plans, and import or export travel data without losing their own judgment.
Local and cloud persistence, authentication and traveller profiles support continued planning across sessions. An AI draft can help begin the work; the itinerary remains explicitly editable.
Ongoing validation
This is a continuing product practice: research informs positioning, positioning informs PRDs, and the architecture keeps family constraints visible as the MVP is tested and refined.