Tuesday, August 11, 2009
Input for VR systems has primarily been concerned with tracking the position and orientation of users. This information is required for immersive stereoscopic display when calculating the correct viewpoint for each eye. 6-degrees of freedom (6-DOF), 3D position and orientation, data are necessary for this calculation. There are three main types of devices that have been produced for 6-DOF tracking; magnetic, sonic, and image based. The following table is a comparison of the cost of these systems. Recently there has been research into using low cost cameras and visual fidutials in a fully enclosed cave for tracking (Reference VF paper). This technique has been shown to be accurate, with moderate latency. Using visual fidutials is currently limited by the requirement to be used in fully enclosed cave environments, and additional processing on the image data from the camera.
Other than tracking devices, VR environments use common computer interaction devices, the keyboard and mouse being the most prevalent. Touch screen devices, gamepads, 3-degree of freedom trackers (Wiimote, PS3 controller), microphone (audio processing). There are additional interfaces including haptics, smell, taste, and even neural interfaces.
HCI of RTSs and console vs pc interfaces(Mouse)
Real time strategy(RTSs) games have historically been confined to PCs. The main reason appears to be that the use of a mouse and keyboard for control are superior to the controls provided by console video game platforms. Notable attempts to bring RTSs to consoles are the Nitendo 64(N64) version of Starcraft and the more recent Halo Wars. Halo Wars has been more successful, as it was designed from the ground up to use a control pad whereas the N64 Starcraft was simply a port of the PC game.
So what is it about a mouse and keyboard that is superior to gamepads for RTSs? I argue that there are two principle ways that separate advantages of the mouse and keyboard. I will break up the discussion of these in to two blogs. First the Mouse:
1. RTSs require very accurate and precise selection of items on screen.
A mouse is better suited for this than a joystick(s) on a gamepad. RTSs require the quick selection/deselection of friendly and enemy units, they also require accurate control of selecting small units within larger groups and accurate placement of commands for selected units. A joystick is limited to, usually, 128(8 bits) of precision on each axis. However modern mice have a much larger range of placement, and greater control over the speed of movement. In the future other interfaces may prove better at this currently then mice touch devices may be very good at this as it allows for direct connection of selection and the display itself.
HCI of RTSs and console vs pc interfaces(Keyboard)
Now for the Keyboard.
2. RTSs require a wide range of commands to be quickly executable. US traditional keyboards have at least 101 keys, in contrast to gamepads that have ~16 buttons max. When using a mouse an keyboard at the same time, as is done for RTSs, only one hand is covering the keyboard while the other is covering the mouse. This means that the whole keyboard cannot be covered at once, only ~30 keys are covered at one time. This can also be added to the 2-3 buttons on the mouse. However the hand covering the keyboard can be moved to cover different portions of the keyboard depending on the situation, so all of the keys can be readily available. Given the number of possible unit commands, magic commands, building commands, selection commands, and camera placement commands the ~16 max buttons of most gamepads are inadequate.
The software available for developing VR applications can be divided into two categories: code development libraries and end-user applications. The development libraries: Cavelibs, vrjuggler, OpenSceneGraph, OpenSG, and vrTools are targeted to application programmers. The End-user applications: Quest3D, Unigine, Alice, Agent Sheets, and Vizard are targeted for application designers.
3D programming environment
Focuses on teaching programming
Create games and computational science applications with music, speech, and visualizations
No VR support
Primarily a development library
Unigine viewer allows modification of scene
development tool for creating real-time 3D applications
When considering the accessibility of software and libraries it's important to understand how it is affected by the licensing. Bruce Perens describes four main categories of software licenses: proprietary, “gift”, “sharing with rules”, and “in-between” licenses[Parens]. Proprietary software is licensed such that it may not be modified or used in another package, doing so would be copyright infringement. The Open-source “gift” licenses like the Apache license[Apache] allow modification and use of the software in any derivative work including proprietary software. Open-source “sharing with rules” licenses allow modification and use of software as long as the derivative work is also shared. The General Public License version 3(GPL3)[GPL3] is an example of an open-source “sharing with rules” license. Open-source “in-between” licenses like the Lesser General Public License version 3(LGPL3)[LGPL] allow modification and use of the software in derivative work, including proprietary software, with the condition that the original software code be made available with the derivative work.
There may be software that provides the functionality needed in a new application, but because of licensing, that software may not be legally usable. This makes the general use of proprietary software and systems inaccessible to many. But under open-source licenses, there is legally solid ground for users to use, modify, and share derivative work
The complexity of utilizing the hardware and software necessary for a VR system still requires specialized knowledge. The development of an application’s software has the most effect on accessibility as compared to hardware. This is because there are many different VR hardware arrangements ranging from very complex to support, 6-sided cave, to relatively simple to support, a single computer with attached HMD. However, developing a VR application with VR software is complex for the range of computer and HMD to 6-sided cave hardware arrangements. To utilize the available software requires software engineering, graphics, and VR domain knowledge. Because of this, most VR projects have an additional cost to pay for personnel that have this specialized knowledge.
Monday, August 10, 2009
To what extent should designers consider accessibility options during the prototype phase? Is this something that designers should be inherently doing and building into their everyday design practices? Are there design patterns to meet these standards?
For example, Section 508 states that “the standards aim to ensure that such information is also available in an accessible format…the use of text labels or descriptors for graphics and certain format elements”
I recently observed a usability review of a table displaying data. There was a page title and description directly over the table. Users generally know where they are from the navigation, so why have these extra titles? They repeated what the navigation (tabs) stated, and added more clutter to the page. The reason? To support accessibility requirements. I feel often designers are given a false choice between “good usability” and supporting accessibility requirements.
What are some ways to work towards a more seamless integration of supporting accessibility standards and following traditional usability practices?
I looked at a few posts and sites about the differences, and to summarize:
- Focuses on larger samples
- Focuses on what people say
- Focuses on what people will buy
- Focuses on smaller samples
- Focuses on what people do
- Focuses on how people will use
So is it important to have both? I’d say yes, since they focus on different areas. UX research often feeds directly into design decisions, where as marketing research feeds into business/strategic decisions.
Is it important to have coordination between the UX and Marketing team? What I found was marketing research could help drive specific areas the UX team can focus on.
Another reason to coordinate internally is to avoid bothering users too much. I realized I had no visibility on customer surveys being conducted by the Marketing team. Since some of our users are contacted by both teams, I’d hate to send a survey out at the same time and bombard the user with questions.
An interesting point about Apple’s approach of not using market research from Jobs: “It’s not about pop culture, and it’s not about fooling people, and it’s not about convincing people that they want something they don’t. We figure out what we want. And I think we’re pretty good at having the right discipline to think through whether a lot of other people are going to want it, too. That’s what we get paid to do.”
This goes completely against UX principles of focusing on user experiences. But Apple is successful. Why do you think that is?
“The usability problem with non-linear content is crucial because it indicates a deeper issue: Kindle's user experience is dominated by the book metaphor. The idea that you'd want to start on a section's first page makes sense for a book because most are based on linear exposition. Unfortunately, this is untrue for many other content collections, including newspapers, magazines, and even some non-fiction books such as travel guides, encyclopedias, and cookbooks.
So, the design decisions that make Kindle good for reading novels (and linear non-fiction) make it a bad device for reading non-linear content. Sure, Amazon designers could fix simple UI stupidities, such as the interaction design for a newspaper ToC. But doing so would simply apply a band-aid. To truly optimize the non-linear user experience, they'd have to completely reconceptualize the Kindle design. “
During the initial stages of product design, I’m curious to know what role the designer plays in understanding and designing for long-term goals. For example, Kindle is obviously focused on the book metaphor and specifically novels for now, but is their larger vision to encompass more forms of media and books in the future? If so, do designers need to understand long-term goals of a product, and consider these when producing the first version? How can designers create designs that are flexible enough to allow for changes in the future without starting from scratch?
Or if the Kindle PM team really didn’t consider anything beyond a novel, should UX have investigated different usage patterns and persona types and considered these during the initial design?
Our agile consultant recently passed these two articles about how UX can use Agile to its advantage:
Both of these articles had really good suggestions. Here are the ones I that stood out to me and could be applied to projects not using agile as well:
“Best practice” suggests that designers should research iteration n+2, design iteration n+1, support iteration n and review iteration n-1. The iteration zero is deservedly becoming an accepted way of buying time, but some teams are extending this idea with an additional mid-project iteration zero, in which no user stories are delivered. Instead, developers can tidy up code and plan next steps, while designers can revisit the vision and check that brand, aesthetics, and experience are coherent across the site so far.
Bill Buxton remarked that a problem with Agile development was iterating without ideating. I'm paraphrasing here, but basically Bill asserted that Agile teams lock onto a solution and iterate to refine it without considering that there may be a better solution out there. He's right, but not just about Agile teams. I see a fair number of designers guilty of the same behavior.
Today it's easier to respond to Bill's call to action with some concrete practices like Adaptive Path's Sketchboarding and Jeff & Jim's Design Studio approach. Desiree Sy described using interns to prototype 10 or more design solutions to a possible design problem.
The smart people at salesforce.com have taken RITE and cranked the dials up to 11. They build html prototypes and iteratively test and repair them using remote usability testing. They'll complete several rounds of this on each chunk of work before it goes into a development time-box.
In an attempt to travel light, I often hear UX people describe their prototypes as their specification. It's common to deliver only the prototype, or ideally the prototype + a discussion with the team building the software. During the discussion annotate the prototype by hand if necessary. No need to produce detailed documentation.
Cultivate a user validation group for use for continuous user validation. Use customer time to do some contextual inquiry style observation and interviewing, then sit down and review a prototype for something that may be built in a future iteration, then to review the working software testing features just built in a previous iteration. The trick here is to leverage that user face time for research and validation. Don't segregate your work.
Sure, a well-designed, intuitive interface can reduce the need for help, but to completely eliminate all help assumes a perfect system and really, a perfect world (don’t think this is going to happen any time soon).
I recently began collaborating with our Documentation team on how to build a better help system in our products. While I’ve found a few articles around document presentation, readability, etc., I wasn’t very successful in finding overall approaches to Help usability. There were a few articles that focused on heuristics, like this one from the STC: http://www.stcsig.org/usability/newsletter/0401-heuristics.html
While heuristic evaluations can help, they don’t approach help by looking at the overall user experience, or help experience.
We decided to try an look at help more holistically. Here’s an example of what we found from a customer interview:
A particularly irate customer printed out the entire documentation (1000+ pages), thumped it down on the table, and then gave me a single error message they had received in the product. They were insistent that I myself try to use our help system, and they wanted to watch. The customer asked me to solve the problem (and remember their production line is down, and every second translates to money lost). I did the following:
1. Read the error message for any clues. It only gave the error type (error), error ID, and a one line message: Contact your system administrator.
2. Searched the documentation (online) for the error code
3. Searched the documentation (online) using various keyword searches
4. Browsed through the topics (online) in the documentation
5. Checked the support website (that lead me into other problems I won’t go into)
None of these approaches produced the reason or solution for the problem. After he shared his own approaches, all of which failed as well. The interface was well-designed, but the help wasn’t.
At first this seems like just a error message problem. If the error message had better explanations, there would be no problem. Yes, this is one area that needs improvement, and there are numerous articles on creating effective error messages for UX designers.
But we took this a step further. Sometimes the reason cannot be given for the error, or the error is produced from customer-side reasons that engineers can’t predict.
We started to evaluate the overall help experience: How is someone using the help? Are they even using the help? What do they assume they can find in the help? When to they turn to help? Etc. We then broke this down into concrete areas we could focus on improving collaboratively with the Documentation team. Here are some examples:
Messages (info, error, warning, etc.)
Search engine capabilities for documentation
How users call help in the system (help links, context-sensitive help, tooltips, etc.)
Grouping of information
What needs to be documented?
Readability of content
I think there is a high potential of improving the overall user experience of systems by working with documentation teams to evaluate and implement help systems. What do you guys think?
“As web designers and information architects, we often dismiss deep consideration of content when we design interactive experiences. By content I’m not only referring to the various forms of text (e.g., headers, body copy, error messages) but also imagery, graphics, and videos or audio that make up the full interactive experience.
Sure, we have a sense of what content is available, and we’ve likely considered it to some extent when creating flows, wireframes, and prototypes. But the design artifacts that we create represent only part of the overall user experience that we’re designing. The content that sits inside of our design framework is often the final arbiter of success, yet we sometimes diminish its importance and separate ourselves from it. The more we separate our design activities from content development, the greater the risk of design failure.”
Recently I was designing a new navigation system and was asked by my UX manager to not use real content, so people could focus on the actual navigation system and not on the content. Also, since this was a navigation system for a set of products, the prototype needed to be generic.
I can see the pros and cons to this request. During the first round of feedback sessions I had fake content in my prototypes. I was able to focus on the actual mechanics of the system quite easily, but I received a lot of questions around if I’d tried to integrate real content to make sure it works. There was a lot of effort for people to imagine how it would really work, and questions about if I considered x, y, z content use cases.
For the second round of feedback I used real content. Having the content helped me find problems early on (can these products’ models work in this structure, spacing issues, size limits, etc.). During feedback sessions, this did help people to understand how the system would actually work, but it also added another level of distraction. The focus would move away from the navigation system and discussions cropped up around the content.
Though more time consuming, I felt having both versions was helpful. Starting with a prototype without real content allowed me to focus on the system itself, and then adding content was like a first test, and gave different, but still useful feedback.
Sunday, August 9, 2009
Some Computer Vision Links:
Human-computer interaction through computer vision
Extending human-computer interaction by using computer vision and colour recognition
Emerging Topics in Computer Vision
Some Tangible User Interfaces Links:
3D Computer Interaction Using Physical Objects: Exploration of Tangible User Interfaces
Tangible User Interface for Children An Overview
A Tangible User Interface as Interaction and Presentation Device to a Social Learning Software
Some Human Robot Interaction Links:
Utilizing Physical Objects and Metaphors for Human Robot Interaction
Human-Robot Interaction for Cooperative Manipulation: Handing Objects to One Another
Some Human Factors and Artificial Intelligence Links:
Activity Theory vs Cognitive Science in the Study of Human-Computer Interaction
Integrating Human Factors and Artificial Intelligence in the Development of Human-Machine Cooperation
- Touchable Holography
- Augmented Reality for Ordinary Toys
- Hyper-realistic Virtual Reality
- 3D Teleconferencing
- Scratchable Input
By the way, a guy that does scratching surfaces will not be invited to my place. I don’t want him to scratch my furniture. ;)
In last July, Nissan Motor Co., Ltd. announced the development of new air conditioning system called, “Forest AC”. This new AC system creates optimum cabin environment by controlling temperature, ventilation, aroma, and humidity. You say, aroma? Yes, I know. Nissan says the new system was based on a research on effects of aroma on human mental activity. You can read the rest as I was curious about what can really do with aroma. There are some systems out there to control automatic temperature of interior of your car and add pollen filters to help you make comfortable while you drive. All these system goes under ubiquitous computing. This new system even goes further by blocking order and removing order using “ion”. Making feel comfortable as you drive is a good idea, but you wonder about the process of designing system like that.
“Nissan develops technology to set new standards in terms of comfort, quality and other factors for every aspect of the automobile, putting human characteristics first, based on the Life on Board concept, which is designed to deliver more joy of driving.”
Where am I going with this? Well, I am wondering if engineers in general think because they can develop system like this, they will develop it. I wondered if they ever consider users and context of driving in general. You can put as many sensors as you can install in a vehicle, but I wonder if they try to understand the context of driving. Making driver “not think” may not apply to this context. Did they just forget about “experience of driving”? Humidity and airflow control maybe good idea, but aroma has some issues. I think “scent” is another sensor drivers use to detect something wrong in a car. Is it good idea to take away users natural senses while driving? I thought drivers should be using all the senses to connect with vehicle and roads to create “driving experience”. I wonder what Dourish would say about relationship between a driver, car, and the road. Did he think these senses ruin your interaction with the world surround us?
After quickly finding this page, I sit with the question, why are these visual search engines not in the mainstream search options? Google, the Godfather of search engines has incorporated visual aids such as the Wonder Wheel and Timeline to assist searchers with visual and semantic information but they have not created anything yet that is similar to the visual search engines on this page.
The chosen tools are advanced than what you would think. As we have discussed various usability tests in the class, these media groups are using similar methods to track how ads are viewed and which ones are effective. Such tools besides eye tracking were heart-rate monitors, skin temperature readings and facial expressions to monitor. They are trying to figure out how small the ads can be but still viewed by users or how they feel about certain ads by looking at their facial expressions.
Again, we are faced with corporate driven $tragegy vs. functionality of information dissemination. This disturbs me greatly as they have to figure out a way to effectively making sure users see ads. As a usability designer, how would you feel about your design being compromised. I understand if it is for entertainment. What annoys me the most is that ads are getting aggressive and no longer a part of the page anymore. In old days, ads had a space in your page. They are in your face and you have to click to stop ads. In usability standpoint, it is not functional part of the sites and not friendly to users. It distracts you from doing what you want to do. If you are an independent designer, you may purposely add spaces for ads. In larger corporate levels, is this how it works? Would designer informed how ads will be displayed so they need to change design to accommodate ads or simply told to design a site but marketing dept. will figure how to put over ads over your design?
What happened to user-centered design? I haven’t across any design books/sites that talks about how to incorporate ads as a part of design. I see Google ads model where you can simply select what type of ads and place a widget on your page. But that’s more for independent designer. I wonder about larger corporations that accept ads. What do you think?
http://hci.stanford.edu/~winograd/acm97.html See section 2.2
The article talks about the emerging area of interaction design. Now I am still trying to wrap my fingers around service design; now interaction design. Simply put, the author describes it as a shift from seeing the machinery to seeing the people using it. This sound a lot like service design; is it the same thing? Or is service design one sector of interaction deisgn? Wikipedia describes service as the non-material equivalent of a good. Interaction is a kind of action that occurs as two or more objects have an effect on one another. I guess from the definition one can have service interaction design. Seeing the people using the service instead of the service itself..make sense? So if I am an engineer designing a vehicle display, I am designing based on the user that will be viewing the display and not the technology. Help me here? What are your thoughts?
"In your usability studies, how do you get the subjects to take the interview, survey, etc as serious as you do? Most people who take surveys fill it out without much thought. One time I created a survey to determine if a particular tool was useful; it seemed as if the participants just went through the motions, especially if the questions only required them to select from a list (i.e. agree..strongly agree). Is there a certain method of questioning or interviewing that is more effective for getting honest answers or well thought out answers?"
The response to my email was to do the following:
1. Build rapport with the people you are interviewing. Make sure they feel like their opinions are valued and put them at ease so they feel they can be completely honest.
2. Wording of questions is critical. Make sure you ask really open ended questions without leading.
I did some browsing around also and what I found in a document that someone posted on the web was helpful in providing more insight as well as confirming the email response. The author of the document posted on the web gave some do's and don'ts of usuability study design. For example, give the participant an options to end the study if they feel uncomfortable. Make sure the user understand that there is no right or wrong answer. Also, have them sign a form explaining that he results are anonymous; this helps them feel that they can be honest in their answers. The author also gave techniques on what to do during the study as far as what to watch for. For example, be sure to note non-verbal communication. Some advice on the types of questions were to give open ended questions as well as task oriented questions.
The author also gave pointers on when to perform usability studies, the best person to conduct the study, etc.
If you read through the article, I know from my personal experience, I agree. I never actually pay much attention to the "happenings" on the side. They also stated that if the user does engage themselves with the ads it is usually one that looks like a windows command. I AGREE. I remember the first time I saw one of those...I CLICKED. That was the last time I was fooled, so nowadays I don't think those are popular anymore.
Now I understand why advertisers are just plain old bombarding web browsers with advertisements. You ever been reading an article then have a McDonalds ad just pop up right in front of your article? Then you have to search for the mistery "close" button. Now I know why! The ads want to be heard or seen in this case. This is another reason why I am beginning to accept that this phenomenon is real.
I found this article to be helpful because it list steps to help guide you in developing your personas. I thought Cooper (Chapter 5 p 77 did a great job with this also. This article gives a different perspective of the step by step process for developing effective personas. One part that I found interesting in the article as opposed to Cooper is the verification step. This is where you find data to support your persona descriptions and scenarios. This made sense because when creating personas, you use the data collected to help get an idea of what your users are like. But is what you came up with correct? Or make sense? Even though article seems to be focus more on development as oppose to the “user”; I think you can pull different techniques and ideas from each process (Cooper and the article).
Saturday, August 8, 2009
I came across this Web 2.0 site called, Smartypig.com. Smartypig.com is a service site which users are able to set own saving amount. It’s a virtual piggy bank. At the same time, you can share your saving goal with others (family members too) so that they can contribute it if they wish. Since this is Web 2.0, it integrates with facebook and other social network sites.
I am little baffled with this service model and user behaviors. I maybe old school, but I don’t get the idea of sharing this kind of personal details. It’s a good behavior that can be recommended, especially in this tough economic time. Everyone wants to save some but I am not sure but doing this in public places.
Then I remember seeing other sites that are related to money lending sites a few years ago. Instead of getting load from banks, you ask from peers. The sites are even more popular now. Some college financial offices are even listing these sites as alternative way to get loans.
"Matching Borrower with Lender, Social-Network Style"
"Peer to Peer Education Loans"
Other sites are…
Obviously, lenders and loaners are getting something out of this service. The needs for both parties are different but the service brings them together to provide what both user wants. To bring this service as legitimate, the service site has to create “trust” to users. I wondered how this kind of service would be started… Peer-to-Peer service is common, but the amount of money both users deal are completely different level. Would this be a common service in future? Is this part of cloud service?
As we wrapped up service design course, I thought I would ask others about this issue. Digital Copyrights has been and will be one mess experience for both content owner and users. No technology so far seemed to work well between content provider and customers
Many industries, particular music and movie have been out of control with how they deal with copyright infringement. General public are fed up but the industries are not responding what customer wants. RIAA is actively going after individuals who violated copyright. The recent case of a grad student from Boston who was ordered to pay over $22,000 per song (total of 30 songs) shows how broken the system is.
AP thought they deserve to get paid every word they publish. So they implemented iCopyright to charge # of words, starting $12.50 per word. Also AP got Copyright Bounty Hunter to go after those who violated the copyright. Guess, how this AP copyright ended up working? James Grimmelmann, associate professor at NY Law School, submitted an expert from Thomas Jefferson’s letter, not written by AP. Of course, AP said he owes $12.
I understand you want to get paid for what you create. But the overall service is broken. The experience of service is not pleasant to both creator and users. Smaller music service sites are trying different models to accommodate both musicians and users. Are there any ways to design workable and realistic service for this kind of issues?
Monday, August 3, 2009
I was pointed to this post about the SDK for Microsoft Surface which permits multiple mice to simulate multi-touch interfaces. This would help verify the correct manipulation features, but would not provide accurate data for ease of use or speed for this different form of interaction. It seems like this area is currently lacking in prototyping opportunities, but then maybe that is the price of using interaction concepts with newer technology.
Friday, July 31, 2009
I find this interesting because it is definitely not the most sophisticated solution, but if you're trying to get people to act on a link, sophistication may not be what you want. Instead, you need to take the route of advertising, address the broadest range of users, and tell them what they should do instead of hinting at it.
What do you think? Is it more important to cater to the masses even if the design is not as clean, or is there a way to marry the two and have good, effective design that pushes action?
From a developer standpoint, the biggest barriers to adopting these techniques are the complexities of computer vision and manipulating 3D space. As a developer, I'm particularly interested in ARtisan, which tries to simplify the use of Flash AR tools FLARToolKit and Papervision3D. Flash is uniquely positioned for the AR space because of the ease with which applications can be distributed and its access to the host computer's camera and microphone. If you have a webcam, I would definitely recommend checking out some of their examples.
Finally, this post has some other interesting examples of AR experiences.
Thursday, July 30, 2009
Part I of the article concludes:
"Like everything else in design and research (often overlapping terms that I’ve avoided specifying here), the answer to “design without research?” is, it depends. Among other factors, it depends on how much we already know about our customers (perhaps through our own experience). It depends on what we hope to learn and how we want to use that learning to create action. It depends on where we are in the development timeline of a product or service, and whether the product or service is new, me-too, innovative, or a redesign. It depends on business constraints like time to market, the maturity of the category, and the cost to evolve the design. No doubt it depends on other things as well. What do you think it depends on?"
Part II of the article makes the point that I would strongly agree with that when presenting design alternatives or business concepts to users in order to get feedback, it is important to give the concept you are presenting the best presentation possible. Meaning, the design alternatives are the most accurate representation of the concept you are getting feedback on. He summarizes the article with the following:
"When we’re using research to understand whether or not a concept is going to address people’s needs, we need design to create the best representation of that concept, and we need design to translate the output from that research into the next iteration of that concept. We can conclude that research needs design, before and after. Rather than treat research and design as separate activities (sometimes performed by siloed departments or vendors), I would encourage all the stakeholders in the product development process to advocate for an integrated approach in which design activities and research activities are tightly coordinated and aligned."
For the full articles, visit the following links:
Part 1: http://interactions.acm.org/content/?p=1255
Part 2: http://interactions.acm.org/content/?p=1273
Saturday, July 25, 2009
Now a most-popular NYTimes article is related: designing the food canister that a bean can't open. It's almost anti-user design: know your user so well you make the product unusable to it. Or perhaps it's just an example of multiple stakeholders: bears and campers.
One more interesting quote from Stephen Anderson's site:
“You never change things by ﬁghting the existing reality. To change something, build a new model that makes the existing model obsolete.” — R. Buckminster Fuller
Thursday, July 9, 2009
First off, for project 3 on encouraging people to go for walks, you may find Social by Social (a practical guide to using technologies for social impact) helpful, at least if you find that the lack of physical exercise, like walking, is essentially a social problem and not about the individual. I discovered this site from Experientia's blog. I, admittedly, have a bias in looking at things to see the social--even in creativity--but I haven't actually looked at the issue of why people walk (or don't) so I can't say whether or not this is a viable solution path (only your data can tell you that).
Also, and I wish I had known about this site earlier (so I could pass it on earlier) is this new site on Service Design tools, which goes over various ways of communicating service design to clients (so a lot of what the last and current service design project deliverables covered).
Also, in case there are still any lingering doubts of the benefits for design-oriented folks to know about implementation, I recommend reading this blog post about a designer now wearing more of a devloper hat ("programming for non-programmers", mostly, but the reflections are still very relevant).
Hope you all find some of this useful.
Tuesday, June 30, 2009
Although since I'm writing up a blog post anyway, I recommend checking out this hour long interview with Don Norman where he talks about service design, user experience vs. usability, and several other topics. Project 1 and 2 focus primarily on what I refer to as 'classical usability' with a lot of focus on Cooper for design and Tullis for evaluation where it's about creating applications where the user can complete a task because the design follows the cognitive concepts in the layout. The service design project is more about the holistic user experience, taking into account not just the usability but also the emotional and other aspects that allow a user to forgive mishaps so long as there is that extremely salient service moment that leaves the customer happy with the overall experience (Norman uses the example of how at Disney everybody hates the lines--which are everywhere and make up the majority of the experience--but almost everybody would go back).
On a final point with service design, I am going to throw out this controversial idea (feel free to discuss in the comments:
Computers will never replace the best waiters and waitresses but very few waiters and waitresses excel past the mediocre level* and computers will always outperform the mediocre waiters and waitresses.
*I am defining "mediocre level" as taking an order and delivering food. E.g. doing their job at the bare minimum.
Tuesday, June 16, 2009
The second is Layar, an Android application from the Netherlands that overlays useful digital information over a real-time video from the phone's camera:
Imagine a shopping experience that show furniture designs as they would look in your own home. Or advertisements that render a three-dimensional view of a product when viewed "through" a mobile device. There's lots of potential for abuse, but as these composite interactions becomes more popular I expect we'll see some really interesting innovations.
Monday, June 15, 2009
On a related note, and something I didn't emphasize enough on this project, is that a good designer documents all decisions and should be able to provide some type of justification for the decision. They might not like it, but that's the way the business world works (not just engineering)--if you can't give a reason then a firm hiring you is justified in dismissing your input since nothing backs it up. There should be a reason why the button is placed on the lower left instead of the upper right and you should have some type of reason behind choosing the line width and color (note: I only mean this to a degree, if the difference isn't perceptible to most people then there's no issue but a thicker line creates more of a disconnect between different types of content and different shades can convey different emotions). For this project I'm not making you justify the minor aesthetic details like that but be aware that some people will ask (and you better have an answer).
And here's something to get the marketing people all up in a tizzy (do people still use that word, really?), there's a piece written about how the products are worthless. This gets into a lot of what we're talking about with the social theories, Where the Action Is, and service design in that the product itself does nothing for a user until it becomes useful to the user in a given situation/context. For better or worse, we are transitioning into a service/knowledge economy in the Western world and talking about the world in terms of products is so last century--you have to think in terms of 'value added', 'experience', etc.
Sunday, June 14, 2009
As a mathematician and language geek, I'm most drawn to interaction optimizations at the symbolic level. Through my programming career, I've been exposed to dozens of symbolic abstractions, ranging from Logo and my TI-85 to academic amusement with Scheme to "real-world" languages like C and Java. For the most part, however, the languages have been more similar than different. And with the exception of a course on functional languages, the style of programming was always the same: tell the computer how to push these bits around. For the majority of problems, that was simple enough, particularly with the steady march of CPU speeds in step with Moore's Law.
Well physics decided to step in the way of our 20-GHz CPUs, leaving us instead with dual- and quad-core systems. There's still an increase in processing power, but taking advantage of it requires new ways of thinking. Among these are various new (or new-again) symbolic abstractions that will be essentially to get developers back to the point where the electrical systems are sufficiently hidden that we can get on with the real work of building the next generation of textual and graphical interfaces. As a developer on the Microsoft platform, there are two in particular that are of interest: Axum and F#.
According to Microsoft, "Axum is a language that builds upon the architecture of the Web and principles of isolation, actors, and message-passing to increase application safety, responsiveness, scalability, and developer productivity." In other words, it's a domain-specific language (DSL) built specifically for scenarios involving distributed and concurrent computation. I haven't built anything with it yet, and at this point it remains very much experimental, but the concept has a lot of promise to faciliate the creation of applications and frameworks that can seamlessly handle the new architectures that have emerged. For more information, check out the Axum page on MSDN.
Functional languages have been around for a very long time, and they are based on the lambda calculus which has been around even longer. But only recently have they started to come back into mainstream view, due in part to new functional languages for the major development platforms: Clojure and Scala for the Java Virtual Machine, and F# for .NET. The other reason for this comback is the ease with which functional languages handle the problem of concurrency through the use of immutable values and data structures. These languages also provide other higher-level abstractions that move developers away from specifying "how to push these bits around" and more toward specifying what they are trying to accomplish.
In both cases, there is clear value in solving the difficult problems once and letting symbolic abstractions shield the rest of us from ever having to think about it at a low level. It will always be necessary to have some knowledge of what's happening behind the scenes, just as managed memory doesn't free the developer from memory considerations completely. But leaning on advanced symbolic abstractions is one more way to advance the state-of-the-art in HCI.
Thursday, June 11, 2009
We have started to discuss the service design and it’s concept. I really like the idea of experience as a whole interaction and focuses on you as a customer. I just recently read relevant service design topics on the web.
A letter to AA:
A reply from AA:
The letter from AA architect touched a few things about Front and Back Stage Design process and how it is completely messed up system that they have to work in bureaucratic/political corporate environment. The website, especially AA would suffer tremendously due to many departments are in charge of area in the website. Each department have its objectives and goals to meet. By the time all of the contents are added into the site, it become large mess to customers. As a customer, you know what you need to do from their website. It is not a very long list of tasks, but the site makes it complicated.
Dustin responded a letter and mentioned that “customer experience is the new brand”. I have to agree with the idea. Everything, I mean everything the company communicates to the customer or the other way around must be part of corporate strategic plan. You have to shake your head to the airline companies. I am not sure about you, but I haven’t had good experiences when I flew. I don’t care for security procedures, booking, pricing, airport, scheduling, food, seating, and the list goes on. It’s a “have-to” thing to get one place to the next quicker. So you have to ask why don’t the airlines make the experience more pleasant, especially in the front end where a customer has to interact before flying. The during a flight and after is important too.
The UI design on the web and services people have to interact to be served are necessary evil that the corporations must to rethink. Sell the experience!
Another interesting read about painful process of corporate product development:
New experience in search engines:
Another quick note about the new development with a few search engines that just released to public.
Microsoft Bing is a new search engine that displays related content, but little more visually interesting to crawl the search engine. It shows you some related contents that you are looking for. Photos and videos search displays somewhat different from what you expected from Google. I especially like the thumbnail views of video that you can actually play a few seconds when you mouse over. $100 million marketing campaign is not just the hype only. It has some minus but the concept is good. However, there is already a talk about copyright infringement of music/movies in thumbnail’s view.
Wolfram Alpha, a maker of Mathmatica, released this interesting knowledge-based computing. They call it, “a computational knowledge engine”. Is this become the rise of machine? We have to see...
As of now, Wolfram|Alpha contains 10+ trillion of pieces of data, 50,000+ types of algorithms and models, and linguistic capabilities for 1000+ domains. Built with Mathematica—which is itself the result of more than 20 years of development at Wolfram Research—Wolfram|Alpha's core code base now exceeds 5 million lines of symbolic Mathematica code. Running on supercomputer-class compute clusters, Wolfram|Alpha makes extensive use of the latest generation of web and parallel computing technologies, including webMathematica and gridMathematica.
Tuesday, June 2, 2009
Sunday, May 24, 2009
- John Rhode's Interview on Selling Usability
- Selling Usability by John Rhodes (Amazon link)
- UXMatters on Selling User Experience
- UXMatters on Evangelizing UX
- Selling Usability During a Recession