Operational Memory Turns Experience into Continuity

One morning, we received an urgent call because an essential piece of equipment had stopped working. The fault was not particularly complex and the spare part existed, but no one could find the exact reference, the usual supplier or the terms negotiated for out-of-hours call-outs. The person who had spent years resolving this type of issue was on leave, and all the information seemed to have gone with her. After several calls, two contradictory diagnoses and a few tense hours, we restored service. The financial cost was uncomfortable; the operational lesson was far more valuable.

The position was covered. We had competent professionals, general procedures and the willingness to solve the problem. However, the hotel’s actual capability had declined because a decisive part of the work had never formally belonged to the organisation. It lived in a personal contact list, accumulated conversations, the memory of previous breakdowns and the judgement that distinguishes a routine incident from one capable of blocking rooms. We believed we had a process; in reality, we depended on a person who sustained that process without us recognising it.

Since then, I have viewed departures, absences, promotions and internal moves differently. A vacancy has a visible cost made up of recruitment, hiring, training and ramp-up time. The loss of knowledge creates a less obvious bill, spread across mistakes, delays, urgent purchases, additional supervision, conservative decisions, lost commercial opportunities and guests having to repeat information. I call this accumulation operational knowledge debt. It is incurred whenever we allow a critical capability to depend exclusively on individual memory.

This debt does not make experienced people a problem. On the contrary, it reveals how much value they have created. The mistake is to confuse trust in a professional with structural dependence on that professional. A hotel needs specialists, judgement and accumulated experience, but it must also be able to retain what it has learned, share important relationships and sustain its decisions when someone takes time off, changes responsibilities or decides to continue their career elsewhere. True knowledge retention does not seek to retain the person against their will; it seeks to ensure that their contribution remains within the collective capability.

In this article, I propose treating hotel knowledge management as a discipline of continuity, risk and profitability. My intention is to help you identify where your hotel’s memory is concentrated, assess what would happen if it became unavailable and build a transfer system useful enough for daily operations. We do not need to fill filing cabinets that no one will open. We need the right knowledge to reach the right person before an absence turns it into an incident.

Operational memory is a hotel capability

Organizational charts describe who occupies each position, but they rarely show where the knowledge that enables the hotel to operate actually resides. Two properties with similar structures can have completely different levels of fragility. In one, several people know the critical procedures, decisions are explained, and external relationships belong to the hotel. In another, operations rely on small monopolies of knowledge that only become visible when someone fails to answer the phone.

I have seen this concentration in almost every department. In Reservations, it may reside in the person who recognizes a potentially problematic request before confirming it. At Reception, in the person who knows which rooms should not be assigned together even though the inventory says they are equivalent. In Housekeeping, in the person who understands the real workload of each area, the time required for certain room types, and the early signs of a defect. In Maintenance, in the person who remembers the history of each installation. In Food & Beverage, in the person who knows how to anticipate the pressure created by a particular combination of groups, events, and in-house guests.

It also appears away from the front line. It may reside in the person who interprets a contractual clause, reconstructs a complex invoice, knows the particularities of a corporate account, understands the logic behind a hotel revenue management decision, or maintains a trusted relationship with an intermediary. If that person disappears from the equation, the work may continue, but it will do so more slowly, with greater risk and less negotiating power.

It is useful to distinguish at least four forms of knowledge because each requires a different transfer method:

• Procedural knowledge explains which steps must be followed, in what order, with which controls, and who must be involved. It is the easiest part to document, although an excessively generic procedure may look impeccable in an audit and be completely useless at eleven o'clock at night.
• Contextual knowledge makes it possible to understand why a rule exists, in which situations it works, and when it is advisable to stop before applying it. It includes background, constraints, priorities, and consequences that rarely appear on a task list.
• Relational knowledge brings together contacts, commitments, expectations, and ways of working built with suppliers, clients, agencies, authorities, technicians, and local partners. A phone directory does not transfer a relationship; at most, it saves you from having to look up the number.
• Judgement knowledge makes it possible to interpret an ambiguous situation and decide with a reasonable balance between service, safety, cost, and reputation. It is the most valuable layer and the most difficult to capture because it is usually expressed through comparisons, weak signals, and previous experiences.

A significant part of tacit knowledge in hotels appears in the form of exceptions. We know what to do when everything follows the expected path, but experience becomes decisive when a reservation does not fit, a room has an intermittent defect, a supplier fails to deliver, a guest needs a solution that has not been anticipated, or two legitimate priorities come into conflict. The procedure describes the road; tacit knowledge remembers where ice tends to form.

That is why documenting tasks is not enough. If we ask an experienced person what they do, they will probably give us a reasonable explanation of the process. If we ask them to recall the last five occasions when they had to deviate from that process, we will begin to uncover the truly critical knowledge. Exceptions reveal the limits of manuals, the risks the team has learned to recognize, and the decisions that still depend on individual intuition.

This idea connects with an earlier reflection on the need to explain how a hotel really works. Before teaching that operation to a tool, we must ensure that the organization itself can articulate it. If we are unable to explain our priorities, exceptions, and criteria to someone joining the team, then we do not have governed operational memory either.

The first practical step I recommend is to build a Knowledge Dependency Map. I would not begin with every position or every process. I would select those activities capable of affecting safety, service continuity, inventory sellability, the hotel guest experience, revenue, compliance, or an important commercial relationship. The initial objective is to identify where an absence could produce a disproportionate deterioration.

To prevent the map from depending on impressions, I use five dimensions scored from one to five. They are not intended to produce an exact science, but rather to force us to have a more rigorous conversation:

• Impact of absence measures what would happen if the knowledge were unavailable for several days. A high score corresponds to tasks that could block service, inventory, revenue, safety, or critical decisions.
• Exclusivity assesses how many people can perform the activity with genuine autonomy. It does not count who has watched it being done once, but who could take it on tomorrow without continually depending on instructions.
• Difficulty of transfer estimates how much effort is required to teach the capability. Repetitive tasks can usually be transferred quickly; those combining relationships, negotiation, diagnosis, and judgement require progressive exposure.
• Time to autonomy estimates how long it would take a competent person to act safely and consistently. This indicator is particularly useful for designing hotel onboarding and anticipating future capability.
• Difficulty of recovery reflects whether the information could be reconstructed through contracts, historical records, emails, suppliers, and observation, or whether it would virtually disappear with the person.

The total score helps prioritize, but it is worth retaining the detail. Two activities may both score twenty points for very different reasons. One may be technically difficult, even though several people understand the context. Another may be simple to perform but depend on a single external contact and conditions that have never been formalized. The response should not be identical because the dependency originates in different places.

I also recommend adding an estimate of financial exposure. This can be constructed by adding the likely cost of disruption, reconstruction hours, extraordinary supervision, urgent purchases, compensation, unsellable inventory, and commercial margin at risk. There is no need to pretend to have precision that does not exist. A reasoned range is usually sufficient to compare priorities and demonstrate that knowledge transfer is not a decorative Human Resources activity.

Imagine that only one person knows the procedure for releasing certain rooms after a technical incident. Their absence may unnecessarily prolong room blocks and reduce available inventory. On a high-demand date, the loss will not depend solely on their salary or the cost of replacing them, but also on unrealized room rates, possible defensive upgrades, pressure on Reception, and rejected sales opportunities. Concentrated knowledge can influence hotel profitability without appearing under that name on the profit and loss statement.

Something similar happens in hotel marketing and Sales. When a corporate relationship, campaign calendar, negotiation history, or the real reason why a client renews remains in one person's memory, the hotel mistakes a commercial portfolio for a personal portfolio. Contact details allow messages to continue being sent, but they do not explain which promises were made, who influences the decision, which objections should be avoided, or which concessions would erode profitability.

Dependency does not disappear simply because a manual exists. I have found extensive documents describing abandoned processes, old rates, replaced suppliers, and policies that the team had been applying differently for months. A document without an owner, review date, and evidence of use is an ageing photograph of the operation. It can create even more risk than having no documentation because it conveys a sense of security that it no longer deserves.

To test whether knowledge belongs to the hotel, I usually ask a simple question: what would happen if this person could not be contacted for ten days? Ten days are enough to cover several shifts, a weekend, administrative closings, occupancy changes, and unforeseen incidents. If the usual answer is “we would call them,” then we have not yet built continuity. We have created informal availability, and informal availability usually ends up becoming fatigue, dependency, and inconvenient calls during holidays.

This test also protects the experienced person. Excessive dependency is often presented as recognition, but it can become a professional cage. Whoever concentrates the knowledge never switches off, cannot easily change roles, and ends up being consulted about every exception. The hotel loses resilience and the person loses freedom. Sharing knowledge does not reduce their value; it allows them to use it on more important problems than repeating familiar instructions.

I have learned to distrust the phrase “without her, this doesn't work,” even when it is intended as praise. A healthy hotel should be able to say something different: “thanks to what she has built, we now operate better even when she is not here.” That change expresses a more mature form of leadership in the hotel industry, where experience is not protected through monopolies but through teams capable of learning from it.

Transferring knowledge without building a dead library

The usual reaction to a loss of knowledge is to demand more documentation. Folders, templates, and manuals are created and grow enthusiastically for a few weeks. Then a busy season arrives, priorities change, and the initiative ends up buried under files with names such as “Final definitive procedure version 7.” Hospitality has a particular talent for producing definitive documents that need another version before breakfast.

Documentation is necessary, but it must be designed around real decisions and actual use. A housekeeper, receptionist, or technician does not need to find a twenty-page academic explanation while the guest is waiting. They need to identify the signal, understand the risk, know the next step, find the person who can authorize an exception, and know what information to record so that the next shift can continue.

That is why I prefer to work with operational knowledge units. Each unit should answer a specific question, protect a decision, or enable a critical task to be carried out. It may take the form of a card, a short video, a decision tree, a photographic sequence, a criteria table, a history of exceptions, or a supervised conversation. The format should follow the work, not the convenience of whoever manages the repository.

For each critical capability, I would create a Continuity Passport containing the following fields: purpose of the task, impact of an error, current owner, backup person, frequency, essential steps, authorized decisions, known exceptions, necessary relationships, access information, evidence of execution, date of last review, and estimated time to autonomy. This passport does not replace a complete technical procedure, but it provides a manageable view of what must remain operational.

The content should clearly separate three levels. The first describes what is mandatory, particularly in safety, privacy, compliance, and financial control. The second sets out the usual service standard. The third defines the space for judgement, indicating what the team may decide, within what limits, and when it must escalate. Without this distinction, some manuals turn recommendations into laws while others leave sensitive decisions under an ambiguous “use common sense.”

My transfer method is based on eight practices that can be implemented without turning the hotel into a documentation office:

• Conduct the absence test. During a controlled period, the expert stops intervening in a specific task and the backup attempts to perform it using the available resources. The questions, mistakes, and calls that arise reveal exactly which knowledge is missing. It is a more honest audit than asking whether everything is documented.
• Capture cases, not just instructions. After an important exception, it is useful to record the situation, the options considered, the decision taken, and the outcome. A short collection of real cases teaches judgement better than an endless list of abstract rules.
• Apply observation and teach-back. First, the backup person observes the task being performed. Then they perform it with support and, finally, explain to the expert why they made each decision. This reverse explanation makes it possible to identify superficial understanding before it turns into autonomous errors.
• Share critical relationships. Important suppliers, commercial accounts, and partners should know more than one person at the hotel. Joint meetings and corporate channels reduce dependency without damaging trust built over years.
• Record the reasoning behind decisions. Knowing what was decided helps; knowing why it was decided makes it possible to adapt when circumstances change. A short history of decision criteria prevents the team from copying old solutions onto new problems.
• Turn onboarding into a route towards autonomy. Instead of measuring only training hours, I would define observable milestones such as performing a task, resolving an exception, explaining a criterion, and training another person. Onboarding ends when safe autonomy exists, not when a calendar has been completed.
• Assign an owner and an expiry date. Every knowledge unit needs someone responsible for reviewing it. Processes change, contacts are replaced, and exceptions accumulate. Without review, operational memory eventually describes a hotel that no longer exists.
• Recognize the contribution of those who teach. Transferring knowledge takes time and requires professional generosity. If the organization only rewards the person who personally solves every problem, it will be incentivizing the concentration it later seeks to eliminate.

The last practice deserves particular attention. Some organizations ask their experienced professionals to document everything they know while maintaining exactly the same operational workload. Transfer then becomes an additional task that has to be completed quickly and without recognition. The usual result is a collection of minimal instructions because no one can reconstruct years of experience between two incidents and a meeting.

Time must be protected for teaching. It is also important to explain that sharing knowledge is not preparation for a covert replacement and does not reduce anyone's relevance. If the team interprets the initiative as a threat, they will provide information, but they are unlikely to transfer judgement. Knowledge retention requires trust, reciprocity, and a culture in which developing others is a sign of professional maturity.

This introduces a tension that I consider healthy. The hotel needs to take ownership of its operational knowledge, while each person retains experience, intuition, and human relationships that cannot become corporate property. The solution is not to extract every detail from individual memory, but to agree on which capabilities the organization needs to preserve in order to fulfil its responsibilities without invading the professional identity of those who developed them.

External relationships illustrate this boundary well. The hotel should retain contracts, conditions, contacts, commitments, incidents, and alternatives. It should not demand indiscriminate access to personal accounts or confuse professional trust with ownership of human relationships. Continuity is built by gradually introducing other people, using shared channels, and ensuring that the institutional relationship accompanies the individual relationship.

We must also distinguish between transfer and succession. Succession prepares someone to assume a position; transfer enables a specific capability to survive an absence. We may have a candidate with the potential to take on a future responsibility and still retain a critical dependency in specific tasks. Likewise, someone may be able to back up a process without being prepared or interested in assuming the entire position.

This distinction expands the possibilities. Continuity does not always require duplicating positions or creating expensive structures. Sometimes it is enough to distribute capabilities among several people. One may understand administrative closings, another supplier relationships, and another the incident protocol. The aim is not to manufacture an exact copy of the expert professional, but to prevent a single absence from simultaneously disconnecting all relevant functions.

In areas such as Housekeeping, this distribution can be supported by a common base of criteria, workloads, priorities, and exceptions. The experience of turning Housekeeping's operational knowledge into understandable planning demonstrates that information only creates capability when it can be applied to a daily decision. The tool can help, but the value comes from first defining how the hotel actually works.

The same logic applies to any digital system. A repository can facilitate searches, control versions, preserve evidence, and bring answers closer to the point of work. It cannot decide by itself which knowledge is worth preserving, who is ready to use it, or which contradictions must be resolved. Technology organizes explicit memory; learning between people remains essential for transferring judgement.

This is one of the reasons why I believe that competitive advantage will return to the hotel's own knowledge. Available tools will increasingly resemble one another, but not every property will have built the same operational judgement, the same learning discipline, or the same ability to transform experience into repeatable decisions.

To govern the system, I would measure only a few indicators, always linked to real risks:

• Percentage of critical capabilities with autonomous backup, calculated on the highest-impact tasks rather than on the indiscriminate total of procedures.
• Knowledge concentration index, showing how many critical capabilities depend on a single person and how that figure evolves by department.
• Time to autonomy, measured from the start of the transfer until the first safe execution without direct assistance.
• Number of contacts made to the absent professional, including calls, messages, and informal queries. It is one of the most honest indicators of residual dependency.
• Incidents attributable to lost context, distinguishing them from technical or execution errors. If the team knew the procedure but was unaware of relevant background information, the failure belongs to operational memory.
• Use and currency of knowledge units, checking whether they are consulted, whether they resolve questions, and whether they reflect current practice.
• Recovery time following an absence, understood as the period required to restore a normal level of decision-making, service, and coordination.

I would not use these metrics to single out departments or individuals. A high concentration index may demonstrate that someone has carried essential responsibilities for years without receiving sufficient support. The correct interpretation is not “this person shares too little,” but rather “the organization has allowed a critical capability to remain without backup for too long.”

Responsibility should begin with the highest-impact processes and progress through short cycles. Each month, a few capabilities can be selected, absence tests carried out, materials corrected, and backups validated. Discipline matters more than volume. A hotel that transfers two critical capabilities each month will make more progress than one that announces a major annual project and produces a hundred documents without checking whether anyone can actually use them.

In operational committees, I would introduce a standing question: what have we learned this month that still lives in only one person? It may be a guest reaction, a new supplier condition, a recurring breakdown, a commercial exception, or a more efficient way of organizing work. The question turns recent experience into learning material before the daily pace buries it.

Another useful practice is to review incidents that were resolved successfully. We tend to analyse failures, but a brilliant solution can also conceal dependency. If one person prevented a crisis thanks to a phone call, a piece of background knowledge, or an observation that nobody else knew, we have achieved a good outcome and discovered a risk. Celebrating the resolution should not prevent us from capturing what made it possible.

This approach helps connect hotel strategic planning with everyday reality. Opening a new service, changing a supplier, entering another segment, or raising the rate we are prepared to defend requires new capabilities. If the necessary knowledge remains concentrated, the strategy will have only apparent scalability. The hotel will be able to execute while key people are available, but it will struggle to grow, replicate standards, or absorb turnover.

Knowledge management also changes the quality of meetings. When background information, criteria, and decisions are accessible, the team spends less time reconstructing conversations and more time evaluating alternatives. The organization stops depending on whoever remembers best what happened and begins discussing from a common base. That improvement may appear administrative, although it ultimately influences speed, coordination, and profitability.

To verify that transfer has actually created capability, I would apply four forms of evidence. The backup person must be able to perform the task, explain the risks, resolve a reasonable exception, and teach the process to a third person. If they can only repeat the steps under ideal conditions, they possess information, not operational mastery. The difference becomes apparent very quickly when the guest, the installation, or the supplier decides to improvise on our behalf.

The same standard should be applied to professional content. As I argued when analysing why knowledge only acquires value when it improves a decision, a manual is not useful simply because it is well written. Its return appears when someone acts with greater confidence, avoids a repetition, or reaches autonomy in less time.

Waiting until an exit interview to capture knowledge is usually too late. At that point, there is pressure, fatigue, emotion, and a limited timetable. Transfer should be part of normal work and reinforced before foreseeable changes. Holidays, promotions, and internal rotations can be used as healthy continuity tests rather than as threats that force the person to remain permanently connected.

If I had to start the process tomorrow, I would choose ten critical hotel capabilities and avoid starting with complete positions. I would ask who can perform them, what would happen after ten days of absence, and how long another person would need to reach autonomy. That information will quickly reveal the dependencies that deserve attention. I would then choose the three with the greatest exposure and set a specific date for their first transfer test.

I would also speak with the people who sustain those capabilities before designing templates. I would ask them which mistakes newcomers usually make, which signals they watch for, which exceptions concern them, and what they would need in order to teach more effectively. That conversation usually produces more useful knowledge than requesting a procedure by email. It also recognizes that accumulated experience deserves to be listened to, not merely extracted.

My final advice is not to measure the strength of your hotel by the number of indispensable people it retains. Measure it by its ability to turn those people's contribution into shared learning. Good professionals will remain valuable, perhaps even more so, but they will no longer carry alone an operation that needs their memory in order to breathe.