Operations
What a turnaround actually looks like
Underperforming properties rarely have one big problem. They have thirty small ones.
Author
TEX Management
Measure before changing anything
The first weeks of a turnaround should produce data, not decisions. Where revenue actually comes from, what each department costs, where guests complain, and which of those complaints repeat. Changes made before that picture exists tend to fix the loudest problem rather than the most expensive one.
Fix the sequence, then the standard
Most service failures are sequencing failures — the right thing done by the wrong person at the wrong time. Rewriting the sequence of service for arrival, breakfast and checkout usually removes more complaints than retraining does, because it removes the conditions that produce the failure.
Payroll is a structure problem
Cutting headcount into an unchanged structure produces the same operation, worse. Durable savings come from changing how departments are shaped: multi-skilling across quiet periods, aligning rotas to real arrival and departure curves, and removing supervisory layers that exist to manage a schedule rather than a team.
Hold the gains
The failure mode of turnarounds is regression once the outside team leaves. Whatever changed has to end up in a written standard, a rota, a checklist and a report that someone on site owns. If it only exists in a consultant’s deck, it will be gone within two seasons.
