Heather Rasley @ ITP

I’ve published the first step of the interaction process for my Cardboard Canon: menu on.

A simulation of this interaction can be viewed here.

To come: sliders scrolling through menu, select button action, top view of switch and knob actions.

[more pics here]

C. Improve

Alternative interactive schema for tasks (changes in italics):

1. Press power button > rotate settings dial to no-flash icon (among other options) > press shutter > release
2. Touch screen to activate menu > find date/time by sorting either by alpha, favorites, or tag cloud > select date/time on touchscreen > use touchscreen keyboard to type date/time
3. Move switch on top of camera to self-timer

My proposed redesign consists of four major changes:

• Replace menu screen and buttons with iPhone-style menu
• Replace menu navigation with sorting options: alpha, favorites, and cloud
• Replace display and buttons on top of camera with manual switches and knobs
• Replace power switch with a single button at the top of the camera

The overall goal is to create an intuitive instrument that maintains the satisfyingly tactile aspects of manual cameras while bringing the device fully into the current era with the addition of a touchscreen. An important aspect of this redesign is the replacement of the outmoded file folder metaphor with flexible data sorting.

D. Observe

I took some time out to reconsider what felt like a hastily thrown together proposal before proceeding with my paper prototype. I ditched the idea of a touch screen in favor of vertical and side scrolls that can be operated simultaneously while the user is holding the camera.

Since reconceptualizing the organization of menu items is a project beyond a week-long assignment, I simplified that task with the solution to display subfolders that can be accessed directly from the main menu. They can also be accessed from other subfolders when those entries are open.

The revised schematic for the second task is then:

Press menu to activate menu > select date from sub-menu of date/time via main menu > change digits > select time from submenu > change digits > select format from submenu > change digits

I bent the rules a little and created a 3D mockup to better simulate the user experience (and for my own benefit when conceptualizing, since I’m a visual-kinesthetic learner).

Because users had limited instruction during the initial tests I only told users what the various parts of the camera were on a literal level: “this is a button, this is a knob,” etc… Some coaching was provided during the test, which felt appropriate since I’d ask them to talk it out this time.

E. Conclude

User One: Thomas
Total time: approx. 3 minutes (nearly half of previous)

As we determined in the first test, Thomas’ camera literacy is a bit lower than the other users. Still, he caught on fairly quickly to the layout of the new camera. Interestingly, despite the subfolder options within each submenu, he still chose to go back to the main menu to get to complete each new action. This proves that users get into patterns of use that can be hard to break, even when the new pattern has the potential to lower their time spent setting up the product and more time enjoying it.

User Two: David
Total time: approx. 3 minutes (one minute less than previous)

David was the most diligent about recreating the original camera experience, making sure that he knew what would happen when he scrolled down, etc… This was good, since his test brought up a couple of interesting issues. One: when exactly should users be pressing select? I had only been thinking of it as a function to be used when an action is completed, but maybe it could also be a navigation tool of sorts. Two: What happens when a user scrolls beyond the end of a menu? Does it cycle back through or just stop? I determined during the test that it would cycle back through, but that wasn’t something I’d thought of beforehand.

User Three: Kacie
Total time: approx. 2.5 minutes (1.5 minutes less than previous)

Kacie caught on quickly and was able to complete just about everything. She was in a bit of a rush, so wasn’t as thorough as David when it came to setting the time. She clearly understood what was going on and commented that it was a much simpler interface than the original Canon EOS 10D.

Conclusions

My users adapted very quickly to the new interface. It was especially gratifying to see them use the two scrolls comfortably and simultaneously. This has a lot to do with the fact that ITP students are used to such interfaces. I’d be interested to see if older people, for example, would catch on as quickly. I was also pleased to see that everyone caught on to the self-timer switch. That task went from impossible to complete for all users to the quickest to complete. No one had to give up on anything, and needed limited coaching.

For this assignment I will test and revise my camera, a Canon EOS 10D.

A. Predict: predict how most users interact with the device.

Most people are generally familiar with how a camera operates, so I expect that people will catch on quickly. However, it’s fairly confusing that some functions are accessible through the on-screen menu, while others are only accessible through the less inviting and user-friendly display on the top of the camera. The layout of the camera is even visually confusing and intimidating, since there are similar physical devices (wheels, buttons) in both the back of the camera and the top, and it isn’t immediately clear which correlates to what between these two displays.

The larger issue is the whole concept of menus. We are so often forced into operating within a folder structure that actually isn’t natural to us. That’s just not how memory and mental information access works. Folksonomies and other sorting techniques that are used heavily across the web (like “most popular”) tend to make accessing data easier. They’re equally applicable to menus in physical devices, but are seldom implemented in that context.

Tasks

To get a sense of their general comfort level with cameras, the users’ first task will be straightforward. Then I’ll ask them to change two settings. One is in the on-screen menu, the other is within the menu on top of the camera. Since this last task is difficult, I may mention Drive-ISO.

1. Turn on the camera and take a photo without flash
2. Change the date, time and dd/mm/yyyy format
3. Turn on self-timer function

Interaction schema:

1. Flip bottom switch on > rotate settings dial to no-flash icon (among other options) > press shutter > release
2. Press Menu > rotate large wheel to date/time > rotate large wheel to change each digit > press button in middle of wheel when change is complete > repeat
3. Press Drive-ISO button on top of camera > move small wheel on top of camera until clock symbol appears > press Drive-ISO again

VIDEO DEMO

Analysis

1. The interaction of turning on the camera can be confusing because the power is enabled by a switch (rather than a button) which is inconspicuously positioned at the bottom of the camera. It also looks just like a smaller switch that enables and disables the wheel navigation. Changing the setting and taking the photo should be easy and comfortable.
2. Rotating through the menu is a bit tedious, since the date/time is in the middle. There is a jump function, but it’s not very helpful for something in that position. It is also unclear that the unlabeled button in the middle of the wheel is what the screen refers to as “set” in its vague visual instructions at the bottom of the screen. I expect some annoyance and impatience during this task.
3. Some users may get this very quickly and easily, and others may not. The menu on the main screen is much more linear and verbal than the display on top, which is less organized and relies on symbols to convey information. A user’s interaction with this display may go very smoothly if he or she is a visual learner. If not, or if he or she doesn’t understand that the small wheel changes functions, the user may not be able to complete the task at all.

B. Observe: Conduct usability testing with at least three users. Was your initial analysis of a typical interaction accurate?

User One: David
Total time: approx. 4 minutes

David finished the first two tasks in record time, but was about as confused as I expected when it came to the self-timer. Ultimately, he gave up, saying he’d have to read the manual.

User Two: Thomas
Total time: approx. 5 minutes

Thomas’ interaction with the camera was problematic in all areas. He was confused about how to turn it on and needed a hint to figure out how to access the menu. He was, however, the only person to successfully switch the camera into self-timer mode

User Three: Will
Total time: approx. 7 minutes

Sadly, my footage of Will was lost. I did capture his final reaction, though, which indicates his frustration with the device: thumbs down. He had a level of difficulty similar to Thomas’ in attempting to turn on the camera. He stated that the two identical on/off switches confused him. He was also unable to figure out how to set the self-timer.

User Four: Kacie
Total time: approx. 4 minutes

Kacie also had difficulties in all areas. I gave her a hint about where to set the flash mode and she commented that she still wasn’t able to tell what the symbols meant. She, too, gave up on setting the self-timer.

Conclusions

In general, the users’ interactions with the device were about what I expected. There are so many switches and wheels and so few logical labels that it’s very difficult to perform functions that could and should be easy.