Eiffel65

Dan Elg, Matt Huang, Rachael Stedman, Sarah Waskom

team eiffel65• Project Goal• User Needs• What We Made• How It’s Improved• What We Changed• Insights From Our Users• Major Takeaways

redesign the mbta kiosks

kiosk user goal

get from point A…

…to point B

purpose of mbta kiosks

I am at point A and I want to get

to point B

Kiosk

Want Need Translation

Fare you need to get to point B

I want this fare type and amount

Kiosk

Financial Transaction

Fare you need to get to point B

OR

disjoint user groups

what regular

users need

what infrequent users need

financial transaction

want to need translation

user interface tasks

disjoint user groups

what regular

users need

what infrequent users need

user interface tasks

Chris the Commuter

Frankie the Freshman

Ted the Tourist

Sally the Sporadic

Purchasing CharlieTicket

Touch Screen

LinkPass Options Screen

Commuter Rail

OptionsScreen

Main Options Carousel Screen

DirectionsScreen

Fare Summary

Screen

Destination SearchScreen

CharlieCard OptionsScreen

CharlieTicket Options

Screen

Payments Screen

1 2

3 4 5 6 7

Other Amount

8 9

10

11

Tap CharlieCard

before

beforeWhy are the fare amounts taped to the

machine?

What’s a CharlieCard

versus a CharlieTicket?

What stop do I get off at if I want to go to the Quincy

Market?Why do I have

to calculate my own fare?

What We Changed• Visibility• Flattened Hierarchy• Customization• Assume Less Knowledge

flattened hierarchy

before

after

increased visibility

assume less knowledge

customization

paper prototype insights

Initially designed for new users

Modified to accommodate regular users

Disjoint Users = Customization

heuristic evaluation insights

if we had infinite time…

Test on touch interface like iPad

Boat Options Screen

Monthly LinkPass Screen

Implement other screens Monthly Bus

Pass Screen

impact within limits

focus on kiosk

interface

large user base is

disjoint

established

standards hard

to change

questions?