Change management in hospitality is the work of getting a new way of operating adopted by people who are already busy. It is not a communications exercise, and it is not training alone. It is the sequence: reason, announcement, training, shadow period, review.

Why do most hospitality change programmes stall?

Not because the technology fails. McKinsey’s research on organisational transformations finds that fewer than a third of transformations succeed at both improving performance and sustaining the improvement over time, and that the difference between success and failure sits in how comprehensively leaders address the human side rather than in the change itself.

Hotels carry two extra difficulties on top of that. Shift patterns mean your team is never in one room at one time, so a single announcement reaches perhaps a third of the people it was meant for. And seasonal turnover means the group you trained in April may not be the group working in September.

Brynja Thrastardottir, Sweeply’s Customer Success Manager, puts the underlying problem plainly: “Managing change can be challenging, as it needs people to step out of their comfort zone and adapt to new situations. It’s common for people to resist change because of fear of the unknown. Leaders should always keep this in mind, and approach with empathy, when implementing changes.”

What should you decide before you announce the change?

Answer five questions in writing before anyone hears about it. They take an hour and they prevent most of what goes wrong later.

1. Why does this change need to happen, in one sentence a housekeeper would recognise as true?

2. How does the proposed solution get you there, specifically?

3. Which stakeholders are involved, and who has a veto?

4. How will you implement it, and how long will each stage take?

5. What three results do you want, and how will you measure them?

Then hold a pre-mortem with your heads of department. Ask them to imagine it is three months from now and the rollout has failed, and to say why. You will hear the real objections in that room rather than in a corridor in week four.

Think about second-order effects too. A change to housekeeping scheduling lands on the front desk, on maintenance and on breakfast service. If you have not told those teams, they will experience your improvement as a disruption.

How do you communicate a change so staff support it?

From the top, in person, and framed as something that makes work easier rather than something everyone has to get through. A message from the general manager at a shift briefing carries weight that an email does not.

Brynja again: “It’s essential to communicate the reason for the change and the benefits it’ll bring. Address concerns and involve staff at all levels. Treat your people as part of the plan, and they’ll be more receptive.”

Resistance is information. When someone pushes back, find out why before you try to persuade them. Often the objection is specific and correct: the new process does not handle a case the old one did, and the person raising it is the only one who noticed. Fix that case and you have converted your loudest sceptic into the person who defends the change for you.

Language matters literally as well as tonally. If part of your team does not work in your primary language, an announcement in that language alone is a decision to exclude them from the reason. Sweeply supports 20+ languages with real-time translation of both the interface and what staff write to each other, which is one reason Volkshotel Amsterdam, 196 rooms and 33 nationalities, was able to onboard smoothly while migrating its PMS at the same time. The multilingual support guide covers the mechanics.

What does a rollout timetable look like?

This is the shape we see work most often for a single property. Adjust the durations, keep the order.

Training supervisors first is the step people skip, and it is the one that decides whether week three works. If the only person who can answer a question is the vendor, adoption stops every evening at five o’clock.

The shadow period needs an end date announced in advance. A parallel process with no switch-off date does not fade, it becomes permanent, and you end up running two systems and trusting neither. The 30-day housekeeping integration blueprint sets out the same sequence in operational detail, and the platform overview shows what the daily view looks like once the paper board is gone.

How do you review progress without kidding yourself?

Go back to the three KPIs you wrote in week zero. Have you hit them, and if not, is the target wrong or is the adoption wrong? Those need different responses.

Add qualitative feedback deliberately, because hospitality runs on judgements that do not show up in a dashboard. Talk to the supervisors, talk to the people who were most sceptical in week one, and read guest feedback for the period. Íslandshótel described the result of its rollout as work that felt lighter, which is not a KPI, and is exactly the kind of signal that tells you the change has actually landed.

Then iterate. Most rollouts need one or two process corrections in month two, and making those corrections visibly is how you prove that the feedback you asked for was real.

Where change management advice does not help

Change management cannot make a bad tool good. If your team is resisting because the software genuinely does not fit how the property works, more communication is just a slower way of arriving at the same verdict. Give the objection a fair hearing and be willing to conclude that the answer is no.

It also cannot fix understaffing. If housekeepers are working through breaks, a new system arrives as one more thing to do, and no amount of framing changes that. Sweeply removes coordination work, not workload, and a property that is genuinely short-handed needs a rota decision before it needs a rollout plan.

Seasonal properties need a different model altogether. If 80% of your team changes every spring, a one-off rollout is the wrong shape. Build the training into the recruitment cycle as a standing 90-minute session and accept that you are running onboarding forever rather than a project with an end.

And if leadership is not convinced, do not start. Staff read hesitation accurately, and a change the general manager privately doubts will not survive its first difficult week.

Get a rollout plan and a price without booking a demo

If the change you are planning is a move to Sweeply, we will send you the rollout plan and the price in the same reply. Email your sellable room count, your PMS, the number of properties and the modules you are considering (housekeeping, maintenance, guest connect, AI agents) to hello@getsweeply.com. You will get an exact quote with onboarding at EUR 100 per property itemised separately, plus the week-by-week rollout timetable above adapted to your shift patterns. No demo required.