July 2006 CONTENTS
Index AltiusPAR: A Mexico-based Hotel Chain Goes Global UX Takes a Holiday Experience File: Kayak.comTo give feedback on the articles published in this newsletter or to make recommendations on writers and topics that you'd like to read about, write newsletter at gotomedia dot com.
AltiusPAR: A Mexico-based hotel chain goes global
By Alissa Fleet
How do you develop a world class hotel reservation system and call center environment that offers a superior user experience for the parent company and is compelling enough to be sold to leading hotel chains in a competitive global market? AltiusPAR, a pioneer in developing software solutions for the hospitality industry, engaged with gotomedia to do just that. Time to market, quality of work, and budget are all factors.



Contextual interviews with
call center representatives
Intuitive design starts with research
gotomedia began by conducting a research program to develop a better understanding of AltiusPAR primary users: call center agents.We started with a legacy system that had been built by multiple teams of independent consultants. While the breadth of functionality was impressive, a number of counter intuitive design barriers prevented users from learning the program quickly. The amount of time per transaction was much higher than the industry standard. For a system that processed more than 8,000 transactions a day, an increase in speed and efficiency would result in measurable cost savings. We choose this as a top priority in our redesign effort.
Our research methodology was to engage in a comprehensive discovery process that included contextual inquiry, video recording agents in Spanish and English on actual calls, to see where the product was working well and to diagnose where exactly the lag times were. This helped us to identify the primary use cases for making new reservations, canceling and making changes to existing reservations, and other complex call center requests. A second goal of the contextual inquiry and observation was to report key problem areas in the user interface at the page level.
During this stage we held back on giving heuristic solutions, instead focusing on uncovering the usability pitfalls, and ensuring the user's voice was heard loud and clear.
Research meets design
Like many legacy systems, although the different modules could "talk to each other" page-based workflows mirrored the underlying database and did not make for an efficient/effective user experience.Through the contextual inquiry and interviews, we determined how we could improve the experience — what was working within the current system, what areas could be improved and modified, and what flows needed to be completely rearchitected. We saw that different groups of users were using the application in very different ways. These differences extended to page flows, and even into the use of specific fields within the pages. This enabled us to begin redesigning the application to more gracefully handle the primary uses of the system.
The project required a cohesive information architecture across five different modules, working within the constraints of the legacy system's logic and programming. The solution we presented was a simplified version of the UI. We created a dynamic pane-based interface that minimized the down time between pane refreshes. Extraneous data was eliminated, so only necessary information was displayed as required.
