September 28, 2005

Don Norman's The Design of Everyday Things

Or, as he calls it, DOET. I really enjoyed this reading. Norman articulated many aspects of experience design that I have long thought about.

The thesis of the first chapter could really be said to be, "Keep people in mind when you are designing something." I think part of the reason the principles laid out in DOET appeal to me so much is that a large part of my life philosophy is, simply, "Keep people in mind when you are doing something." I'm a very conscientious person. I develop feelings of discomfort when I realize I am hindering someone's ability to do something. This is pretty prominently pronounced while walking on the sidewalk: I am very aware of my surroundings and don't like to be in someone's way. I naturally gravitate to the side of the sidewalk when I am walking, and when I realize I need to stop and turn around, I will first slow down and then peel off the main foot-traffic flow. When I am having a conversation with someone, I find it difficult to concentrate if we are in a public thoroughfare and in the way, and I'll try to nonverbal influence the person I'm talking with to kind of scoot out of the flow.

So perhaps I'm especially inclined to be concerned about how an object's poor design would hinder someone's ability to operate it.

An example of an object the design of which I spend an inordinate amount of time thinking about is the cell phone. I have had two different models of cell phones myself, and used many others' phones, and I think they are truly ripe for design/experience improvement. For instance, my cell phone still doesn't display the time while I'm on a call. Since I have ditched a wristwatch for my cell phone's time display, I am basically unable to check the time while I'm talking to someone anymore.

On my most recent phone, I had to connect to the web in order to send or receive a text message. This is incredibly irksome, because it takes usually over a minute to connect to the web. And then, once I had connected to the web and navigated to my "messaging center," I was no longer able to access my phone's address book so I had to resort to writing down people's cell phone numbers on a piece of paper and then connecting to the messaging center, re-entering the phone number (the phone's input defaults to text input, too, so I had to change it back to number-only input), and then finally being able to send the text message. As a result, I almost never sent or read text messages. My new phone, thank goodness, has fixed this oversight.

Another, more subtle example, is the paltry "recent calls" list on the phone. It only holds 10 numbers at a time for each of missed calls, recent calls, and outgoing calls. I know that the phone's memory must be much larger than this, so why not have a larger list? This could be an option that is not readily available (having only 10 numbers at a time is usually sufficient for basic "recent calls" needs), but I for one would like to be able to go back to a day two months ago and see who I called, and who called me, if for no other reason than curiosity.

Again, I enjoyed reading what Norman had to say; his words resonate well with me, for I too am always finding "Norman doors" and other poorly-designed objects. I had long read the website of his colleague, Jakob Nielsen (useit.com), but hadn't yet heard any words from Mr. Norman. I'm glad I did.

Posted September 28, 2005 03:31 PM. Categories: Readings , Week 3 | Permalink

Improving Union Square Station v2

This is a continuation of last week's entry on the subject. This is our final version of the text.

For a description of the assignment, see here.

Introduction

Our group chose to observe the actions of individuals at the Union Square Station subway stop in Manhattan. Metro stops in general are chaotic, busy places with a lot of mental stimulus. In the Union Square station, which takes up nearly a full block of space underground, the situation is exacerbated by its immense size. There are overhead signs every few feet pointing the way to various tracks, there are hordes of people going in every possible direction, there are huge steel girders to avoid, there are subway maps on the walls, as well as other signs that sometimes are useful (e.g., posters informing about limited service on certain lines) and sometimes not very useful (e.g., advertisements, announcements of city events). Because of this capacity for mental overload, we must be careful that the improvement that we propose does not further overwhelm the subway riders. Any design must be situated intuitively within the space in order to enhance the riders' experience.

Observation Research

We gathered information through two primary methods: unobtrusive observation and surveys administered in person on the platform. During our observation, we watched people entering the station from above, and we also watched their behaviors once they had entered the station. We paid close attention to any difficulties they had, when and why they stopped, whether they seemed confused by anything, and what interactions they had along the way.

We solicited survey responses from about 25 subway riders as they waited for their trains to arrive. The information we gathered was: occupation; where they were from; how long they have lived in New York City; how often they took the subway; how long they waited for their train (their estimate); what they did while waiting; what they did when riding the train; what their biggest complaint was; their proposal for improving the subway; their suggestion for improving the efficiency of the experience. Anyone on the platform who was willing to take the survey was allowed to participate, and we obtained responses from a large cross-section of the subway-riding population, including an MTA Efficiency Consultant and a New York Police Officer.

Observation Results

We observed that there are two major groups of subway riders: those who ride on a daily or near-daily basis (frequent riders) and those who are new to the station and unfamiliar with the navigation of it (infrequent riders). For frequent riders, speed and efficiency are the priorities: They want to get to their ultimate destination with as few distractions as possible, and they want to avoid waiting (in lines, for trains, etc.). They want to know the answers to questions like the following:

• When is the next train?


• Is this the fastest route to my track?


• Do I need to speed up?


• Will the next train be express or local? If it's the local, is it faster to take it or to wait for the express?

The infrequent riders tend to be more concerned with information: They want to know where they are and how to get where they want to go. We often observed them asking others which train to take to get to a specific location. They want to know the answers to the questions:

• Is this the right track?


• Is this the way to my track?


• Which track should I take?


• Which exit do I take to get to the Tower Records (or Filene's Basement, etc.) aboveground?

There is some overlap in these two groups. Even users familiar with the subway system in general might not be familiar with the specific station they are at (in this case, Union Square Station). The frequent riders are easily identified by their purposeful gait when moving around the station, but many of these frequent riders are momentarily perplexed, along with the infrequent riders, as to which direction to go when they exit their train.

Through the surveys that we distributed, we were able to obtain some information that was not apparent through observation alone. There were several apparent themes in our respondents' complaints about the subway. One major source of complaint was the subway environment, including the general cleanliness, temperature, and noise level on the platforms. The other major theme was uncertainty. Delays and changing schedules were listed frequently as irritants.

Nearly half of the survey respondents indicated that they do essentially nothing while waiting for their train (i.e., common responses were think, sit, stare into space, etc.).

Proposed Improvement

Our group has devised a system of technological enhancements to the subway stop that we believe will improve the experience of frequent and infrequent visitors alike. We believe that one of the questions all subway riders would be well-served to know the answer to is the question, "When is my train coming?"

To this end we propose a train-tracking system that would be put in use in New York City's subways. The system would use radio frequency transmitters located in each train and receivers mounted at each track to monitor when trains enter and exit the station. This would allow for detailed information on train arrival and transit times. The MTA could use an internal database that would hold all the information for the trains. There are also several useful interfaces we propose for disseminating this information.

First, the LED display signs located in all stations that currently only display the time could also display countdown timers to arriving trains. These signs could also be mounted outside the stations as well, to give arrival information to subway riders before they even enter the station. This would allow riders to enjoy time aboveground, perhaps doing something more interesting with their time than simply "staring into space."

The display of train arrival time need not be limited to MTA-mounted signs around the subway station. The information could also be linked to a dynamic website that would allow riders to find train arrival information before leaving their apartments. Similarly, cell phone users could receive the same information via text message queries.

A system that tracks information for all the trains in the subway system could be further leveraged to great effect. The train arrival times for distant subway stations would be known by the system, allowing it to accurately determine transit times between any two points on the entire subway map.

Our final proposal is an information kiosk that would hold all the above information, made freely available to any subway rider in the station. This kiosk would be able to give detailed transit times between any two subway stations, as well as directing infrequent riders to the correct route to take to get to their destination. This would also solve the problem of changing route schedules that was noted on some of our survey responses.

This kiosk would be able to give a printed receipt with subway directions that riders could take with them to refer to on their ride. The kiosk could also be used to give aboveground information to the subway riders, such as weather information or the correct exit to take to get to a specific location aboveground.

This is a schematic of the system:

Summary

This subway train-monitoring system will allow riders (who consistently over-estimate their wait time, as we found on our survey) to maximize their efficiency, and reduce anxiety, in their subway experience. It will allow subway riders to feel empowered to know when they need to begin their journey before they can even see the subway station. It will give riders the ability to accurately predict their travel time around the city.

This system will also allow infrequent riders unfamiliar with the station or the subway in general to find answers to their questions at their own pace.

Other Improvements Not Explored

During our observation research, we found many areas of the subway that could be improved that went outside the scope of our project. Several of the areas that we found are summarized below.

Busy Turnstiles
At busy times of the day, there is a mass exodus at certain exits of the station. These occur right after a train has arrived. If the trains were outfitted with the RFID tags described earlier, the station will know when a train has arrived. If the turnstiles could then be momentarily turned into one-way turnstiles (by keeping the bar from being able to move in a certain direction) and indicated as such using green or red lights, then the subway riders just entering the station would be able to get through the onrush of exiting people. The turnstiles could also be outfitted to pay attention to how many times they have been used in the past 10 seconds or so, and if they are unused for a specified period of time, they could be turned back into two-way turnstiles.

Turnstile Feedback Sounds
We also noticed that occasionally the metrocard needs to be swiped again, and the sound that accompanies the "swipe again" message on the display is the same sound that accompanies a successful swipe, leading to riders occasionally slamming into an immobile turnstile. The solution to this is simple: change the sounds so there is a negative feedback and a positive feedback sound.

Posted September 28, 2005 12:24 AM. Categories: Group Projects , Week 3 | Permalink

September 27, 2005

Analog In/Out, Serial Out, Infrared Remote Control

Description of the lab see here.

This week I learned how to send serial signals out from the PIC to be read and understood by a computer. We used a PC program, Hyperterm, to view the serial data. Connecting reminded me of how I used to get on the internet back around '96: Specify the baud rate, the parity, stop bits, flow control, etc.

I figured out how to use a potentiometer wired in series with a 10K resistor to vary the voltage coming in to the PIC, and the resulting numbers that show up in Hyperterm range from 0 (when there are 0 volts, i.e., the potentiometer is at maximum resistance) to 1024 (because we specified that there would be that many steps between low and high).

In the course of trying to find something interesting to use this analog signal for, I thought about the different kind of input devices that were possible: there are force resistors, light-sensitive resistors, heat-sensitive resistors. We use single LEDs to indicate the presence or absence of a digital signal, so why not use one of the analog sensors mentioned above with an array of LEDs to indicate strength of the analog signal coming in? I decided to be fancy and try to create a crude remote control using an infrared sensor and infrared emitting LED.

I went down to Chinatown and found an electronics store where I bought an IR Photodiode, part number NTE3033, and an IR LED, part number NTE3017. I had a lot of headaches with these, mostly because I didn't have a clue how they should be properly powered and installed on the breadboard. I finally got a decent reading from the IR receiver when I wired it like a switch, from power to receiver to 10K-Ohm resistor to ground. But I never got the IR LED to work well. I wired it in series with a potentiometer so that I could vary the voltage on it (I wasn't sure if it uses the same amount of voltage as a normal LED), and I was only able to get big readings off my photodiode when I had the resistance on the pot turned down so low as to almost fry the board.

I had also been told that a digital camera will pick up IR, so that you can see an IR LED shining if you look through the camera's viewfinder. I could see no such thing on my poor IR LED.

Long story short, I plopped down a few more bucks at Radioshack for another IR-emitting LED, and all my problems were solved. On with the lab.

The first idea was, if I am going to make an infrared detecting system, I might as well just go ahead and make a full-blown remote control. I used a 9V battery and wired it together with a 5-volt regulator, a 220-Ohm resistor, the IR LED, and a push-button momentary switch. Here's the battery, wrapped in tape (to prevent its metal outside from creating shorts):

A close-up of the guts of the remote, before wrapping them all up in tape.

The final remote:

When the remote is clicked, you can see the infrared LED glow in the viewfiender of a digital camera:

Here is the original setup. The IR detector is the black blob on the right.

Here's how the board looked after I put the LED bar display in, trimmed all the wires, and bent the IR detector backwards so it would detect a signal coming from above.

This is the Radioshack IR Kit (emitter and detector) that saved me:

And, finally, a movie of the sucker in action, set to the Beastie Boys' "Remote Control" (turn your bass up):

And don't forget the code.

Posted September 27, 2005 12:52 PM. Categories: Labs , Week 3 | Permalink