How Operating Judgement Survives Growth

Hospitality groups can struggle to reuse operating judgement when the reasoning behind decisions remains in meetings, private messages, and senior memory. Documents preserve the final template or approval, but not the questions, constraints, alternatives, and later evidence that made the decision sensible. Reuse fails when an old answer travels without the conditions that made it reasonable.

Judgement Lives in Questions and Exceptions

The operating problem is a lack of accessible decision context rather than a lack of files. Teams need to understand which risks mattered, how strategic fit was interpreted, what changed the view, and which local conditions limit reuse. The target is better preparation for judgement, not a digital replica of an executive.

The important distinction is between a mandatory standard, a local procedure, and a useful precedent. Treating those records as equivalent turns contextual knowledge into unsafe policy.

Knowledge reuse fails when:

• A final template is stored without the reason behind it.
• One property's practice is treated as universal group policy.
• Local regulation, labour, guest mix, asset condition, or brand context is omitted.
• Meeting decisions are not linked to later outcomes.
• Experienced leaders become the only route to historical context.
• Teams cannot distinguish mandatory standards from optional precedent.
• Poor results are remembered selectively or not at all.

Scale Fails When Answers Travel Without Context

As a hospitality group expands, shared operating judgement should make preparation faster and more consistent without taking adaptation away from local leaders.

Reusable judgement is more than a playbook. It includes the situation, evidence, constraints, options considered, decision, responsible people, result, and later learning. A precedent should help a team ask better questions, not dictate an answer.

The benefit is less dependence on repeated senior explanation and stronger continuity when people move between properties or roles.

ISO 30401^{1ISO, ISO 30401 Knowledge management systems} treats knowledge management as a management system that has to be established, maintained, reviewed, and improved. That supports a living view of operating knowledge rather than a one-off exercise in storing past decisions.

Judgement moves across three scales

The same problem appears at three different scales in a hospitality group.

At the local scale, guest, loyalty, and commercial evidence makes opportunities more comparable without collapsing specialist judgement into a score. Across time, operating precedents help the organisation remember which questions, conditions, and exceptions shaped an earlier decision.

The object changes from guest, to opportunity, to precedent. The requirement does not: evidence has to remain connected to the present decision, its constraints, and the person with authority. Shared operating judgement is therefore not a central answer applied everywhere. It is the ability to move relevant reasoning between scales without losing the differences that make it valid.

Playbooks, Search, Coaching, and Precedent Models

Making operating reasoning available is different from standardising every local decision. The difference determines which decisions and later evidence matter, so approved records need to be audited, cleaned, and reconciled before retired guidance, local exceptions, and current controls can be distinguished reliably.

A playbook is the right tool for stable standards and repeatable procedures. A searchable knowledge base helps when the problem is finding current guidance. Apprenticeship and direct coaching remain stronger when the judgement is tacit, high stakes, or difficult to describe. None of these needs an ontology merely to appear more sophisticated.

The gap appears when teams keep finding prior answers but cannot tell whether they travel. Search may return a successful decision from another property without its seasonality, service model, temporary authority, or later correction. A playbook can make that answer look like policy. Coaching can resolve the ambiguity, but repeated reconstruction keeps senior leaders in the loop for questions the organisation has already encountered.

An indexed ontology layer links decisions to circumstances, authority, outcomes, and applicability. Source IDs, timestamps, permissions, and provenance remain attached, while source records stay authoritative. This can surface a precedent together with the reason it may not transfer, but supersession, local exceptions, and applicability rules need ongoing governance. Automation can then fit existing review and coaching habits, with precedent shown through the local leader's operating question rather than an abstract knowledge catalogue.

The precedent therefore begins with the operating question and the property, market, service model, authority, and constraints around it. Policies and playbooks define what was mandatory; review papers and meeting records preserve the alternatives and decision; later service, commercial, maintenance, staffing, or project evidence shows what happened next. The experienced people involved remain part of the context rather than being reduced to names in a knowledge catalogue.

The model distinguishes mandatory control, current guidance, past precedent, local exception, and retired practice. Each item retains effective dates and source ownership.

Operating precedent can become dangerous when its context is compressed. A staffing response that worked in a resort may not fit an urban select-service hotel; a recovery decision made during opening can be inappropriate in steady operation; and a leader may have acted under temporary authority. Brand transitions, ownership changes, emergency periods, seasonality, local law, and unusual guest mix all affect applicability. Retired controls and decisions outside the user's authority are hard exclusions. Similar but incomplete cases should be framed as prompts for comparison, with differences shown before the earlier action.

The ontology for precedent, authority, applicability, and outcomes needs governance from operations, brand, people, legal, and local leadership. Effective dates and supersession links matter as much as search relevance. Teams should be able to mark a precedent as useful, inapplicable, outdated, or missing critical context, and each correction should go to the relevant owner. Review is also needed when retrieval patterns or interface ranking begin to privilege frequently documented properties over less visible local experience.

The most documented precedent is not necessarily the most relevant one. A local leader needs to see how a comparable decision was reasoned through, what conditions made it work, and where the comparison breaks. Search alone tends to reward volume, so it can make one property's habits look like group wisdom. Connecting precedent to authority, applicability, and later outcomes makes the comparison more honest. Repeated rejection of retrieved cases then shows group leadership where guidance is stale, local variation is legitimate, or important experience is missing from the record.

One Review From Precedent to Local Decision

A property team prepares for a recurring operating review and finds a prior decision that appears to have solved the same issue. The earlier result looks favourable, but it came from a property with different seasonality, a different service model, and temporary decision authority during an opening period. A search result that shows only the action invites imitation. A generic summary adds confidence without restoring the missing conditions.

The connected precedent view begins with the current operating question, then retrieves the earlier questions, constraints, options, decision, and later evidence. It places current controls beside the precedent and highlights the differences in seasonality, service model, and authority. The local leader can accept the reasoning, adapt it, or reject it, and records why. That response becomes new evidence about where the precedent applies rather than a vote for or against an old answer.

This is how judgement becomes reusable without becoming rigid. The organisation saves senior reconstruction time when the comparison is genuinely close, while local leaders retain room to respond to conditions that the earlier decision never faced. The same material can support onboarding around real operating rhythms because it teaches how questions are framed and exceptions are escalated, not merely which answer was chosen.

Local Leaders Keep Authority

Property leaders, executives, and functional specialists retain operating judgement and accountability.

PMS, learning, document-management, project, and performance systems remain authoritative. Property leaders and functional specialists decide policy, local exceptions, service recovery, staffing, rates, capital, and how precedent should influence current work. Source-linked precedent supports that judgement without acquiring policy authority. ISO 22483^{2ISO, ISO 22483 Hotels service requirements} spans staff, service, safety, maintenance, supply management, and guest satisfaction, reinforcing why hospitality operating judgement cannot be reduced to one function's playbook.

Training Is the Operating Model

An appropriate first scope is a recurring review with enough comparable past decisions to test applicability, but with consequences low enough for local leaders to challenge every retrieved precedent before it shapes action. The review needs a clear owner, current controls, and later evidence against which earlier reasoning can be assessed.

The team selects a small set of reviewed decisions, classifies their authority, and adds the context needed to interpret them. Current teams test whether prepared precedents improve review without narrowing local options. Facilitated review helps teams practise accepting, challenging, or rejecting precedent and builds trust without turning it into policy. The pilot produces no automated policy or action.

Training should resemble leadership coaching rather than software instruction. Managers can work through cases where precedent conflicts with a current control, where local conditions differ, and where no close comparison exists. Reasons for rejection or adaptation should refine applicability rules while preserving the local leader's judgement. If shadow use becomes reliable, controlled action can extend to assigning a follow-up from an approved review decision. Retrieval popularity does not carry policy authority.

Evidence That Judgement Is Becoming Reusable

The outcome is less repeated senior explanation without weaker local decisions. The leading indicator is the share of recurring reviews prepared with relevant precedent, current controls, explicit differences, and a named decision owner. A guardrail is the rate at which leaders reject material because it is outdated, misclassified as policy, or missing local context. The idea is falsified if experienced leaders spend as much time correcting retrieved precedent as they previously spent explaining the issue from scratch.

Supporting measures include senior time spent reconstructing prior decisions, precedents corrected or retired after feedback, decisions with explicit local differences and rationale, and repeated avoidable issues where relevant precedent existed. Retrieval volume is not evidence of value. A rarely used precedent that prevents one repeated failure can matter more than a popular but generic document.

When Direct Coaching Is Enough

This approach may be unnecessary for a single stable property with low turnover and direct access to experienced leaders. It is premature where the group cannot distinguish policy from local habit.

The strongest fit is an expanding operator whose judgement is valuable but fragmented across properties, functions, and individual memory.

Sources

1. ISO, ISO 30401 Knowledge management systems
2. ISO, ISO 22483 Hotels service requirements