Deconstructing an Interaction - Peter, Stefan, Syd & Terry
Our project aims to analyze the interaction between a person and the Toronto Transit Commission (TTC) website. http://www.ttc.ca
The site is designed with the administrator/corporate user in mind, with a lack of a "front-end" interface for the common user. The lack of a "trip planner" option is also an issue. The user is given the raw data (a giant, resource-hogging PDF map of the entire TTC system) and is expected to glean their required information with little help at all.
Our group recorded the interactions of 12 people with the TTC site, and were able to deduce the following:
- Users have trouble even locating the map they need for route-finding;
- Once they have found the map, there is so much data that it is difficult to find or understand anything specific right away;
- The PDF file is massive and requires much moving around and a prior knowledge of the city to find any destination, location or transit route;
- The links on the site are confusing, misleading and difficult to find.
Using the example of another major city's mass transit system site (Chicago Transit Authority, www.transitchicago.com) it is painfully easy to find any route. Not only does it give you the location, schedule, and walking distance to the nearest transit stop from your origin, it will give you the cost of travel and walking distance to the exact destination. If the TTC took even just the trip planner as a good example and framework, interactions would improve greatly. Also beneficial would be a consolidation of all pages into one easily-readable and attractive front-end page.
The site is designed with the administrator/corporate user in mind, with a lack of a "front-end" interface for the common user. The lack of a "trip planner" option is also an issue. The user is given the raw data (a giant, resource-hogging PDF map of the entire TTC system) and is expected to glean their required information with little help at all.
Our group recorded the interactions of 12 people with the TTC site, and were able to deduce the following:
- Users have trouble even locating the map they need for route-finding;
- Once they have found the map, there is so much data that it is difficult to find or understand anything specific right away;
- The PDF file is massive and requires much moving around and a prior knowledge of the city to find any destination, location or transit route;
- The links on the site are confusing, misleading and difficult to find.
Using the example of another major city's mass transit system site (Chicago Transit Authority, www.transitchicago.com) it is painfully easy to find any route. Not only does it give you the location, schedule, and walking distance to the nearest transit stop from your origin, it will give you the cost of travel and walking distance to the exact destination. If the TTC took even just the trip planner as a good example and framework, interactions would improve greatly. Also beneficial would be a consolidation of all pages into one easily-readable and attractive front-end page.