How a “reverse-engineered” approach can reduce a complex product launch to a single conversation
This article opens the practical section of the Scenario-Based Care Journal.
In the previous articles, the perspective was observational — looking at the current state of the travel and hospitality industry through a practitioner’s lens: where the body breaks, where the gap in service lies, why the host is the key figure, and what prevents the problem from being solved.
The next few articles draw on accumulated practice — years of running tourism operations, designing travel kits and care scenarios, working with decision detox from its minimal form to its maximum. What follows is not theory about how care should work — it is what the authors of this journal learned by building it.
Resistance to change is useful and rational
If you run a hotel, a tour company, a yacht fleet, or any other business in travel and hospitality — you know how hard it is to get processes right. People are involved on every side: staff, guests, subcontractors, suppliers, each with their own variables. These are complex, hands-on businesses. Everything is held together by feel, by experience, by years of iteration. So much emotion, so much physicality, so much that can’t be controlled.
So if a process works, the best decision may be to leave it alone. If it isn’t broken, don’t fix it. Any new addition — even a brilliant one — means training, risk of disruption, and the chance of breaking something that was hard to build in the first place.
The first thing worth saying about implementing scenario-based care: the resistance to change is rational. The instinct to protect what works is correct.
The authors of this journal spent years running tourism businesses — rebuilding companies, introducing changes, living on the operator side. Anyone who has done this knows first-hand what it means to implement something new — how even the most necessary and positive changes can be met with resistance, sabotaged by staff, and quietly despised by everyone involved.
Which is exactly why scenario-based care was designed in reverse: the product is complex — but the host’s side is kept as light as possible. No new systems, no retraining, no process redesign. The care layer fits into what the host already does.
When the host is on the side of simplicity
In our own past tourism businesses — and later at ÓCOMO — we went through every stage of building scenario-based care. First, we recommended what guests should bring — specific products for specific routes and conditions. Then, as we moved upmarket and increased the level of decision detox, we started providing more on-site. Eventually we pushed simplicity for our guests as far as it could go: even on a demanding expedition, they could arrive in ordinary clothes. Scenario kits evolved through every format — from full-size jars to travel tubes to single-dose capsules. We can say with certainty: building a scenario-based care system inside your own company is hard.
But here is the point. There is a distinction — between simplicity before complexity and simplicity after it.
A product that looks simple because nobody solved the hard problems underneath is the first kind. Easy to start with — but every downstream consequence becomes your problem.
A product that looks simple because someone else already absorbed the complexity is the second kind. The difficult work was done before it reached you.
Here is what scenario-based care looks like now — on the supplier side:
Every formula is developed in dialogue with the laboratory — not just for efficacy, but for mutual compatibility. If a guest applies SPF in the morning and an anti-mosquito product an hour later, those two formulas must not interfere with each other. The order of application matters; ingredient profiles must be designed as a sequence, not as isolated products.
Once formulas are approved, they are tested for compatibility with single-dose packaging — because a capsule is a different environment from a jar, and the formula must remain stable in it. Each product is then certified individually as a standalone cosmetic under EU regulation — CPSR, PIF, CPNP, GMP. Only after that do the mono-doses arrive at the warehouse, where they are assembled into scenario-based sets.
This is serious, unglamorous, detail-obsessed work. The host never touches any of it. What reaches the host is a ready set, assembled for their scenario, with all documentation included. The authors of this journal were hosts themselves — on the hard side of that equation — and learned how much better it is when someone else absorbs it. That is why scenario-based care is now built so that the host’s side is as simple as it can possibly be.
No briefs, no forms — just talk
A host who has been working in their field for any significant time develops pattern recognition — what guests ask about most, which types of guests come, what problems keep repeating.
A hotel on the Camino de Santiago sees it year after year: guests arrive with exhausted feet, ask at reception where to buy plasters, whether there’s a pharmacy nearby. The hotel has stood in the same place for years — the pattern is identical every season. A trekking operator in the Alps hears the same complaints every group: sunburn on the first day, blisters by the third, dry lips from altitude wind. A boutique hotel in Barcelona or Rome knows it too — guests walk fifteen to twenty kilometres a day through museums and streets, and by evening their feet and skin tell the same story as a light trek. It’s an informal guest portrait — a cloud of recurring problems built from observation.
Hosts also know the patterns of place, timing, and even anomalies — in Scandinavia the midge season arrives at the same time every year, in the same locations. In Berlin, a genuinely cold winter comes once every ten to fifteen years. In northern Spain, heat can alternate with rain so that you manage to get both sunburned and frozen in the same day. A wellness hotel with a thermal spa sees the same post-treatment dryness after every pool rotation — the guest’s skin needs one recovery step, not a full-size jar from the boutique.
Hosts accumulate this knowledge naturally — it’s the information guests keep asking about, the problems that keep repeating. These are not newcomers. They’ve been running their operations for years. They know their location intimately.
The host doesn’t usually think of this as “a scenario” — the word is new. But the information is there. The scenario is composed by the supplier — the host simply describes their situation in whatever way feels natural: a voice message, an email, a conversation. From that, together, the most obvious starting point emerges — the low-hanging fruit for the first launch.
The principles behind the simplicity
The simplicity rests on a few specific principles that carry the structural weight. Understanding them is what makes the simplicity believable.
Timing and precision. Scenario-based care works in a rhythm: protect before the stressor, support during exposure, recover after. Preventing a blister takes thirty seconds of barrier cream in the morning. Treating one can cost a day of the trip — or a whole trip.
Format solves logistics, safety, and waste in one move. A monodose is sterile, pre-measured, and fully consumed. No open jars, no cross-contamination, no leftovers, no staff training on dosing. One capsule, one moment, one purpose — the guest doesn’t choose, doesn’t measure, doesn’t make mistakes. Each capsule is individually certified. The format carries the safety — the guest sees only the result.
The system is assembled, not custom-developed. Sets are built for a specific route, context, and rhythm — from a library of tested, certified capsule formulas. What changes between sets is the combination. The building blocks are already proven. That means no lengthy formula development from scratch, no high minimum orders, no frozen stock. How the offering adapts to each host’s specific business — that is the subject of a later article.
Where the process starts
A host describes their situation. The supplier proposes a first set based on the most obvious stressor — the one the host would describe with their eyes closed — and explains why this particular set, what problems it addresses, and how it works. A first batch arrives — assembled from the library of formulas, matched to the host’s real scale. The host places the sets in the touchpoint that best fits the existing service flow — minibar, reception, a booking package, or another natural point of contact. In most setups the sets are self-explanatory enough that guests understand them without further explanation. Calibration happens after the first guests.
Almost nothing changes in the host’s current operation. No new system is installed, no workflow is redesigned. A thin care layer sits on top of what already works — and the host’s effort is limited to placing the sets and reordering when needed.
From the guest’s side, however, this is anything but small. It is a tangible gesture of care, designed specifically for their situation. Someone thought ahead, prepared, and placed the right thing at the right moment. That is what the guest remembers.
Core Concepts
Scenario-based care — the discipline of designing physical comfort into the rhythm of a guest journey, treating care as a service layer rather than a product category.
The two-layer model — the separation of hygiene infrastructure (Layer 1: soap, dispensers, basic products — managed as CPOR) from scenario-based care (Layer 2: optional, context-specific, tied to the guest’s actual day).
The Host — the hotelier, operator, guide, or captain who holds the actual context of the journey. Knowing the weather, schedule, and physical stressors in advance, they co-design the scenario-based care layer for their business.
Absorbed complexity — the design principle where the supplier carries the regulatory, formulation, and logistical weight so that the host’s integration requires no specialised knowledge, no process change, and no compliance burden. The host’s side is thin by design — not by omission.
Pattern recognition — the host already knows the scenario. Guests with exhausted feet, sunburned faces, dry skin after a thermal pool — these patterns repeat every season. The word “scenario” is new. The knowledge isn’t.
Frequently Asked Questions
How difficult is it to implement scenario-based care? The goal is maximum simplicity on the host’s side. You describe your situation — we propose a solution. No complex briefs, no lengthy approvals. We handle the entire technical side: formula selection, logistics, documentation. You receive the sets, place them at the right touchpoint, and reorder when stock runs low. In most setups, no special guest explanation is needed — the packaging and the context do the work.
What’s the minimum order? The first launch is based on actual needs and kept reasonable. A boutique hotel with 100 rooms is one situation — start from real occupancy and adjust volumes gradually. A boutique tour operator running groups of 10 is another. The approach is sensible and surplus-free: if you have three upcoming groups of seven, you don’t need 50 sets — 21 will do. It is better to resupply and stay current than to store excess inventory.
What about guests who might react to a product? Risk is minimised at every level. First, hypoallergenic formulas. Second, monodoses are sterile — meaning cleaner compositions with fewer preservatives. Third, full ingredient lists are provided; a monodose is, technically, a standard cosmetic product with all legally required documentation. Fourth, the responsible person is the manufacturer, backed by an insurance policy. In short, the same principle as everything else in scenario-based care: minimise risk by design, manage it during the process, and handle it if something goes wrong.
← Previous: The Complete Case: Why Scenario-Based Care Is the Logical Next Step
→ Next: The Rhythm and the Format: Why in Scenario-Based Care Everything Is Connected