Amari Raaya Maldives: I found what internal teams may miss

The context

Amari Raaya Maldives (now RAAYA by Atmosphere) was a newly opened 5-star resort, a part of ONYX Hospitality Group, with an experienced management team, skilled employees and a strong offer.

Two months after opening, I was brought in for a week-long mystery guest stay to review the complete guest journey and give the GM and HODs an independent view of how the new operation was coming together from the guest’s side.

The resort consisted of 187 villas, seven F&B outlets, in-villa dining, a spa with 10 treatment rooms, diving, watersports and excursions, recreation and entertainment, and photography services. With more than 300 staff across numerous teams, some managed by concessionaires, bringing it all together was no small task.

For the guest, however, it all needs to work as one.

Why bring in an outside perspective?

Experienced employees know hospitality. But they still need to know how this particular property wants hospitality to be delivered.

What should happen when a guest mentions an interest? When should someone follow up? What information needs to reach another colleague? How should staff recommend something useful without simply handing over a price list? What should happen after “I’m sorry”?

Management cannot see every one of these interactions.

A manager’s attention is divided between occupancy and revenue, sales and marketing, staffing, budgets, maintenance, suppliers, owners and the daily operation of the property. Department heads understandably concentrate on their own areas.

The guest doesn’t. They experience one stay.

That is where an outside view can be useful.

What the review showed

There was plenty of good hospitality.

Staff were friendly, responsive and knowledgeable. Restaurant service was excellent. The island host helped organise activities. The diving was very good, with a knowledgeable instructor and strong attention to safety. The spa team delivered a lovely treatment and actively recommended another one.

My review report documented dozens of individual hiccups across the guest journey. But that’s not the point. The useful part for management was seeing which observations pointed to the same bigger issues.

For example:

→ Information shared during booking was not always used later.
→ A guest’s interests could be known without anybody following up.
→ Services and activities were available, but guests were sometimes left to discover them themselves.
→ A request could be passed on without anyone checking whether it had actually been resolved.
→ Good service sometimes depended on the individual employee rather than on a shared way of working.

One example: I had expressed an interest in diving. Later, a member of the dive team told me he had wondered why I had not returned to book it.

He knew I was interested. I wanted to dive. The service existed. But nobody connected the three until I took action and signed up myself.

My value is in looking for patterns, not simply collecting faults.

What might sit underneath an observation?

A guest repeating information may mean the handover between colleagues is not working.

Different answers may mean important knowledge sits with individual employees rather than being shared.

A missed recommendation may mean the employee does not know enough about the offer, does not feel comfortable suggesting it, or simply does not realise that this is expected.

A polite apology with no solution may mean nobody is sure who should take the problem further.

I observe and show you what happened, then connect everything into patterns so we can understand what may need to change.

Sometimes it’s training the staff or coaching the manager.

Sometimes communication, a process or an onboarding handbook.

Sometimes it’s simple routines like setting up a morning meeting structure to get people to work better together.

What guest reviews may never tell you

Reviews are valuable, but they don’t show everything.

A guest is unlikely to write:

Everyone was nice, but I had to ask for most things myself.

I told somebody what I was interested in, but nobody mentioned it again.

I probably would have booked something else if somebody had recommended it.

Nothing was really wrong. It just didn’t feel quite worth the price.

That guest may never complain.

They may even leave a positive review.

But the next time they’re deciding where to spend their hard-earned money, they may shop around for other options.

It’s not just for new hotels

This was still a new resort, so some of the hiccups were understandable. Teams were learning the property, processes were settling in and people were finding the best ways to work together.

But a guest journey review isn’t only useful when you’re new.

An established hotel has different reasons to look: ways of working become habits, teams change, the offer grows, new partners come on board, and things that once made sense may no longer work as well as they could.

You don’t need to wait for complaints, falling ratings or another reason to tell you it’s time to look.

Different hotels. Same principle.

I am not bringing a Maldives-resort playbook to, say, a 15-room Slovenian hotel.

They are very different businesses.

But the fundamentals are the same.

Information can still get lost. Staff can still interpret “great service” differently. Guests can still miss things they would have enjoyed — and paid for. And a good hotel can still have blind spots simply because the people running it are too close to see everything.