"We make things talk so we can talk to people."

I grew up watching Back to the Future trilogy (especially with those reruns on TV). But every time I saw the scenes where Dr. Brown or Marty operated the time machine’s dashboard, I was always like: “Is that really a good way to enter your time travel information? I mean, this is time traveling we are talking about. Don’t you guys have a quicker, safer, and slicker way to enter the times?” I was a young boy, not even knowing what Human Computer Interaction meant (or any of what the 3 words meant, :D), but the bad design of the dashboard did catch my attention. Granted, plot thickened and the story got more interesting when the characters got into trouble with the wrong time entries. But I just thought the Delorean deserves a better gadget, plus, it’s a good design activity.

Original Design

So the original dashboard looks like these:

back-to-the-future
(image source: link)

TimeMachine_remake
(image source: snapshot from this video)

The driver uses the number keypad to enter the destination time. But when you drive in a fast and small space, it’s not uncommon you enter a wrong number. Also, the relationships between destination time, present time, and time of departure are not visually clear. Plus, the whole dashboard is just taking too much space (but it’s definitely good to cram the space with a bunch of electronics to show what a grass-root scientist Doc is. :D). So, here are the 2 new versions I propose.

My Design

New Design A (Sized version)

TimeMachine_New-A

My idea is based on dragging a slider on a touch screen. Here are some of my design considerations.

  • 3 slider heads are placed on a timeline.
  • Since we are doing time travel, where you are from/to isn’t always past/future, so these heads need to have a new visual representation. According to the movie, the present time was positioned in the middle of the dashboard, which is supposed to mean the most important information. So in my design, using that importance level, I use the big head as the present time, the small head as the time of when you are from, and a middle one as the destination time.
  • The destination time head is tappable and draggable. Dragging that head can modify the destination time.
  • The present time and “from time” are not draggable (obviously that’s something you can’t change). But they are tappable to show detailed info.
  • The destination time head glows with animation to hint the driver that it’s some info s/he can change.
  • The 2 ends of the timeline are tappable. When tapped, the timeline extends (to one of the directions) to show more time available.

New Design B (Colored version)

TimeMachine_New-B

This design is pretty much like New Design A, except the head sizes are the same. They are colored in gray (for “from time”, a less important info), green (for present time, color chosen from the original design in the movie), and red (for “to-time”, color chosen from the original design, which specifies the idea of “this needs more attention”).

Conclusion

The main idea of my new design is incorporating a touchscreen and a slider timeline to allow visual presentation and gestural input. As mentioned, since it’s time travel,  the past isn’t always when you are from and what’s in the future isn’t always when you are going, so I use different sizes or colors to specify when you actually are/from/to on the timeline.

Suggestions? Comments? Really to go 88 miles per hour? 🙂

( the finger image in my design is from: http://openclipart.org/detail/160447/)

Topic: Usability Testing: Analyzing and Reporting Findings

Reading material:

  • UxB: Ch 16 & 17

____________________________________________

These 2 chapters don’t make much sense to me.  A lot of things mentioned are too trivial or irrelevant (at least to me). Basically the ideas are, for evaluation:

Evaluation Analysis (Ch 16)

  • Formative/qualitative data is used to form or identify issues, such as usability inspection, cognitive walk through, think aloud, contextual inquiry…etc.
  • Summative/quantitative data is about the numerical or statistics from the evaluation.
  • After problems are identified, prioritize the order of fixing with the relationship of the problems’ cost and importance.

Evaluation Reporting (Ch 17)
Using a formal and conventional way to report evaluation findings is a good way to convey the ideas “This is indeed a problem”, “Here is my solution to the problem”. Common Industry Format (CIF) is a often used for this kind of reporting. Effective reporting should identify problems specifically and provide corresponding solution/recommendation based the cost-importance, urgency, severity. I don’t quite agree with the book’s idea of “go easy on the doses of bad news. Clients and customers will not want to hear that here is a whole list of problems with the design of their system.” A UX expert’s job is to identify problem as much and as specific as s/he can, being too “polite” won’t do much good for the stakeholder.

Decoding/reporting the data from my UR4 experience
Metrics of usability issues can be analysed and decoded. The metrics include performance, issues and severity, behavior (non-verbal and verbal), self-reported. The statics data (avg. time on task, completion rate, SUS score) can be visually presented into charts or graphs. The qualitative data (e.g. interview answers) can be generalized into certain issues. I think the meat of a usability report lies in the issue/recommendation/severity section that lists the problems that need to be fixed.

Reading material

  • UxB: Ch 14 & 15

__________________________________________

(I actually feel good writing this after we finished our UR 4 research project. The knowledge have been internalized so writing this post is like naturally writing a digest article.)

Conducting usability evaluation can be two-fold. The preparation and the the actual testing.

Preparation

  • Data of interest: Design/ask what kinds of data is going to be collected. For example: define the tasks, time on task, pre/post – SEQ for one task, SUS survey for the whole product, pre/post-session interview questions, record of the users verbal/non-vebral behaviors, voice/video record of their interactions with the product…etc.
  • Roles: Facilitator, observer, supporting actors…etc.
  • Participants: Define how many participants are needed, their demographics; recruiting them and get ahold of their availabilities; Is compensation needed? Is IRB needed? is NDA needed?
  • Preparing facility: Find a suitable test place, preferably one same location (a lab). Prepare the equipment.
  • Pilot testing: Find some people who are from the target demographics to do pilot testing. Modify all the things listed above based on the result of the pilot test(s).

Testing

Conduct the test based on the plan. Give a opening speech. Record the data along the way. Encourage the participant to think aloud. Keep the participant at ease by: reminding that s/he is not being evaluated, the product is; providing some help while not affecting  his/her own ways of the interaction. Wrap up with a post-session survey. Provide the compensation after one participant is finished and express the research team’s thank-you. Continue with the next participant.

Reading material:

______________________________________________________________

Information Architecture

The chapter brief talks about what information architechure is, followed by these main topics:

  • Navigation models (how people decide and find): Satisficing; Information foraging; Mental maps; Rote memorization; Information Cost..c. These navigation models are mostly based on the idea that people consciously or unconsciously budget their mental and time cost which are highly related the websites’ scannability and page traversal time. All these models provide corresponding design implications.
  • Process of developing an architecture: There are top-down and bottom-up way to design a architectures. (The top-down one makes more architectural sense to me.) Architectures can be represented in outlines, flowcharts, tree diagrams, wire-frames, page schematics.  One useful and popular way for architecture development is to have the designer or users do card-sorting.
  • Organization schemes: This is about how the content across pages should be organized. Some schemes are Hierarchy(tree), Line topology, Matrix, Full Mesh, Network, and Hybrid. Hybrid is the most common one because it gives a good overall structure of the site, in the meantime  products in the same subcategory can be cross-linked (a pair of shoes with different colors). Also, a website’s structure is better off with more breadth than depth because it saves more mental & time cost for the users. The meaning of the material, semantics, can also be used as a way of organization categorization, e.g. user type, topical, life event, implementation…etc.
  • Presenting navigation to the user: A browser provides navigational tools/cues (Back, Forward, Homepage buttons; URL). A webpage also provides similar things such as breadcrumbs, progress bard, expanding outlines…etc.

Prototyping

  • Horizontal and vertical prototypes: Horizontal ones focus on developing features. Vertical ones are more about making functionality. There was a confusion/discussion in the class about what’s difference between “feature & functionality”, because they are similar words. I think “feature” is more about “modules” (for a shopping website: user verification module, search module, product recommendation module), while functionality is about the technical implementation and consideration of those modules. A good prototype would be a “T” prototype: most features are rough listed, with one/some particular feature’s functionality well developed.
  • 3 kinds of prototype fidelity (they can be used in different phases or with different costs): Low (sketching), Medium (wireframing), High (close to final product).
  • Prototype interactivity: scripted/click-through, fully programmed, “Wizard of Oz”; physical mock-ups (cardboard or paper) for physical interactivity.

______________________________________

Thoughts

  • At first I didn’t know why these 2 topics are grouped together in one week. But after reading the section about card-sorting, I had a question — “card-sorting is how people come up with system architecture, but that chapter started with navigation models, how does card-sorting relate to navigation  models?” Then there comes UxB’s chapter about prototyping with interactivity, which is essentially a way to test how user feels/thinks about the architecture.
  • But why does UxB spend so many pages talking about paper prototyping with specifics like the sheet dimension and material and etc?

Dogs can drive

A while back I posted a RAA about a CHI paper on video chatting with pets. I also posted my design for the interface of a time machine — which came in the form of a Delorean. And not long after, this news came along. Dogs can drive.

Granted, these dog drive with some assistance from the human trainers, and the driving lesson isn’t really about training the dogs how to operate vehicles perfectly but about raising the awareness of how intelligent they are so they will hopefully be less abandoned by people. Still, watching this video raises a lot of interesting questions. One of them is: would the idea of user centered research apply in this scenario in which the users are not human? I am not entirely joking because often times new products need to be designed or modified for users who can’t express their thoughts or express their likes/dislikes with feedback we don’t normally understand  (e.g. babies). Besides trial and error, is there a better way to tackle this kind of problem?

I came across this post a while ago. It’s a column article from a Taiwanese business magazine’s website written by a Taiwanese UX designer who has won many international awards. It’s written in Chinese, so only people who know the language (e.g. people from Taiwan or China) understand what it’s about. But let me share some of the thoughts and content of the article here.

Basically the article brings up this observation: The technology industry in Taiwan is working hard to integrate good user experience design in their products that in the meanwhile the term UxD is becoming a lingo, a specification, a slogan. There are successful stories, there are failure stories. But if we look around, the industry that’s really doing well with UxD in Taiwan is the chains of convenience stores. For example, when it rains, the staff would bring a table of umbrellas or raincoats outside of the store so customers can have an easier access buying them. When checking out microwavable foods (e.g. a small carton of milk or a lunch box ), the staff would ask the customer  if s/he wants to have it heated, how much s/he wants it heated, so s/he can enjoy that food in the store’s seating area.

As someone from Taiwan and having studied/worked abroad, I have come to realize how “pervasive” the convince stores are in Taiwan (once a news story said some tourists, from another country, got lost in Taipei because there are  multiple convenience stores in one block that they got disoriented). On top of that, I also realized that you can literally do anything in a Taiwanese convenience store. You can use the kiosk to buy shuttle/train/concert tickets or print/fax/scan documents. You can pay all kinds of bills (including some taxes!). The stores are always cool (or warm) and clean. You can buy all kinds of foods and drinks. You can give them your laundry or picture files then a couple days later the laundry comes back cleaned, the photos printed. You can have your online order delivered to the store. You can use the bathroom or the seating area for personal convenience. The staff is trained in a way that they are always polite and professional to answer questions, solve problems, offer information, organize and clean the store.

But most of all, the staff are trained to take initiatives to make better service. That reminds me of what Cooper said about computers should be smart and considerate, so they can work better like a human, or in this case, a Taiwanese convenience store staff member. 🙂

Taiwanese tech brands – ASUS, hTC, Acer…etc, I look forward to more of your work on making products well-integrated with good user experience design.

(Additional link: A US professor’s experiences with Taiwanese convenience stores: The 7-Elevens in Taiwan Are a Necessity – Not a Convenience )

Citation
Korhonen H., Koivisto E., (2006), Proceeding MobileHCI ’06 Proceedings of the 8th conference on Human-computer interaction with mobile devices and services, Pages 9-16, link

Purpose of research
The research aimed to formulate a set of playability heuristics for games running on mobile platforms through a series of expert evaluation iterations.

Method
Initially 10 heuristics were developed based on the literature (e.g. Nielsen’s heuristics) with the team’s own modifications. They were divided into 3 categories to evaluate “playability”: Gameplay, Game Usability, and Mobility. After one round of evaluation with 1 mobile game and 4 evaluators, a new version of 29 heuristics were developed to replace the original 10 because the team realized not all playability problems got defined and identified. The new 29 heuristics were categorized y in the same way with the 1st version. A new round of evaluation was then conducted, with 5 games, each one evaluated by 2 to 4 people.

Main findings
In the 3 categories, Game Usability issues (from viewing the game as a commercial utility software or website) are most identified as they are both the commonest to be violated to and the easiest to identify with.

Mobility issues are the ones least identified. My personal take is there are significant fewer heuristics in the Mobility category (only 3 out of the 29 total heuristics), and, the unique system characteristics/usage/limitation of mobile devices are often well-considered during the mobile game development.

Gameplay issues were the most difficult to spot, mainly because it takes experts (people who have real game development experience, who plays game a lot, or someone who is trained for this kind of evaluation) to interpret the heuristics and identify the issues accordingly. For example, for the heuristics “GP3: The players are rewarded and rewards are meaningful”, it takes someone who has the mindset to tell if/what the rewards of the game are and if they makes sense to the gameplay right off the bat.

Analysis
Playability is the idea of usability coupled with fun, immersions, and engagement. It’s a relatively new terminology. It’s mostly applied in computer games, but I think it can also go well with the design of theme parks, 3D theater, or virtual environments. I picked this paper because I wanted to get a better understanding of what playability is. Also, although this paper is old (written in 2006, which is like 3 generations ago in the world of mobile software/hardware), this paper is somewhat the ancestor of other offspring papers who did mobile game evaluations based on the heuristics this paper developed.

Here are some of my thoughts and questions:

  • I like that the 29 heuristics were not made for any particular genres (e.g. adventure, puzzle, combat). The essence of heuristics is they are like guidelines. They are “specifically general” — they provide ways to identify certain problems but they are not over-limited to particular subsets. However, I do hope they include dmulti-player related heuristics. This is not particular to any genre but I think is an important variable to gameplay, usability, and functionality. (Strangely, the multi-player factor was brought up to re-design their 1st version of heuristics, but in the 2nd version, multi-player consideration didn’t show up as one of the new/modified heuristics.)
  • The Gameplay heuristics (14 out of the total 29) are not only good for evaluation, but useful for game design. Gameplay is the experience of game mechanics and story. To me it’s mainly about the balance of things. Making a good game is not easy because it’s not just a software, it’s not just a movie, it’s an interactive experiences with a lot of things involve. That’s why Gameplay heuristics are important, that’s also why gameplay issues are not easy to identify.
  • I am not sure if making the heuristics into 3 independent categories is the best way. For example, the Mobility heuristics should be somewhat tied to Gameplay ones to provide an expert view that the design of mobile game play has some different considerations.
  • I personally don’t get why they used this kind of chart, i.e. the charts (below is one of them) present total playability issues across all 5 tested game. What makes more sense to me would be a chart of average issues for all 5 tested games, or one chart of each tested game.
  • Over the past one year, I have experienced the mobile app boom by playing tons of games on my Android phone and iOS iPad. A lot of the games are really creative and beautiful, but also a lot of them lack the consideration in playability or interface design, which stops me from keep playing them. That’s the interesting about this business. Interfacing: it works best when they are silent, simple, and intuitive. And you know there is something wrong when the interface is making “noises” that obstruct your flow of play. Here is a screenshot of Outwitter, a turn-based strategy iOS game I have played for half year. I just did a quick evaluation with the 29 heuristics this paper came up with. Turns out, the success of Outwitter can be explained by the fact that it violates very fiew of the 29 heuristics.

 

I came across this website: http://windows95tips.tumblr.com/

On the website, people mess around with the UI components available to Windows 95 by adding funny (also somewhat dark) text or graphics. (That’s like something we had done in the class presentation. :D)

Strangely, it’s not a very nostalgic experience scanning through the images posted on the website. Not as nostalgic as seeing a VHS tape rewinder after having watching DVD for years (if you know what a VHS tape rewinder, you are not young, :); if you don’t know what a DVD is, kudos to Netfelix and Hulu), not as nostalgic as one seeing an Atari after having played Wii or Xbox for a while. I guess that’s because a lot of the look and usage of those components are still available (in some way) in today’s Windows OS.

Here are 2 of my favorites from the website:

Citation
Golbeck, J., Neustaedter, C., (2012), Proceeding CHI EA ’12 CHI ’12 Extended Abstracts on Human Factors in Computing Systems, Pages 211-220. link

Purpose of research
The purpose of this research is to establish a new pet video chat system to investigate the usage and potential of this kind of remote computer interaction among pets and their owners.

Method
The team built a remote interaction console, which has 3 main features: a sound panel with a set of sounds to play from; a virtual laser pointer panel which can be controlled by the owner’s mouse movement; a swimming tadpole panel where an animated tadpole swims by itself without any interaction from the user.

A laptop was place at approximate eye level for each pet (e.g., on the floor, on a stool), in a location where the pet usually frequent. The owner starts a Skype video chat from his/her own laptop, and a connection would be established after the pet’s laptop automatically accepts the call (the auto-accept is a configuration made in the pet’s laptop’s Skype). Then the owner uses screen sharing to display the interaction console on both his/her laptop and the pet’s.

2 modes were tested with 10 dogs. In the 1st mode, the “in-person mode”, both the pet and the owner were in one same room of their home. The owner was asked to conduct tasks with the interaction console by playing the sound from the sound panel, moving around the virtual pointer, or playing the tadpole animation. The dogs’ response and engagement were observed and documented by the researcher. In the 2nd mode, the “remote interaction mode”, everything was pretty much the same except the owner conducted the tasks remotely, i.e., from another house.

Main findings
The research is more like a technical exploration of this field (human/pet computer interaction, which has more literature than I thought). No particular research question(s) was asked so the paper is somewhat just an introduction and test of the system they built. The statistics data shows the dogs, rated by the owner, can pay longest attention and best preference to the sound output from the interaction console. But I don’t know why this finding isn’t included in the abstract or the conclusion.

Analysis

The reasons why I picked this paper were:

  • It’s mentioned in the class that the demo session of this paper made a big hit in this year’s CHI.
  • Feline computer interaction has been brought up as Dr. V’s retirement plan (semi-jokingly or in all seriousness? I don’t know. :)) several times in her class. I was wondering if I could find more related research — turns out there is more publication in human-canine/feline-computer interaction than I thought.

Here are my thoughts and questions about this paper:

  1. The research question isn’t really clear. I am not saying a novel invention can’t be a paper, nor am I saying a novel invention must be a solution or application to a certain field. But the paper is really vague in “what I am using this system for”. Often the development of a system takes most of the research time because the process is building the apparatus to address the research question. The paper somewhat just stopped at building the apparatus.
  2. The literature review lists studies in how people use video chat to connect family members and how systems (iPad game, social network) are invented for pets. But those ideas aren’t connected to this paper in a good depth. Coming back to the last point, maybe the team can design either qualitative or quantitative experiments to explore specifically how the system improves or affects the relationship between the owner and the pet, or the family and the pet, or the owner and the family.
  3. Dogs perceive digital information in different ways compared to us. And I am sure the researchers considered the fact that most dogs have better dynamic vision, are far-sighted and color blind. But it would be good that they mention those considerations with how they designed the console’s specifications and content (yep, content for the canine friends). For example, one thing I would like to know is how they chose the screen size. Did they just place a regular laptop, or there is actually some reference, like a data table, to show what an appropriate monitor size for dog vision would be.
  4. Despite my critique and questions, I am all for this kind of creative research. And Jen Golbeck, as far as I can tell from her literature, is a scholar who has done much really interesting research with good breadth and depth. This kind of research has its important value because not only does it stimulate more interesting research, but it also studies how technology intersects our daily life (even between human and animals). And maybe, in a way, with their intelligence and intimacy with us, computers we use every day (laptops, cell phones…etc) are essentially another species of pet.

This has been circulating for a while but I couldn’t help sharing this. So the story went like this, on a forum someone was posting his problem with the new Iron Man flash drive he bought. Every time he plugged it to his computer, the computer shuts down. Other forum users were posting solutions like “Maybe your flash drive has virus, run an antivirus scan with another computer…”, “Is your flash drive compatible with the system at all?” , “Is it manufactured in a wrong way that it short-circuits the mother board of the computer”. But the problem remained unsolved, so they asked him to post an image of what the problem was like. And it turns out………

image source
http://www.quiterly.com/wp-content/uploads/2012/10/I-just-got-trolled-by-the-Iron-Man-Avengers-USB-flash-drive-600×800.jpg:

Talk about epic fail. 😀 But the thing that doesn’t make sense is not why Iron Man’s hand is pressing the power button. The design itself is bad because it probably only considered this flash drive used only for laptops or other devices in which there is no more stuff over the USB port.

I came across this age reduction FX video the other day. This filter can be applied to many areas as an additional tool: camera, phone, computer. But I think/hope the main novelty of it is the filter can be used in real time so it can apply in scenarios like live TV broadcasting.

I can tell this filter is not technically difficult to implement. But it just interests me that how a few changes/removal of things on a face (wrinkles, mole, skin tone) can affect how one’s perception about age.

And I know, we’ll all need this filter, someday. 🙂

 

Citation
Mazalek, A.,  Chandrasekharan, S., Nitsche, M., Welsh, T., Clifton, P., Quitmeyer, A., Peer, F., Friedrich, K., Athreya, D. (2011). TEI ’11: Proceedings of the fifth international conference on Tangible, embedded, and embodied interaction, Pages 129-136, link

Purpose of the Research
This project established a puppeteering game control system to explore:  1) how accurate players can be in performing certain spatial tasks in a game (made as part of this system) with this tangible/embodied interface,  2) compared to existing commercial game controls, if/how mental rotation abilities improve after playing with this system.

Method
The research  can be mainly divided into 2 parts.

Part I: Establishing the system
This part is consisted of both hardware and software. The hardware is the “puppet” itself, which has the size of  a baby and when used, is worn on the player’s waist/belly area. The puppet is constructed with wooden “bones”, electronic components (particularly sensors in the joints), and a signal transmitting unit that sends the data change of the joints to the software system, which is a 3D game made along with the project. The 3D game is able to receive the movements of the puppet and map them to the game’s avatar. The 3D game provides 2 kinds of gameplay: 1) The player moves his own body and the puppet to walk in the physical space in order to move the avatar in the game so the avatar can touch the teapot. The teapot disappears after it’s touched by the avatar and then reappears in a new location waiting for the avatar to touch it. 2) The 2nd gameplay is similar to 1), except it’s camera (the view-port from which the player sees the game) is constantly moving (slowly) in a unpredictable way which makes the avatar “float” in the space if different orientations. This requires the player to constantly readjust his position of the avatar so he can “beat” the camera to touch the current teapot.

Part II: Results for 2 experiments
30 users were divided into 3 groups, each group was tested with this same sequence: [pre-test] -> [play]  -> [post-test], except in the [play] section, each group was given with different interface: keyboard, joystick, and the puppet. Results are grouped in 2 sections. The 1st one is a direct comparison of [play] accuracy performance across the 3 interfaces. The 2nd section is the comparison, across 3 interfaces, of how the players improve in mental rotation both in accuracy and speed using the result of pre-tests & post tests. (The mental rotation tests are sets of tasks to test the user’s “imagination” on how a object would look like after a series of rotation.)

Main Findings

  • The group with puppet interface performs significantly better in touching the virtual teapot, both in terms of aiming accuracy and response time.
  • The group with puppet interface has much better improvement in mental rotation accuracy.

Analysis
This project is a mind blower. It established a creative interface and did a solid/complete research about it. Wearing a puppet on one’s body may sound like a strange/geeky idea but it’s like the researchers were making a statement, “Check this out, this is strange, this is odd, but this is creative, and this is our exploration on what can be next. Oh, and we made a solid research about it. Take that.”

A few things I think can be improved for this project are:

  • It compared the puppet with keyboard and joystick. I am not sure if Wiimote and Xbox Kinect, both motion capturing game controls, were already commercially available during the research. But it would be a even more interesting research if the puppet is compared with those two motion controls. But of course that would be a more complex project with more hypotheses, system development, and experiment design.
  • Common coding (ideo-motor) theory was mentioned in the introduction and discussion sessions of the paper. But it’s not really used a lot to elaborate on the research. (But perhaps the rich experiment and analysis in mental rotation tasks were already their way of incorporating ideo-motor theory.)
  • This is mentioned in the Future Work section: if vibrortactile feedback incorporated, this project will have more interesting data to discuss about, e.g. how the player controls the avatar differently, moreover, how the player accustoms himself to the avatar which is able to perform movements not normally considered or possible for the player, and how that can be applied for the medical domain.

Overall, this is a very good research paper with a creative idea followed by complete system design and concrete research methods. It pulled in many fields together (HCI, computer graphics, game, psychology/cognitive science) which eventually funneled into specific and positive findings.

I was presenting this 2012 SIGGRAPH paper I read the other day in another class. It’s about  human’s and computer’s recognition (and some feature extraction) on sketches. The video above is about an interactive sketch recognition app (available in Windows, iOS, OSX), which is one of the outcome from the research project. The paper, video, image results, apps..etc of this project are available here.

The main novelties of this research:

  • It’s the first ever sketch exploration using large scale data: It utilizes crowd-sourcing  with the use of Amazon Mechanical Turk to get a very big bunch of human sketches and the human recognition results on those sketches.
  • It develops a computerized analysis (an app) based on the data mentioned above. So, the context is not just limited to a small special domain (musical notation, chemical structure), rather, it’s able to analyse and recognized everyday objects (teapots, puppies, table, chair….etc).

Sketching is like jazz or blues, it welcomes variation and improvisization, but in the meantime it sticks with certain core elements that everyone can understand its meanings. That is why sketching is a popular and useful tool for product prototyping. The design team can understand the general idea of a sketch, but it doesn’t restrict  possibilities, questions, challenges, and enhancements.

For the designer himself, the physical actions of sketching is a good way to help him formulate his ideas. Every stroke he made helps him to construct a better idea of what he plans to design. This other paper, incorporated with fMRI and physiological experiments, studies some aspects of sketching on why/how a few simple strokes can create the same stimuli as a corresponding detailed object (e.g. a landscape photo) can.

I think essentially sketching is just like a language, a language that doesn’t require a lot of knowledge or literacy, while in the meantime provides a lot of meaning and opportunities, for the designer and the designed.

 

 

 

 

Last week we had a in-class design activity. We were asked to design a iPhone App which allows students to check their grades (exams/assignments across courses in different semesters) on the go. My group members were Jackie, Carol, and Stewart. We went through procedures documented below. I like this activity because it’s a practice of user-centered design. We started with brainstorming, then we generated personas & scenarios (as if we had gathered data from potential users), then we moved on to prototype with sketching, story-boarding, and wire-framing. All of those were done in less then 3 hours. It’s not a lot of time but it’s great that, with the help of time pressure and group work, we completed these activities and learned from doing. Also, I like how my group came up with the “main page” of the app which shows a big number for current GPA (from a configured set of courses) as if it’s a weather app, which displays the temperature of the current location.

________________________________________________________________________________________________________________

Brainstorming
Each of throw out some ideas and put that idea on the wall. Then we grouped them together with similar functionality, a.k.a. card sorting.

________________________________________________________________________________________________________________

Persona & Scenarios
We built 2 personas: One is Bill, an international undergraduate, whose scholarship is dependent on his grades. Another is Sally, a salesperson who travels a lot, and  is a part-time MBA student who takes courses mainly online. Details about these 2 personas & scenarios can be found on Jackie’s blog post. She was the one typing down our discussion. Thanks, Jackie!

________________________________________________________________________________________________________________

Story-boarding
a.k.a comic strip version of the user’s actions

________________________________________________________________________________________________________________

Wire-framing

________________________________________________________________________________________________________________

Demonstration

Reading material

  • Cooper: Ch7
  • The UX Book: Ch 7, 8, 9

__________________________________________________________________________

Last week we had reading, lecture, and design activity on the topic “Conceptual Design”. A lot of the concepts covered were abstract right after I read them. But it’s good that we had an in-class design activity which concretized and internalized my understanding about the use of tools like persona, scenario, storyboarding, sketching, and wire-framing. The next post documents the in-class design activity I had with my group, so I am not going to recap too much about those terms. However, I want to document some of the thoughts/knowledge I got from the reading and lecture.

Sketch It Rough
I like how in the case study of Magitti, it says sketches are best made deliberately rough to elicit criticism and improvement. Of course prototyping tools (e.g. sketching) should convey some fundamental functionality and visual layout, but it meantime, prototyping is about getting more input from other designers to obtain more meaningful iterations. The good “rough” sketches should not just create questions like “What is X?” but “I can tell what X is but what does Y have to do with X?”. The following video is how Magitti works. (ps: It was made 4 years ago. I think that must had pioneered/inspired many other mobile apps we see today.)

Design Paradigms

A. Engineering Paradigm: making a product work (functionality)
B. Human Information Processing (HIP) Paradigm: making a product easy to use (e.g. ergonomics)
C. Design Thinking Paradigm (Phenomenological view of HCI): making a product pleasant to use (e.g. provide pride, joy, coziness, “presence”)

The relationships for the 3 paradigms can be presented in these 2 diagrams.

Diagram 1 depicts their inclusiveness, i.e. good functionality is part of good usability. I like the 2nd diagram better as it displays their relationships of foundation and evolution.

Phenomenology
What does this term from philosophy have to do with human computer interaction? Turns out it is a good way to interpret those interactions as that can be observed, measured, and situated. It’s about the experience provided by an object (and its affordance) to someone. It’s about roles of users and product and their connections. Phenomenology comes from “phenomena”, how things happen/appear and how they are perceived or experienced by a subject, e.g. with the lens o phenomenology, we don’t really study the electronic circuits or mechanical components of a refrigerator, rather, we study how it’s operated and how those operations interact or affect our daily lives.

Ecology & Presence
The ecology of a product takes more than the product itself into consideration. It’s about designing an overall experience provides by the product, the product’s parent/sibling/child products, and the usage of them in terms of how/where/when. The best way to design with ecology perspective is to apply the notion of “presence”, which is to treat a product not just as something being used, but something being felt, loved, valued, favored, situated, relied, and needed. Doing so will generate a web of emotions, interactions, and connections which will in turn build a system ecology. The best example would be the integration of iOS apps, iTunes/AppStore, and the synchronizability across iOS devices.

In Windows 7, when you plug an external device for the 1st time, the OS will install the corresponding driver and give you this dialogue box saying “Your device is ready to use”. This is what I got after I put my flash drive in a university lab computer.

According to Cooper, that’s an excise, that’s not smart, that’s not considerate, because the user is required to read a message about a task that’s not the user’s job to do (installing & finishing a driver), and is also asked to click a button when it finishes. Of course he would say that, since he thinks this kind of “it’s ready” or “action completed” dialogue boxes are redundant even for more important tasks like file transfer or those related to personal/security data. Not only does he think clicking a button that says “Close” or “Okay” is unnecessary, but also the message box itself is extraneous.

External devices made with USB protocol should stick with and make the best of the idea of “Plug and Play”. I plug, and it plays (runs). The users should not (from Cooper’s point of view) need to provide more interactions to conclude this task, which should be totally performed by the computer.

I agree with that, but in the meantime I think a bit too extreme.
So in this case, probably a better way is it still provides a feedback, but the feedback doesn’t make the user confirmation mandatory. Something like this:

(image source: link)

Window 8 is out these days. Let’s see if they are doing something new about this.

 

 

 

I came across this blog post about how Erik Stolterman thinks after reviewing CHI papers.

http://transground.blogspot.se/2012/10/chi-reviewing-some-reflections.html

I like this post because:

  1. It points out that when you do research, make sense of the theory you introduce, i.e. don’t start with mentioning a theory but in the method or conclusion section the theory disappears or becomes only slightly related. Like what we talked about in class, a theory is a lens we use to see something in the world. Make sure the lens is there so the research has a focus (pun intended :)).
  2. Somehow it suggests that a better research is yo start with something small and you do a complete study about it, rather than start with something big or revolutionary but ending up losing the relevance or concentration. My own extension on that would be: start a research topic that concerns you. It’s okay it’s a small topic, as long as you like/care about the topic, you will go far with it.

 

 

 

Winter is coming so I bought this hot water dispenser the other day. The capacity volume is 4.0L. But the gauge only shows 1.0/2.0/3.0. So where is the missing 1 liter?

Maybe:

  1. It’s for safety purpose. The 1 liter is not showing because when the gauge hit “refill” (which should mean zero), there is actually 1 liter left, so it’s not completely empty when it researches “refill” (which does not mean zero here). Therefore the whole chamber inside won’t be heating without water at all which is a safety issue. This like in driving, when gas meter hits zero, there is actually still some gas left.
  2. The total 4 liter is divided into 3 divisions, each division actually means 1.333 liter.

Okay, the 2nd one is not likely the case here, :D. But either of the two is just not intuitive and causing some excise. Maybe in this case what they can do to improve is to use a intuitive 4 divisions for the 4 liter (so the measurement actually makes numerical sense) while assembling some safety alert mechanism (sound, flashing light) so the user knows it’s time to refill. Is it too much to do for a simple appliance? I don’t think so. After all, “product should be made considerate and smart”, well-said Cooper.

In fact, this hot water dispenser actually has a auto-turnoff when water is running low or circuit is burning too hot. So, I really don’t know why the gauge is still designed that way….

 

 

————————————————————————————————————————

Citation
Findlater, L., McGrenere, J. (2004). A comparison of static, adaptive, and adaptable menus. Proc. ACM Conference on Human Factors in Computing Systems (CHI 2004), ACM Press, 89-96.

Purpose of the Research
This research, which developed an split menu application and conducted user experiment in a controlled lab, sought to find statistical comparisons on the users’ (N=27) preference and performance (speed & error rate) between static/adaptive/adaptable (customizable) menus.

Main Findings

  • The customization in the system was not difficult, but the users had to be guided (with using static or adaptive menus first) so they could use and even like adaptable menus.
  • Static menus were found to be significantly faster (+20%) than the adaptable ones; and adaptable menus were found to be much faster than adaptive ones under certain conditions.
  • Despite the higher performance with static menus, most users (who are exposed to all 3 kinds of menus) expressed their preference in their after-test questionnaires that they liked adaptable menu more.
  • Interestingly, their perceived performances are against their measure perforce: they thought they did better with adaptable menus but they actually performed better with static ones.

Analysis
I chose this article because I got interested in the idea of “adaptive control” a couple weeks ago in our class presentation. This is an old article but it gave me good systematic introduction and research on this topic. I like how it picked a small (by small I mean it’s “down-to-earth”, not a “save the world” kind of pioneering high concepts which sometimes yields to over-generalized results), interesting, and well-literature-reviewed topic then conducted a very scientific research with the use of pre-experiment (generated conditions & schemes from Word use behavior) along with statistical analysis/adjustment on the experiment data.

Some questions/observation arose to me:

  1. The result showed the subjects like to have the menu customizable even though that didn’t provide better performance for them. This echo with (or sound against to?) the class we had a few days ago on the topic of Conceptual Design which mentioned the 3 steps of product design: functionality->usability->pleasantness. What interesting here is the subjects actually prefer/value the pleasantness of having menus customizable over the functionality/usability (in this case, the performance) of it.
  2. The project could use more contexts, not just finding a certain item within menus, so that more tasks can be performed hence a more psychological/behavior models can be analyzed based the data.
  3. The researchers used only 1 user’s Word behavior to generate a pre-test 3×3 condition & scheme which was used to develop the actual test application. I understand too many may result in a unnecessary divergence, but isn’t 1 a bit too little?

 

A few years ago, when we wanted to convert a Microsoft Office Word document (.doc) to a Acrobat .pdf file, we would use Export from the sub-menu accessed from File. Then as time went by, we had the choice of installing  plug-ins so that the pdf generation is done by choosing to print the document with a virtual printer (which is essentially a converter). Now in newer versions of Microsoft Word, we can just use Save As, which allows us to save the doc to a pdf with a list of file types.

I used the word convert/converter because this is a word of abstraction and it can apply to both the mechanical mode and mental model of this action. But for the actual terms o Export, Print, and Save As, which one is closer to the mental model of the users?

This action is to convert a .doc file to a read-only, uniformly-formatted, and annotation-less new file. Imagine Export as a process performed by a big machine which converts the data to another form of data. In early days, the mechanical model of this is close to what the user have in mind because the user imagine computers as mysterious and intelligent machine. Print is closer to the actual use of printing out a physical paper version of the document so it is read-only and meant to be distributed to other project members, which is a perfect example of mechanical model, but also was close to the mental model of it because people think pdf is meant to be made like a printed, clean document. As pdf becomes more commonly used across platforms and occasions, this conversion is nothing more than making it a new file-type, which is both how the mechanical and mental model works in this case.

I agree with Cooper that the closer the representation model is in-sync with the mental model the better the design. But in this file conversion case, based on my observation, there is nothing wrong with making the functionality echoing with the mechanical models because our mental models just have the abstraction of the idea which can be interpreted and evolved with the mechanical models.

Here are screenshots from Purdue’s 4 websites:

A lot of people may have got accustomed to this high similarity across Purdue websites, but not to me, someone who is new to this university and is studying in the field of user experience. These sites are what we use very often, they have good usability and rich content. But they just look too much alike. If I shrink the sizes of those 4 screenshots, the difference might just be indiscernible.

I understand the importance and benefits of CIS (Corporate Identity System). But to me those sites just look too much alike. No, they don’t create usability issues. Individualizing their own styles (of course, under same CIS) may not be a very cost-effective thing to do. And I won’t call this high similarity a bad design. (For the record, their front-pages do have distinctively different images.) But in the meantime, I want to open the floor to these questions:

1) Will this high similarity between websites under one same organization create some unexpected experience to the users? If so,

2) How and how much of this deja-vu is going to affect the users? Positively consolidate and reinforce user’s impression? Or negatively causing confusion and disorientation?

Well, there are other websites in Purdue that are made in the same CIS but have distinct looks, check them out:

(By the way, a somewhat related interesting post from Temi: RAA2 – Aesthetics and Usability: Is beautiful really usable?)

In filmmaking or video game production, the writer usually has his/her own way of composing a compelling story while maintaining the story in a commonly understood structure — e.g. the Three Act (Exposition, Conflict, Resolution). Here I recap what I learned about Persona, User Cases, User Role, and Scenario in the context of storytelling.

Persona = Character Configuration
In movies or games, the writer usually comes up with many “background configurations” about the protagonist or other characters. Some of those may be presented in the final product, others may not. But all of those configurations help the writer (or other crew member) imagine a good idea about who a characters is, what his/her life goals are, how s/he behaves (over certain topics), s/he feels about performing certain tasks. And that is just like the idea of persona used in HCI design to model a certain group of users.

Scenarios = Scenes & Levels
In movies, stories are divided into scenes. In games, gameplay are divided into levels. In both scenes and levels, the characters perform certain tasks, with certain purposes, to certain characters. That’s just like scenarios for users in which the users are asked to do some interactions (with the product or even other users) in a given situation.

Use Cases = Lines, Actions…etc.
The smallest unit of script writing is a certain line a character says, or an action the character does. (John holds the torch and then walks into the dungeon. He sees Jen and yelled “I thought you already left here an hour ago”!!) A use case is somewhat like that, except it’s a series of actions with a purpose given in a scenario, e.g. a series of clicking/typing actions required to make an online purchase in Amazon from logging-in to placing the order.

User Role = (Over-) Abstraction of Characters
Often characters are over-generalized like formulas, “A man faces an ethical conflict and struggles to solve this conflict while trying to keep himself alive”. A user role, which is not recommended by Cooper, is similar to that, which uses abstraction to define the relationship between users and their problems/interests/behavior. The reason why it’s not recommended by Cooper is it’s unlike persona, which conveys empathy, communicates emotions or needs, and looks at personal goals. The persona equivalent of the example I made would be: “Joe Williams, who is in his early 40’s, has a loving wife and two kindergarten children. He works in a computer manufacturing factory who just promoted Joe as a sales manager. One day he accidentally saw a confidential file which documents all the illegal and toxic waste dumping in the lake that’s in Joe’s community. He, with the risk of losing his job and even his life, decided to disclose this conspiracy against the company”. See, doesn’t it convey much more?

 

Citation
Ivan Poupyrev, Philipp Schoessler, Jonas Loh, Munehiko Sato. (2012) Botanicus Interacticus: Interactive Plants Technology. Proceeding SIGGRAPH ’12 ACM SIGGRAPH 2012 Emerging Technologies, Article No. 4
(full text link)

Purpose of the Research
The project, with several unique features apart from other similar prior work, established an interactive system in which users can physically interact with plants for digital space outputs.

Method
Hardware: different species of plants, capacitive sensing electronics at multiple frequencies (1K to 3M Hz); Software: machine-learning algorithms.

Main findings
The project mainly isn’t about answering to certain research hypotheses, but more about exploring and implementing a new kind of interactive plant system. The system allows and encourages visitors to physically interact (touch, gesture, proximity) with plants based on each plant’s unique constraints and affordancse (cactus and orchid behaves differently in terms of both how input is taken and how output is generated).

Analysis
This is not a new idea, at least not to me. But I am still awed by this project with its technical finesse, especially in augmenting the exploration to different species of plants to various gestures. I also like how the research isn’t trying to propose any immediate practical or industrial usage, rather, they want to leave the project in a field of arts and science, where engaging/interesting/entertaining/educating users are its main goals.

What I’d like to see more is some sort of diagram or better description about the electronics and the algorithms they used. Also, how about smell? Each plant species emits its own aroma, can we implement that as part of the plant’s unique interactive characteristics?

The biggest question I am left thinking is their notion of: “From the point of view of our sensor there would be no difference between real and artificial plants: they would all represent the same plant species: BOTANICUS INTERACTICUS “. The interesting thing is this kind of project starts with organic lives in hopes of encouraging  people to interact more with the physical world, but the researchers here eventually looked for the digital representation of this kind of model. I am not saying if that’s good or bad or if it’s necessarily, but it’s just intriguing to think about the questions like: What is ____? Why do we need them? What do we hope and plan to get from them? — fill the blank of the 1st question with Virtual Pets, Second Life, video games, online dating…….


On Wednesday we had a guerilla-style contextual inquiry interview with the purpose of getting to know what potential applicants, especially those who are female or underrepresented minorities, think about Purdue CGT’s graduate program website. I was an interviewer as well as an interviewee and some questions/observations arose to me. Here are some of them:

1) My group designed a series of abstract and open-ended questions with smooth and flexible transitions. Those were, according to Cooper, early phase interview questions. Turns out they don’t really work well. The reason was we were doing quick interviews, so the open-ended questions didn’t really apply. We should have asked straightforward questions so we could get the data we wanted. Not to say we needed to be directly asking things like “What do you think should be improved for the website”, but at least we should have more questions like “Tell us about your experience finding a certain faculty member from the website and how easy that was for you.”

2) Is it better to be interviewed by 1 or multiple people? I understand that getting bombarded with questions from many people can be uncomfortable for some people. But my personal/professional experience told me getting many questions from different people sometimes is a good way to get real (not that the interviewees may lie, but by “real” I mean answering without less “packaging”) and intuitive answers. However having too many interviewers may cost more time and make the interview less focused. Dr. V gave me her good answer commenting my question: “Having no more than 2 interviewers is better”.

3) My group didn’t spend time for the interviewees to actually use the website. Even though we were doing a quick and simulated version of user interview, but it’s actually important that we observe the user’s interaction with the product and ask corresponding to questions.

4) We didn’t get enough interviewees with the ethnographic background we wanted. But maybe that’s not a bad thing. Maybe, during a design phase of product, it’s not bad to sample some opinions from people who don’t fall into the target consumer demographics. Deok shared some of his good insights on this topic.

Personally the best takeaway I got is, it’s okay to do a user research without many desired users and without a lot time. Be flexible to do something based on the manpower/time/money you have. Having some data is better than having no data. And sometimes some data can be good data.

I am in a program where people use 3D modeling software to make “hard things” (CAD, CAE, CAM) and “soft things” (games, animations). It would be cool to apply this kind of gestural input in lieu of clicking a lot of buttons in series or pressing a lot of keys simultaneously.

Now, I don’t know if similar kind of input devices have been on the market. But hey, it just doesn’t seem too utterly expensive to assemble 2 Kinect camera (along with the 3Gear’s SDK) that a lot or modeler can afford and benefit from.

In order to break the rules, you need to know what the rules are. In order to think outside the boxes, you need how the boxes work.

New interfaces are made to create new experiences or functionality (touchscreen, Wiimote, Xbox’s Kinect), but it’s always good to revisit the things we have been using in our everyday life, in this case, the UI components of computer software.

Last week we had group presentations on these components: pointing & selecting (of mouse), controls (buttons, scroll-bars, sliders), menus (drop-down, toolbars), dialogs, errors & alerts messages. Sometimes as a user, who just want to continue our work without getting our thought flow interrupted, we accustom ourselves to the design of these components. But often times it is the bad design of these components that interrupt our thought flow, let alone the fact they may be difficult to learn in the long run. So it’s actually a good reflection time  to learn and rethink how we should design and/or develop those common UI components. Turns out it’s good to revisit the invention of wheels so we get know how to make good wheels.

I especially like how the presentations abstract the use of those can’t-be-more-common UI components with analogies. For example, the sentence analogy (we can use”adverbs” & “adjectives” to modify the actions applied unto certain objects); the map analogy: a good menu should work like a map, giving the traveler directions and even reminders.

The nice thing about this abstractions is not only do we get to remember how good interfaces should be made, also, we can internalize this “language” of UI (human communicating with machines) and hopefully come up with something better later.

Last week we shared and looked at topics in usability guideline. These publications can all pitch in as part of what the “general phylosophy of usability” should/could entail:

  • Interaction Cycle & User Action Framework (UAF) (Hartson & Pyla)
  • “Don’t make me think!” (Krug’s book with a lot of practical examples)
  • Design Heuristics (Nielsen)
  • Design the product as a considerate & smart human (Cooper et. al)

We presented our study on Alan Cooper’s philosophy on designing software/hardware as someone who you interact with from the service industry. The product should be designed as an assistant, a waiter, a secretary, a butler, a receptionist, e.g., the product should care about you and not revealing its own troubles; the product should be responsible for its duties while taking initiatives to do more; the product should be flexible —  even if that means fudging some facts in certain occasions; the product should work while you are not working, the product should remember who you are and what you like.

A lot of the improvements in HCI design today somewhat exemplify what Cooper proposed. But we are still not there yet. We are still not in a place where we don’t need to think before operating something. Maybe it’s because of the machine (software/hardware)’s capability is not advanced enough that they are able to perform closely as human. Or maybe, it’s more because the machine’s human-like behaviors are not well-valued and well-implemented by the humans who design it.

Cooper’s book was initially published in 1995. Today, his ideas still look novel and daring. It’s not really because his ideas are completely strange or unheard of in this very present day. It’s rather more like every time I read about his ideas and how he phrases his ideas, I would think, “Cooper, you are such an arrogant (the positive type of arrogant) evangelist of your own truly engaging and futuristic thinking”.

Usability Evaluations

According to Hartson & Pyla there are several ways for doing usability evaluation/inspections and each comes with its pros & cons. Some requires only a small group of potential real-world users (RITE, Rapid Iterative Testting and Evaluation; Quasi-Empirical UX Evaluation), some can be conducted with only the developer and UX practitioners (Heuristic Evaluations). Here are some of my questions and remarks:

1) User Experience can’t be inspected but issues in UX design can be inspected. This is like the core idea of UX testing which renders the notion of “as long as it’s an intuitive design it’s a good design.” But what is “intuitive”? Something intuitive to one may not be another one. The context of the product may be intuitive for the Subject Matter Expert but the way it’s made for use may not make sense to the SME at all. (Just like what Cooper mentioned in his Metal Models chapter, things designed by an engineer may be too close to the Implementation Model of the product that it might not be easy to use for other users.) This question is like the ever-lasting question for every design. And that’s why I think it’s important to identify the demographics of “target audience” during the design and evaluation phase.

2) Yet, it’s almost universal to have certain “heuristics” for designing software related product, just like what Nielsen’s Ten Usability Heuristics. Be it from empirical data or just from field experience, most of the heuristics works for different kinds of product. However I believe heuristics evolve over time, i.e. in this information overload age we prefer simple design or plain color scheme, but in 1995 you won’t say DOS (two colors, very simple interface) is easier to use than Windows 95. It will be interesting to do a UX heuristics comparison every one decade.

3) On a personal note, once I did a “think-aloud” UX testing for a friend’s learning game research by playing with his game prototype. It’s really an interesting and useful experience. It’s like what The UX Book said, I was being “schizophrenic” (dual personality) exploring the functionalities while saying out loud about what I get from my previous action and what I am going to do for my next action. In a way I was trained as a UX tester of my own for my personal projects (whether it’s just writing an article with Word or developing a program).

4) The idea of evaluating “emotional impact” caught my attention. Most of the time we want a software or website act just like our body “No news is good news”; “Not feeling something is a good thing”. But conveying positive emotion is like going beyond just being “okay”. This is fun. This is beautiful. It looks elegant. Computer games, contrary to websites or application, it’s more important to be entertaining/horrifying/saddening/engaging than being user-friendly because as Hartson & Pyla mentioned in Chapter 2. It will be good to find balances or trade-off between emotionally-satisfying and user friendly across different kinds of software.

5) The inspection methods are quick and dirty. The pros are they are inexpensive; they are fast to do so they can provide iterative modifications. The con is they will give errors, whether they are “false negatives” or “false positives”. Yes we know the idea number for testers is 3 to 5. But how does this number come up? Good we have Nielson’s figure, from a benefits to costs analysis, to answer my question:

Curve of ratio of benefits to costs as more evaluators are added

(copyright: “How to Conduct a Heuristic Evaluation“, by Jakob Nielsen)

Mental Models

I enjoy reading Cooper’s writing style. He uses many good examples to elaborate on one idea. Anyway, Cooper described Implementation Models are how things work, Mental Models are how we perceive/use things. Represented Model is how something is designed as a “bridge” between these two models. And it’s better the Represented Model is closer to Mental Models. Questions arose to me:

1) As Cooper mentioned, we can use mechanical examples in Repented Models, even it’s different from how a product really mechanically work, to facilitate the Mental Model. But what if the mechanical example doesn’t make sense to a certain demographics or generation of users? Like in many softwares, you look for a floppy disk icon to save the project. But for those who never get to use floppy disks, do they experience difficulties or confusions the first time they see this icon? And how about the idea of “recycle bin” or “virtual CDR drive”? Will they become so obsolete that using them as mechanical “metaphor” actually becomes a minus for providing information-age representation?

2) And, will what is information-age enhanced interactions someday or soon become the mechanical-age design for us? Be it the examples mentioned (Photoshop, calendar, drag-dropping file) or other digitally- designed, I think we are inevitably facing the evolution (as mentioned in point 2 of the last section) and challenges of designing with and for new heuristics over the change of time.

It’s quite some work but it’s also a lot of fun to read through the theories in visual perception/attention, fundamental cognition, and why they are important to designing better user experiences. And I couldn’t help proposing these observations:

1) It’s all about survival.
Not explicit in every article but apparently our brains are hard-wired in a way that we detect/perceive/process/react to information to survive. We have different levels of memory (sensory, short-term, long-term, muscle/mechanical memory) so we have enough buffer space in our cognitive system to process urgent and quick tasks (be it fighting a beast in 2,000 B.C. or rushing for a presentation deadline in 2,000 A.D.) while being able to gradually learn something for the long run. We “information-forage” laptops on Amazon while we develop an optimal mental cost/benefit model, just like a lion ponders if that buffalo is worth crossing the river for. Phenomena described by Gestalt Theory are (I think) a sign of human’s “balanced delusion”: while not losing too much of reality, we see what we want to see so we can quickly and approximately get a grasp of things. So your brain may always has this monologue, “Hey I don’t have OCD and I do know that’s not a perfectly connected circle but I am going to tell you that’s a circle so you can concentrate on the speed limit number in that sign”.

2) It’s all about survival — but of what kind?
Nowadays information is so exploded and ubiquitous in a way the amount and availability of messages we receive in the past 10 years is probably more than what one could experience in his/her whole life even in the age of Renaissance. Our brains have been conditioned/regulated/configured in a new way to process daily information and even respond to life-or-death situations. For example, some fire or earthquake survivors reported that the first thing they wanted to do (or actually did) right after the disaster occurred is to take pictures or update their status on Facebook. Also, multi-tasking becomes more common compared to decades ago. The UX Book mentions we feel “closure” when finishing a task out of many simultaneously processed tasks. But really, why do we squeeze in so many things to do in one time in the first place? Desire to survive helps us concentrate on one job then it rewards us with relief when fishing the job, but the modern version of desire to survive also urges us to do/read/listen to many things at the same time so we won’t feel behind others or out of the loop.

3) So….
Our models for perception, attention, and cognition have changed with the overload of information. When it comes to the daily interactions with people and machine, we are doing more than survival, or more precisely, we are still dealing with survival but new kinds of survival are taken into account. Perhaps just like what The UX Book mentioned about designing good user experience for Virtual Environments, both traditional and new considerations for HCI need to be implemented so our modern-day brains can interact with things with better efficiency and even more pleasure.

Create your own website, free on WordPress.com.Create your own website.
Start free