01Core service
Hospitality for Businesses
True efficiency starts where the work actually happens.
From the frontline
Not a workshop room. The counter, the pass, the screen, the corridor — and the paper people invent to hold it all together.


Screen recording of a booking being entered twice: once in the channel manager, once by hand in the property system.

Perspective
Strategy looks different from the frontline.
We speak with the people who run the process every day, look at the interfaces between teams and systems, and compare the theory with the reality.
Frontline involvement is not frontline governance. Not every existing way of working is automatically right. But no intelligent solution for a process comes from ignoring the knowledge of the people who carry it.
That knowledge is data for better transformation.
We observe.
A full shift, at the counter and behind it. No interview room.
We listen.
To the people who run the process daily, and to the guests it lands on.
We follow the process.
End to end, including the parts that leave the building.
Then we design.
Workplace, service and system, in that order — with the team, not at them.
The diagram and the day
Four steps on paper. Eleven in reality. The difference is where the cost sits.
The frontline says
Every step someone actually performs, including the ones nobody drew.
11
The process says 4 steps. The frontline says 11. That is where we start.
- 01Request
- Wait
- Manual entry
- 02Approval
- Email chase
- Second system
- Excel export
- Workaround
- 03Execution
- Follow-up
- 04Done
That’s where we start.
Operational friction
What we usually find. Not workplace wellbeing — operational reality.
Duplicate entry
The same guest typed into three systems, because none of them was allowed to talk to the others.
Workarounds
A spreadsheet nobody owns, holding the part of the process the software refused.
Handovers
Knowledge that only survives if two specific people happen to overlap by ten minutes.
Waiting
Not in any report. Measurable at the counter, in the corridor, on hold.
Unclear ownership
Everyone is responsible for the exception, so the exception waits.
Manual intermediate steps
Printing something in order to type it back in. Usually invisible from above.
Two journeys
The same day, read from both sides. Neither one explains the other.
Customer journey
- First contact, and how long it stays unanswered.
- Arrival, orientation, the moment of being recognised.
- The exception: what happens when something goes wrong.
- Departure, and whether anyone would return.
Employee journey
- The first ten minutes of a shift, and what they already cost.
- Tools, screens and the distance between them.
- The exception: who is allowed to decide, and how fast.
- End of shift, and what only exists in someone's head.
What we work on
Design follows observation. Never the other way around.
- Process analysis
- Operational friction
- Customer journey
- Employee journey
- Service experience
- Workplace & process design
- Operational experience
- Transformation
Where to go next
Two core services, and one conversation behind both.
Events built around the whole guest journey — arrival, timing, and what stays afterwards.
Write in your own words. A single person reads it and answers by hand.
Start a conversation