Liquid Content in Practice: One hotel brand, three locations
- Roman Schurter
- No Comments
Imagine a small hotel brand called AlpineNest with three properties: Zurich (a busy city hotel), Lausanne (French-speaking, conference-heavy), and Lugano (Ticino, more resort-like and with different suppliers).
On paper, AlpineNest already has “documentation”: SOPs, training decks, checklists. But every season the same friction shows up again. New people join fast, the shift moves faster than the manual, and each location insists that things are “slightly different here.”
So AlpineNest rebuilds operations knowledge as Liquid Content using Get More Brains DIFF layer concept: modular content that can be assembled per role, location, and moment.
How the DIFF layers play out in real life
Foundation is what never changes: how AlpineNest wants guests to be greeted, what “good service” means, hygiene basics, and core safety routines.
In Practice: A new front-desk colleague starts in Zurich on Monday. Instead of getting a giant binder, they get a short onboarding path that covers only the Foundation essentials for the front desk.
Localization is what changes by language, culture, or local rules. Lausanne needs French, and a few compliance notes look different than in Zurich.
In Practice: The same onboarding path is reused in Lausanne, but the guest-communication examples and policies appear in French, and the local compliance notes are included automatically.
Operations is how each property runs day to day. Zurich optimizes for speed and early departures. Lausanne has meeting rooms, group arrivals, and conference setups. Lugano follows a different rhythm.
In Practice: A banquet helper in Lausanne opens the “Conference Setup” playbook and sees only what matters for Lausanne, not generic hotel theory.
Detail is the micro-level content that usually breaks traditional manuals: the exact coffee machine cleaning steps, the key-card encoder reset, or the detergent dosing for a specific supplier.
In Practice: Lugano replaces a floor-cleaning machine. The team updates one Detail module, and everyone who needs that instruction sees the new version right away.
Multi-device access brings content closer to the moment of need
Liquid Content does not stop at structure and language. To be truly useful, it must also flow across devices and contexts.
In hotel operations, the right device at the right moment matters. A manager might plan schedules on a laptop. A housekeeper checks room status on a tablet. And during service, when hands are full and hygiene rules are strict, a smartphone becomes the only practical option.
AlpineNest designed its content system to work seamlessly across all three: desktop for planning and training, tablets for mobile coordination, and phones for quick checks during shifts.
In Practice: A chef in Zurich’s kitchen needs to check the new dishwashing procedure during service. Laptops are not allowed in the kitchen for safety and hygiene reasons, so she pulls out her phone and quickly scans the updated “Dishwashing Protocol” on her mobile device.
Later that evening, the General Manager of AlpineNest in Zurich reviews the same dishwashing protocol on his laptop while planning a training session for the kitchen team. He sees the full context, including compliance notes and supplier details, and can add annotations for the upcoming team meeting.
What changes for AlpineNest?
Instead of maintaining three slightly inconsistent manuals, AlpineNest maintains a set of reusable building blocks. New hires get role-based onboarding, teams see the right location-specific routines, and updates happen once at the source and then flow into every assembled “playbook.”
Liquid Content is not just nicer documentation. It enables faster localization, higher adoption in day-to-day work, simpler product bundling across use cases, and more realistic recurring revenue models because the content stays alive and updateable.
Liquid Content becomes real when three pillars work together: modular, semantic content (for example with bitmark), AI workflows that transform and contextualize reliably, and a flexible interface where people can annotate, store, and share in real work.