Based on a recent Wall Street Journal interview with Marriott’s Chief Information Officer Bruce Hoffmeister, it is obvious that the hospitality sector has made tremendous leaps and bounds when it comes to adopting new innovations.

It seem like only a couple of years ago that major hotel brands were just starting to embrace the concept of mobility, and other innovations aimed at pleasing the guest through the entire stay cycle.

Fast-forward to today and hoteliers like Marriott are an example of how to employ mobility and other innovations – such as providing “unique guest experiences” to interacting with guests at multiple touch points. Leading hotel brands are now officially on the forefront.

So, what’s next?

While many of us don’t have crystal ball in front of us, it would be safe to assume that innovation will continue to transform the guest experience. Whether it’s the true adoption of robot butlers and concierges to ubiquitous keyless entry, the foundation for brand loyalty will lie in evolving technologies.

And even though at some point in the near future, these types of technologies will be commonplace at any property, this normalization of innovation will continue to create a new springboard for the next level of exciting technologies.

Of course, it is difficult to see this next level through a crystal ball. However, we imagine that Marriott will continue to spearhead the latest technologies on their properties, web and mobile apps.

 


Fatal error: Uncaught wfWAFStorageFileException: Unable to verify temporary file contents for atomic writing. in /var/www/wp_corporate_site_test/htdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:52 Stack trace: #0 /var/www/wp_corporate_site_test/htdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(659): wfWAFStorageFile::atomicFilePutContents('/var/www/wp_cor...', '<?php exit('Acc...') #1 [internal function]: wfWAFStorageFile->saveConfig('livewaf') #2 {main} thrown in /var/www/wp_corporate_site_test/htdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 52