Two hotels, same brand, same prototype, same standard operating procedures handed down from the same corporate office. One runs smoothly. The other fights the same standard every week — the front desk workaround becomes the norm, the housekeeping sequence drifts, the standard nobody follows quietly stops being enforced. Ownership sees two properties that should perform the same way, producing two different results from what looks like the same playbook.
The playbook was never actually the same, because the playbook only accounts for part of what makes a property run.
An SOP describes a process. It doesn’t describe the staffing level available to execute that process, the tenure and training of the team doing it, the physical layout the process has to work around, or the market’s labor conditions that determine who’s actually available to hire. Two properties can share an SOP word for word and still be operating under completely different real-world constraints — and when the constraint and the standard don’t match, the standard is what gives.
This is where a lot of operational troubleshooting goes looking in the wrong place. A standard that isn’t being followed gets treated as a training problem or a compliance problem, and the response is more training, more oversight, more documentation. Sometimes that’s exactly what’s needed. Just as often, the standard was written for a staffing model the property doesn’t actually have, and no amount of retraining closes that gap — it just makes the team responsible for a standard the schedule was never built to support.
The properties that consistently execute well tend to treat the SOP as the starting point of a conversation, not the end of one. The standard describes the target. The operational work is figuring out what has to be true locally — staffing, layout, vendor relationships, team experience — for that target to be realistic on a Tuesday morning during a sold-out weekend, not just on the slide deck where the standard was written. That’s a property-by-property exercise, which is exactly why identical brands under identical standards still perform differently.
It’s also why a labor problem and a standards problem so often get diagnosed as the same thing when they’re not. A property that’s short-staffed will drift from its standards regardless of how well those standards are written or how well the team understands them — there simply aren’t enough hands to execute the sequence as designed. Solving that by rewriting the SOP addresses nothing. Solving it by adding training addresses nothing either. The fix is a staffing and scheduling fix, and until that’s diagnosed correctly, every other intervention just adds friction without adding capacity.
The reverse is also true. A fully staffed property that’s still drifting from standard usually has a different root cause — unclear accountability, a supervisor who isn’t reinforcing the standard consistently, or a standard that genuinely doesn’t fit the property’s layout or guest mix and needs to be adapted rather than enforced as written. Treating that as a staffing problem wastes budget solving the wrong issue.
This is the case for looking at operational performance the same way a diagnosis should always start: what’s actually happening here, specifically, before deciding what the fix is. A performance gap between two similar properties is rarely explained by one variable. It’s usually a combination of staffing, training, physical condition, local leadership, and market conditions, each contributing a piece — and the standard itself is almost never the whole explanation, even when it’s the easiest thing to point to.
The properties that close the gap fastest aren’t the ones that rewrite the SOP the most. They’re the ones that figure out, honestly, which of those variables is actually the constraint at that specific property — and fix that, instead of the standard.
JUDESO works directly with operators on standards, staffing structure, and the operational gaps between how a property is supposed to run and how it actually runs. Start a conversation about a property that isn’t performing the way it should.