2. Systems Create Freedom

Why systems and checklists are not the enemy of personal hospitality. 

The routine should be systematized so the team can devote attention to the situations that require judgment.

The Fundamentals Come First

The more personal you want hospitality to be, the better the fundamental systems need to function. That may sound backwards, but bear with me. 

We want the guest experience to feel relaxed, spontaneous, and human. We want people on our team to use their judgment, have real conversations, notice opportunities, and sometimes do things that are not in the playbook. 

It is easy to assume that systems, checklists, task management, written procedures, and operating discipline push things in the wrong direction. Too much process can make a place feel corporate. Too many scripts can result in performative hospitality. 

We understand the concern. But it’s not black and white, not all processes are bad for hospitality. A well designed system does not make the guest experience more rigid. It removes friction from everything around it allowing space for personal hospitality to take place.

If the team is searching for an arrival time, wondering whether someone confirmed the restaurant, trying to figure out who owns a maintenance issue, looking through texts for a decision, or asking a guest to repeat something they already told us, we are spending our attention on things that should already be handled - and guests take notice.

That attention has to come from somewhere and in a small hospitality business, it comes from time that could be spent on the guest.

I learned this long before getting into hospitality. In startups, I saw the benefits of teams mastering the fundamentals: clear ownership, writing things down in a single source of truth, answering questions directly, preparing for meetings, documenting decisions, following through on commitments, and making sure work has a defined next step.

Some see that as overhead. We see it as friction removal. The objective is not more administration. The objective is to make administration fade to the back.

Why Friction Is Expensive

Most friction seems trivial when you examine one instance at a time.

Someone sends an email and does not hear back. The next week they realize the answer is now holding up their work. They check email again. They wonder if the answer came through a different channel, perhaps the team messaging app or the task tracker. They search, then follow up.

Nothing catastrophic happened. Maybe only five minutes were lost. But the real cost is the interruption and the impact on momentum. The unanswered question has to be remembered. They have to stop what they are doing, reconstruct the context, search for information, decide what to do next, and then return to the work they were doing before.

Multiply that across a team, hundreds of decisions and requests, months of work, and different time zones. The cumulative cost becomes enormous.

This is why small operating habits matter so much. A quick acknowledgment with a promised answer date prevents someone from wondering whether a message was received. Meeting notes with clear decisions, next steps, dates, and owners prevent people from reconstructing a decision later. A clear owner prevents three people from half-owning something while each assumes someone else is handling it. A next-step due date makes the next milestone visible. Updating the source document after a decision prevents an old assumption from carrying forward or the same discussion from having to be revisited later.

None of these practices is complicated. That is exactly why they can be easy to dismiss.

Pace Creates Opportunity

We like efficiency. There is nothing quite like the energy of an aligned team moving quickly and getting things done together. But speed is not the goal. Pace matters because it creates momentum, and momentum creates opportunity. 

Moving quickly closes loops. It keeps work from accumulating and consuming valuable time as the same issues are discussed week after week. It prevents small ambiguities from turning into larger ones. It creates more options because problems are spotted while there is still time to do something about them.

Most importantly, pace creates space. When the basic work is handled promptly, you have more time for the work that makes hospitality special. 

You can think ahead instead of catching up. You can notice a risk before it becomes a crisis. You can spend time with a guest without mentally carrying twelve unresolved tasks. You can follow an interesting idea because the important work is already under control.

It’s the small things that add up. Not finishing a task means it gets added to an agenda and discussed at the weekly meeting. The owner feels the need to explain why it’s not done, team members depending on that task are delayed, questions are asked, a new date is agreed on, and the task management system is updated. Each small delay pours a little sand into the gears of the project and sucks some energy from the meeting. 

This matters enormously in hospitality because some of the best opportunities are perishable. A guest mentions at breakfast that her father used to make wine. Someone on the team remembers that a local winemaker will be in his cellar that afternoon. There is an opportunity to make an introduction.

A child becomes fascinated by what is happening on the farm. A member of the team realizes one of our local farmers is harvesting later that day and might enjoy having a young helper for an hour.

None of those moments will appear as a task called "create meaningful memory." They require someone to be paying attention, and attention is much harder to find when the organization is constantly dealing with friction.

The energy and time required to turn these observations into an unscripted moment requires a team member taking action. To take action, they can’t feel overwhelmed working to keep up with the basics.  They need a smoothly operating foundation and a team that has practiced the basics enough to move together almost effortlessly. Like a great sports team, preparation creates room for improvisation. 

The Back of House Makes the Front Feel Easy

Personal hospitality depends on disciplined work behind the scenes. The guest should not experience our operating system. They should experience the result.

They do not need to know that their preferences are recorded, that the team reviewed their arrival before they got there, that someone reconfirmed dinner, that housekeeping knows when their room is available, that maintenance issues are being tracked, or that every important promise has an owner.

They should simply feel that things work. The car is there when it is supposed to be. Their room is ready. The team knows that one person does not drink. Someone remembers how they take their coffee, but still asks rather than assuming. The restaurant is expecting them. The activity starts where and when everyone thought it would. If something breaks, it gets handled without the guest managing the repair.

The more seamless that foundation becomes, the more freedom the team has to be flexible when the moment calls for something different.

The discipline behind the scenes is what makes spontaneity possible in front of the guest.

Write It Down

One of our strongest operating beliefs is simple: write things down. Verbal communication feels fast in the moment, but it often fails later. A conversation happens. Everyone leaves feeling aligned. Two weeks later, each person remembers a slightly different version. Someone new joins the issue and has no context. The same subject gets discussed again. Eventually a decision changes, but the old plan is still sitting in a spreadsheet or playbook, quietly waiting to cause a problem.

Writing creates a durable version of reality. For anything meaningful, we create a document, a task, a spreadsheet, a note, or some other record that can be found again and built upon.

For a meeting, that may be a simple agenda beforehand and decisions, owners, and next steps afterward. For a guest, it might mean recording information we have learned about them that will matter later.

For an operational issue, it means documenting the problem well enough that someone who was not in the original conversation can understand it and move it forward.

For a playbook, it means updating the actual standard when we change our mind rather than assuming everyone remembers the conversation.

We don’t document for documentation's sake. The value of a good decision fades quickly if the organization cannot reliably retrieve it. In hospitality, this becomes even more important because so much information passes through casual conversations.

A guest mentions an allergy at breakfast. Someone asks for a later housekeeping time. A parent says their child is terrified of dogs. A couple mentions that tomorrow is their anniversary. Someone says they loved a particular wine. If that information matters, it cannot live only in one employee's memory. Memory is not an operating system.

One Source of Truth

Writing things down helps only if people know where to find what was written. Small teams can create surprising amounts of information sprawl. There is email, messaging, task management, shared documents, spreadsheets, the property management system, notes on someone's phone, and whatever somebody remembers from a conversation in the kitchen.

The problem is not that any of these tools are bad. The problem is when nobody knows which one contains the current truth. One source of truth does not necessarily mean one software application for the entire company. It means one authoritative home for each type of important information.

Guest information belongs in the guest record.

A maintenance issue belongs in the system where maintenance work is managed.

A finalized operating standard belongs in the playbook.

A project task belongs in the project system.

The booking belongs in the property management system.

Once you decide where something belongs, the team has to be disciplined about putting it there.

Otherwise the organization starts paying a search tax.

"Did we ever decide this?"

"Who was handling that?"

"Where is the latest version?"

"Did someone already tell the guest?"

"What ever happened to that thing?"

Every one of those questions is a little piece of friction.

Clear Ownership

Assigning someone a task and giving someone ownership are not the same thing. A task says, "Please do this." Ownership says, "You are responsible for the outcome."

That distinction matters. If you own an outcome, you are expected to understand the details, follow up, anticipate where things may get stuck, bring in other people when needed, keep the relevant information current, and make sure the issue actually gets to a conclusion.

If someone else is doing part of the work, ownership does not disappear. Trust them, but verify. For a small team, this is especially important because there are fewer layers of management to catch dropped handoffs.

Ambiguous ownership creates a strange form of collective anxiety. Everyone is somewhat aware of an issue, but no one is certain who is driving it. People check in on one another. Meetings include repeated status questions. Someone eventually jumps in because it feels risky to keep waiting.

Clear ownership removes all of that. It also gives people more autonomy.

If I know you own the outcome and we have agreed on what success looks like, I do not need to manage every step. I should not need to assign every subtask. You can determine the work required and pull in the resources you need.

A High Say/Do Ratio

Trust is built in surprisingly small increments. One of the most important is doing what you said you would do. This is maintaining a high say/do ratio.

If you say you will send something today, send it today. If the timeline changes, say so before someone has to ask. If you tell a guest that maintenance is coming, make sure maintenance comes and follow up afterward.

Every missed commitment creates more work than the original task.

Someone has to notice that it did not happen. They have to decide whether to wait. They have to follow up. The task gets rescheduled. Another task may depend on it. Options narrow. Sometimes the work becomes more expensive because it is now urgent.

There is also a human cost. Every time someone has to chase a commitment, confidence drops a little. This is true inside a company and it is true with guests.

Guests should not have to manage us. They should not have to ask twice for the same thing, check whether a reservation was actually made, or remind us that they requested a crib.

A high say/do ratio creates calm.

People stop carrying contingency plans in their heads because experience tells them that what was promised will happen. This calm is a special type of luxury.

Proactive, Not Reactive

Good operating systems change the timing of work. Reactive organizations spend enormous energy solving problems at the last moment - when the cost is high, the damage is done and time is of essence.

Proactive teams ask: what could cause us problems? This does not mean manufacturing anxiety around every possible risk. It means taking the time to look forward.

If guests are arriving next week, what could make the arrival difficult?

If a dinner is off property, has it actually been reconfirmed?

If someone has an allergy, has the kitchen seen it?

If an activity depends on weather, what is the backup?

If a piece of equipment is essential to the guest experience, what happens when it fails?

If something requires an outside person to sign off, have we built that relationship before the deadline?

Being proactive creates options. Problems are almost always easier to solve when they are small and when there is still time.

The same principle applies to guest experience. If we know a family is arriving after a long overnight flight with young children, the time to think about food, room readiness, luggage, and how much orientation they can tolerate is before the car reaches the gate.

Systems Should Disappear

With systems and processes there is danger. Once people start believing in systems, they can overbuild them. A system can create just as much friction as it removes.

A task management system with twenty required fields will not be updated. A guest profile with endless preference questions starts to feel invasive. A checklist that requires more time to complete than the work itself becomes theater. A meeting process that generates pages of notes nobody reads is not discipline. It is bureaucracy.

The test is asking: does the system make the work easier, clearer, faster, or more reliable? If not, simplify it. We want the minimum structure required to create clarity.

At Borgo Santolina, we use Cortile, a software system designed for small, full-service properties. It gives us a place to manage guest information, tasks, housekeeping, maintenance, operating workflows, and other shared work.

But Cortile is not the point. A property could use another property management system, a CRM, a task management application, or some combination of tools. The technology matters far less than the discipline behind it.

The important information should be recorded where the team can find it.

The status should be visible.

The work should be followed through.

The system handles that so people do not carry it around in their heads.

Don’t Lose Sight of the Priority - the Guest

None of this is hospitality by itself. A perfectly maintained task system has never made a guest's vacation memorable. A checklist is not kindness. A CRM is not a relationship. A well-run meeting is not a guest experience.

These things create capacity. That distinction matters because it is easy for organizations to confuse operational excellence with the purpose it is supposed to serve. The fundamentals are the foundation. They remove avoidable friction. They protect time. They reduce mental load. They help teams trust one another. They make the routine parts of the operation predictable.

Then something important happens. People have room to notice.

They can linger in a conversation for another five minutes. They can think about what a guest actually meant rather than simply recording what they said. They can call the winemaker, find the local musician, change tomorrow's plan, or recognize that the tired family in front of them does not need the beautifully designed orientation we prepared.

The system handles what should be predictable so the people can respond to what is not.

That is why systems create freedom. And the kind of hospitality this book is about, freedom is where the interesting part begins.