The Situation
The system worked exactly as designed. That was the problem.
A Ryokan booking platform set out to enhance its experience for international travelers by surfacing meal plan options alongside room rates. The intent was sound — traditional Ryokan meals are a defining part of a stay, and making them visible during booking was meant to help travelers understand the full value of what they were booking.
The meal plan labels shown to travelers — "Breakfast Included," "Meal Plan Available" — came directly from the partner property system: the standard data structure the platform used to collect amenity information from accommodation providers. This is the same terminology used across hotel booking platforms globally. The system was working correctly. But it had been built to capture hotel data, not Ryokan data — and it had no field for what a Ryokan meal actually is.
A 30-course seasonal Kaiseki experience, prepared by a chef with decades of craft, using local ingredients that change with the season, was being presented with the same label as a buffet breakfast. As the embedded UX researcher, my task was to surface that gap — and help the team understand that fixing it meant changing what data the partner system collected, not just how the booking page looked.
Research Approach
Understanding both sides: what travelers expected, and what the meals actually meant.
Getting to the right answer required two parallel lines of inquiry — one focused on travelers, the other on the cultural context they were being invited into. Neither alone would have been sufficient.
User Interviews & Usability Testing with International Travelers
In-depth interviews with international travelers from Korea, China, and Taiwan — a group with strong interest in authentic Japanese hospitality but also a range of expectations about how a stay should work. The interviews explored motivations for choosing a Ryokan, what they hoped the experience would feel like, and what concerns surfaced during the booking process. Usability testing showed what actually happened when travelers encountered the meal plan section — where they paused, what they clicked, and critically, what they scrolled straight past. The text labels, it turned out, communicated almost nothing about what was actually on offer.
Cultural Context Analysis with Local Ryokan Hosts
Working directly with Ryokan hosts, the research examined the significance of the meals themselves — the philosophy behind Kaiseki cooking, the role of seasonal ingredients, the care and artistry involved in preparing a multi-course dining experience for guests. This wasn't background research. It produced specific, concrete language and imagery that could bridge the gap between what the booking flow was showing and what the experience actually offered. The hosts were a source of cultural knowledge that had never previously been brought into the design process.
"The travelers we interviewed weren't indifferent to the meals — they were curious. They just couldn't tell from the booking flow whether there was anything worth being curious about."
Key Findings
A valuable experience, invisible behind the wrong words.
The research pointed to a consistent mismatch between the richness of the Ryokan meal experience and the way it was being communicated during booking. Three things stood out clearly.
The Partner System Had No Field for What Ryokan Meals Actually Are
"Breakfast Included" and "Meal Plan Available" were the standard amenity labels the platform collected from all accommodation partners — accurate for hotels, meaningless for Ryokans. The system had no mechanism for a Ryokan to communicate anything beyond those binary options. In usability testing, travelers read the labels and moved on — there was nothing to engage with. The mismatch between the experience being offered and the data structure capturing it was the root cause, and it couldn't be fixed with copy alone.
International Travelers Wanted Flexibility, Not Rigidity
While travelers were genuinely interested in experiencing authentic Japanese hospitality, the interviews revealed an important nuance: they also wanted to explore local cuisine outside the Ryokan. Rigid, non-negotiable meal plans created friction — not because the meals weren't valued, but because travelers felt locked into a structure that left no room for spontaneous food experiences. The meal plan as presented felt like a constraint, not an invitation.
A High-Value Emotional Moment Was Being Missed
Travelers choosing a Ryokan were, by definition, seeking something more than accommodation — they were seeking cultural immersion. The meal section was a natural place to deepen that connection during the booking process itself: to make the cultural richness of the experience tangible before a traveler had even arrived. The current approach wasn't neutral. It was actively squandering a high-value moment of engagement.
What Changed
The fix started upstream — in the partner system, not the booking page.
The research made clear that richer meal plan presentation required richer meal plan data. That meant the solution had to begin with what was collected from properties — not just how it was displayed to travelers.
Partner system — before
"Breakfast Included" / "Meal Plan Available"
Standard hotel industry fields — the only options properties could select. Built for hotels, not Ryokans. No field existed to describe what the meal actually was.
Partner system — after
"A 30-course seasonal Kaiseki meal, prepared just for you, highlighting the best of local ingredients."
A new experience description field, added to the partner intake system, let Ryokans provide culturally meaningful meal context — which then powered what travelers actually saw.
A new field added to the partner property system — The core product change: where properties previously selected from a fixed set of hotel-industry amenity labels, Ryokan partners could now provide an experience description for their meal offerings. This structural change upstream was what made everything downstream possible — rich content couldn't be displayed if it had never been collected.
Visual storytelling powered by richer property data — With meaningful meal descriptions now in the system, the booking page could present imagery of the meals, the chefs at work, and the seasonal ingredients used — giving travelers a genuine window into the experience before they had committed to a booking.
Flexible meal plan options addressed traveler friction — Recognizing that international travelers wanted to explore local cuisine outside the Ryokan, an option to customize or opt out of the meal plan was introduced. Flexibility didn't reduce the appeal of the Kaiseki experience — it removed the feeling of constraint that had made rigid meal plans feel like a deterrent during booking.
The Outcome
Travelers stopped scrolling past — and started engaging.
The reframed meal plan section drove a 27% increase in clicks and interactions. Travelers who had previously moved through the section without engaging were now spending time with it, reading, exploring, and opting in. The improvement wasn't a product of more prominent placement or a louder design — it was a product of clearer, more culturally resonant communication.
The broader lesson was about where UX problems actually live. The booking page wasn't the root cause — the partner data system was. A UX problem that looks like a presentation problem is sometimes a data problem, and the fix has to go to the source. By adding a single new field to the property intake system, everything downstream — the visual presentation, the narrative, the cultural richness — became possible. None of it could have been built on the data structure that existed before.
Results
27%
increase in clicks and engagement with the meal plan section after reframing
3
markets studied — Korea, China, Taiwan — informing one culturally grounded solution
1
new partner system field — the upstream product change that made richer traveler experience possible