Can a hotel modernize its technology without turning hospitality into another automated transaction? In this episode of Tech Talks Daily, I speak with Mark Hollyhead, Chief Transformation Officer at Aven Hospitality, about the systems behind thousands of hotels and the operational decisions that affect both employees and guests. Mark brings experience from British Airways, Heathrow Airport, Expedia, and travel management before joining the company carved out from Sabre with support from TPG.
His argument begins with a distinction that many technology programs miss. Guests rarely remember the property management system, API, or data pipeline behind a stay. They remember whether somebody knew their name, solved a problem, explained when the room would be ready, or prevented them from repeating information after a long journey. Technology matters because it can remove the administrative work surrounding those moments. Mark wants frontline employees to have time to be hospitable, especially when a situation requires empathy or judgment. That means looking beyond the promise of convenience and asking whether a system gives staff better information, reduces repeated work, and leaves them free to focus on the person in front of them.
Mark shares an example from a hotel he visits regularly in Dallas. Different employees recognized a few preferences from previous stays, including his connection with Seattle, a request for two bottles of water, and a preference for a corner room. None of those details required the hotel to know everything about him. They gave the employee enough context to make the interaction feel personal.
The example also illustrates the boundary between thoughtful personalization and an experience that feels intrusive. Mark's test is whether the customer would be surprised by what the company knows. If the guest begins wondering how the information was obtained, trust has already weakened. Hotels hold identity, payment, preference, and location data, including the place where somebody is sleeping, so that responsibility deserves careful treatment. For technology investment, Mark begins with friction rather than a product category. He looks for employees rekeying information, building spreadsheets because systems do not communicate, switching among screens, and developing improvised techniques to complete ordinary work. Across one property, five unnecessary minutes may appear minor. Across thousands of employees and repeated tasks, those minutes become expensive.
This approach changes how transformation is measured. Mark says another login, dashboard, or screen usually indicates that software has been added without changing the underlying work. He asks what has disappeared after a release. Fewer clicks, calls, handoffs, and repeated explanations provide clearer evidence than the launch itself.
Hotels also depend on a large network of systems covering reservations, property management, payments, distribution, loyalty, revenue management, customer relationships, and housekeeping. When definitions differ across those systems, employees become the integration layer. Data quality problems then appear at the exact moment a guest expects a simple answer. Mark believes the arrival of agentic commerce will make trusted and consistent information even more important. Travelers who have spent decades filling out search forms may increasingly describe what they need through a conversation. The AI agent will expect accurate room attributes, availability, rates, preferences, and policies from connected sources. Conflicting answers will damage confidence quickly.
The episode also challenges the familiar debate between digital and human service. Mark argues that people do not wake up choosing one or the other. They want an easy experience suited to the circumstances. A traveler arriving after a normal flight may prefer to go directly to the room. A traveler stranded in a snowstorm is unlikely to appreciate a chatbot repeating that it understands their frustration.
His operating principle is to automate predictable work and make it simple. When a situation becomes ambiguous, emotional, or unusual, a person should be able to step in with the context already available. The handoff matters as much as the automation because the employee should not force the guest to repeat the entire story. This has implications for frontline adoption. Mark rejects the assumption that resistance means employees dislike change. People often dislike bad change, especially when a new system makes the job harder and the response is a lengthy training session explaining why it should feel better. Aven involves frontline staff earlier so their knowledge can influence workflows before technology is introduced.
AI can also help prioritize work by showing employees the next action that deserves attention. That does not eliminate human judgment. It can give staff the information and authority required to resolve the most important problem without searching through several systems while an increasingly frustrated guest waits.
The opportunity is a hospitality operation where technology works quietly, reliable information travels with the guest, and employees have greater capacity to create memorable moments. The risk is adding automation to disconnected processes, collecting personal information without a clear purpose, or mistaking another launch for an improved experience.
Where would removing five minutes of friction create the greatest difference for your employees and customers? Listen to the episode and share your thoughts.