03.01.13 1

Kap. 20 –Case: Flexible User Interfaces

How Information Technology Is Conquering the World:

Workplace, Private Life, and Society

Professor Kai A. Olsen, Universitetet i Bergen og Høgskolen i Molde

Kai A. Olsen, 19.04.23 2

Booking, with a human intermediate

CustomerCustomer HumanintermediateHumanintermediate

Booking SystemBooking System

Know-how, experience

Needs, wishes, interests

“inexpensive weekend trip from Pittsburgh to New York”

Search flights 04/12, return 04/14, Pittsburgh-Washington DC; Washington DC Hotels 04/12-14

Kai A. Olsen, 19.04.23 3

On the Web

CustomerCustomer Booking SystemBooking System

The customer herself must convert needs and wishes to formal search terms. No support from a human intermediate, little support from current Web-based booking systems.

Works when dates and places are known (travel to a meeting), but not when user needs are more open (”a vacation in the sun”).

Kai A. Olsen, 19.04.23 4

Getting the picture

CustomerCustomer Booking SystemBooking System

The customer must perform repeated searches to get an overview (prices, availability, etc.), and has to register and organize the results himself.

This is a very time consuming process. User get minimal support from existing systems.

Taking notes

”Is there any cheap flights to Europe”

”What do I have to pay for a hotel room in Manhattan”

Kai A. Olsen, 19.04.23 5

What we need

A system that can replace, to some degree, the human intermediate

A system that can aid the user in transforming needs and wishes into an explicit booking.

A system that embodies the flexibility inherent in the original request

A system that can give the user an overview over prices, availability, destinations, etc,

Kai A. Olsen, 19.04.23 6

Situation today

Most Web based booking systems requires exact search terms, dates, locations, etc.

Some interfaces offer a limited degree of flexibility with regard to dates

Some examples below

Kai A. Olsen, 19.04.23 7

Examples: Traditional

www.usair.com

www.sas.no

Kai A. Olsen, 19.04.23 8

Examples: Date flexibility

www.ba.com www.travelocity.com

Kai A. Olsen, 19.04.23 9

Visualization (prices vs. time)

www.flybilligst.com

Kai A. Olsen, 19.04.23 10

Airport flexibility (for a city)

www.aa.com

Kai A. Olsen, 19.04.23 11

Overview

Må velge avreisested, ankomststed og måned.

Kai A. Olsen, 19.04.23 12

But, users need higher flexibility

To go or not to go Dates Place of departure Places to visit Type of trip (cruise, tour) Hotels Prices What to see, what to do etc.

Kai A. Olsen, 19.04.23 13

Are we satisfied?

Discrepancy between what users need and current interfaces

It seems that evolution stopped when existing systems got a Web interface, after more than 10 years with Web based systems we should expect something better

Even if competition is high, there seem to be limited efforts in trying to move the interfaces closer to the user

With today's technology there should be no difficulty in providing more flexible systems

Kai A. Olsen, 19.04.23 14

Flexible user interfaces

The interface should accept: a list of destinations, both for departure and arrival (leaving

from New York or Baltimore, to London, Paris or Rome) destinations based on activity (diving, skiing, museums…) sets of attributes (large city in Europe) range of dates (weekends this fall) constraints (not Paris, departure Thursday, less than $1000) unformalized data (”suitable for kids”)

These requirements can be satisfied with a form based interface

Profile data (names, address, hotel room requirements, seating preferences, etc.) can be remembered by the system.

Kai A. Olsen, 19.04.23 15

Implementation

Extensive searches based on user dataCollect statistics Categorize (families with children go to

this place, this hotel have a high number of guests returning)

Feedback, user feedback is important (elderly customers are very satisfied with this hotel)

Kai A. Olsen, 19.04.23 16

Optimizing

When Google and other search engines can index the open Web, booking systems should be able to index the much simpler and more formalized booking databases

Ample opportunities for optimizing searches Users will get requests satisfied faster and will

thus spend less time with the booking systems

Kai A. Olsen, 19.04.23 17

Conclusion

Current Web interfaces for booking does not satisfy user needs in open cases

More flexible interfaces are needed The implementation should not be a problem with

today's technology Advantages:

Simplified, faster bookings Better user satisfaction A competitive advantage for those that go ahead and

implement these systems Currently: Implementing prototype interfaces Next step: Pushing the industry ahead

Kai A. Olsen, 19.04.23 18

Bedre nå?

Dette var et foredrag holdt ved en konferanse i Las Vegas i 2005.

Det er gått 9 år siden den gang.Har vi bedre verktøy i dag?