Showing posts with label user interface design. Show all posts
Showing posts with label user interface design. Show all posts

Tuesday, July 27, 2010

File Under "This Makes Me Feel Better"

"Designers get pulled off projects and their ego is bruised. Feeling hurt is how they should feel. If their ego wasn’t bruised, they weren’t trying hard enough. Professionalism means they don’t show it, but if they are good designers, they care. And caring means feeling pain sometimes."

- Christina Wodtke
GM of Social at Myspace
http://www.boxesandarrows.com/view/fear_of_design

Many designers work alone in large corporate environment - just like I frequently do - they need to know that not every project will be continued or successful. The fact that one feels pain when a project fails is good - it means you are a professional who cares about your work!

Paper prototype for functional and user interface design window_and_mirror_blue

Tuesday, February 19, 2008

Some User Interface Design Fundamentals

User Interface Design for Programmers by Joel Spolsky (Paperback - Jun 26, 2001)

About Face 2.0: The Essentials of Interaction Design by Alan Cooper and Robert M. Reimann (Paperback - Mar 17, 2003)

The Elements of User Interface Design by Theo Mandel (Paperback - Feb 1997)

Ambient Findability by Peter Morville (Paperback - Oct 1, 2005) - Illustrated

User Interface Design and Evaluation (The Morgan Kaufmann Series in Interactive Technologies) by Debbie Stone, Caroline Jarrett, Mark Woodroffe, and Shailey Minocha (Paperback - Mar 22, 2005)

The Design of Everyday Things by Donald A. Norman (Paperback - Sep 2002)

The Humane Interface: New Directions for Designing Interactive Systems by Jef Raskin (Paperback - Mar 29, 2000)

The Essential Guide to User Interface Design: An Introduction to GUI Design Principles and Techniques, 2nd Edition
by Wilbert O. Galitz (Paperback - May 2002)
Excerpt - page 34: "... 34 INTRODUCTION TO SCREEN DESIGN FOR THE GRAPHICAL USER INTERFACE recognition.) When you're finished with ..."

About Face: The Essentials of User Interface Design by Alan Cooper (Paperback - Aug 11, 1995)
Excerpt - page 1: "... I: The foal Designing for Users Technology is the engine that drives user interface design. ..."

The Windows Interface Guidelines for Software Design: An Application Design Guide by Microsoft Corporation (Paperback - May 1995)
Excerpt - page 3: "... Design Principles and Methodology A well-designed user interface is built on principles and ..."

Interface Design: Effective Design of Graphical User Interfaces for the Web and Multimedia Pages by Alistair Dabbs (Paperback - Sep 2002)
Excerpt - page 16: "... frequently as elements of everyday interface design; they are more likely to ..."

Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces (The Morgan Kaufmann Series in Interactive Technologies) by Carolyn Snyder (Paperback - April 2, 2003)
Excerpt - page 3: "... for designing, testing, and refining user interfaces. In the early 1990s it ..."

The User Interface: Concepts And Design by Lon Barfield (Paperback - Mar 31, 2004)
Excerpt - page 1: "... reader in mind, is what user interface design is all ..."

User Interface Design: Bridging the Gap from User Requirements to Design by Larry E. Wood (Hardcover - Dec 2, 1997)
Excerpt - page 2: "... USER INTERFACE DESIGN effective design, there is usually ..."

Web Style Guide: Basic Design Principles for Creating Web Sites; Second Edition by Patrick J. Lynch and Sarah Horton (Hardcover - April 10, 2002)

Don't Make Me Think: A Common Sense Approach to Web Usability (2nd Edition) by Steve Krug (Paperback - Aug 18, 2005)

Designing Interfaces by Jenifer Tidwell (Paperback - Nov 21, 2005) - Illustrated

The Essential Guide to User Interface Design by Wilbert O. Galitz (Paperback - Jun 15, 2002)
Excerpt - page 53: "... The User Interface Design Process Part 2 presents an extensive series of guidelines for the interface design process. ..."

User Interface Design: A Software Engineering Perspective by Soren Lauesen (Paperback - Feb 14, 2005)

Sites - Jakob Nielsen's Website
The most widely read and recognized usability expert, Dr. Nielsen was a Sun Microsystems Distinguished Engineer.
http://www.useit.com/
http://www.useit.com/alertbox/
http://www.useit.com/alertbox/20030825.html

Future Perfect, Jan Chipchase
Principal Researcher, User Research at NokiaBlog
http://www.janchipchase.com/

Joel on Software, Joel Spolsky
Software developer (formerly with Microsoft), author
Blog
http://www.joelonsoftware.com/
On writing content, the book Best Software Writing.
http://www.joelonsoftware.com/articles/BestSoftwareWriting.html

Web Style Guide
http://webstyleguide.com/

Donald Norman’s Site
http://www.jnd.org/
Dr. Norman former VP of research at Apple Computer is credited with creating the field of usability. He recommends the following books

Handbook of human factors and ergonomics Gavriel Salvendy 2005: Hoboken, NJ: Wiley.

Universal Principles of Design. William Lidwell, Kritina Holden & Jill Butler 2003: Gloucester, MA: Rockport Publishers.

Why Art Cannot Be Taught: A HANDBOOK FOR ART STUDENTS (Paperback) by James Elkins "Is there anything worth knowing about art schools in past centuries?..."

http://www.informationdesign.org/archives/2006_06.php

http://www.uxnet.org/

Monday, January 21, 2008

Saying thank you, and that is all ...

Some people live user centered interface design and welcome feedback from users, but so far I have found most people form strong opinions, say they want open feedback from users and then explain to the user why they are wrong or show other methods to refute the end user's input, if they ever even ask in the first place. There is never anything wrong with just saying "thank you" to an end user - to never turn down that opportunity is a goal of mine, served with a fresh cup of "shut up".

One personal exception to this tendency to show who is right or wrong, which still drives me to think it is possible to be open minded and really driven to build great things for people by listening to what they say, is the founder and principal of BlinkIA here in downtown Seattle, Kelly Franznick -- http://www.blinkinteractive.com/aboutus/ .

My goal as a design engineer is to live up to Kelly's demonstrated ability for open listening without forming strong opinions, while communicating in a straightforward business manner - this he does about conclusions he reaches on UI / UX test results, all with a sense of humor. It's not all about rules either.

For one thing it is difficult to be successful in this or any field if you don't have a contract or money coming in the door. One's user (stakeholder always sounds like a vampire slayer to me, ha!) can also be construed to be whoever pays you, in addition to all the other users/stakeholders.

When you can successfully state a point of view based on watching and listening to user feedback coupled with business needs, all without scaring off the person holding the capital, then that is success, even if they don't agree with implementing a recommended design change. They too may have their reasons, not the rarest being a lack of comprehension (not enough experience to understand) or a lack of a shared language to communicate with.

If one's conclusions are correct, for example as I believe I may have been about Google's ecommerce application, (part of which is now called "Google Checkout", which I believe eventually will be integrated as a silent backend through their API), the businesspersons who one did not convince the first time through will be more likely to listen the second or third time.

One can only hope this is so, for the benefit of saving many end users time and frustration so they may take the happy train of sunshine and continue pursuing good things for themselves and others, and surf away from their experience with your information application as happy campers.

Tuesday, December 12, 2006

Three reflections on an email design assignment

Adapting and Appropriating eMail, ProcessRight WorkFlow
Appropriating and Adapting eMail - ProcessRight Workflow Poster

First,

I have always loved email since 1978 when I began using it over the University of Alaska’s UNIX main frame in Anchorage to email people in Fairbanks. Significantly at that time we were discussing music, Bob Marley and The Wailers (how I discovered them), another thing of strong social importance Microsoft managers failed to recognize as valuable.

Why Bill Gates and the factory did not see what a huge innovation email was, and how extensible, I never understood. Why, despite my input and the input of others at Microsoft, development for email failed to gain much footing. Until the last few years a very small amount of money was invested in developing email. This was due in part to the structure of the development managers directly reporting to Bill Gates -- within that hierarchical structure, at each level there is a decreasing amount of authority, however at the next level down one can not really question the voice of authority above. This is an old fashioned management style based on military structures developed for waging war.

From interviews I did last fall including one of a former Microsoft lead email development engineer, I found that all that required was one manager at one level to wipe out Bill Gate’s vision – if Gates said spend $10-$20 million, the next manager changed that to 3 million, or less, there was nothing the visionary email engineers below could do about it. Eventually they quit and formed other companies.

Everyone understood the value and power of email of communications – but no one, save the customer voting with their buying power, could get management to budge. Finally when Microsoft's eMail product became the leading selling product after Windows itself did Microsoft management take notice. They were forced to do so by the downward trend in stock value and sales. Now we clearly see all end users really need are two things – browser and email -- and some products can be both and more at the same time using the same basic interface.

I believe this is why we have this as an assignment – had Gates encouraged other non-traditional, cooperative, even tribal structures to form leadership in various ways the product we describe would already exist, not just be embedded as a possibility in applications such as Outlook which require a developer to pull into reality.

In this way, over so many years, I learned that new ideas can be killed due to stubborn traditional systems which may not be recognized for what they are. New ideas may long await fresh new management.

Second,

Having the third party review engage the cohort from our idea stage down to their formal presentation was a stroke of genius in envisioning and shaping up our resulting product.

I found much that I took for granted was still embedded in my thinking as an “of course” and not explicit. In communicating with people you have to make your ideas explicit.

So such usability issues as landing pages to track the results of a process are one of these “of course” structures, which will be included in my future product designs.

Performing recent usability studies I found the exact same problems with beginners learning software exist now as they did in 1989 – the year Windows 3.0 was released. In 1984 I recall having very little trouble learning the MacOS interface.


Third,
The VIEW

There is a small political commentary nod in our selection of the title for the company “ProcessRight” Actually it relates to the political LEFT because the public voided the Right. I recently searched on ‘processright’, and quickly realized it owes its name in part it to the format of method calls in C++ and C sharp, such as used in the Invaders game at Duke University:

http://www.duke.edu/~jbs3/cps108/ooga/oogadocs/invaders/Invaders.html

“ProcessRight
public void processRight() - Provides the rules for what to do when a left event is pressed
Overrides:
processRight in class Game”

We used Google Talk IM to communicate in the last hours of our project. One of my cohorts, an employee of our favorite 800lb gorrilla across Lake Washington, may not want a GMAIL account to communicate using Google Talk IM.

It is true that Patton said, “There's a great deal of talk about loyalty from the bottom to the top. Loyalty from the top down is even more necessary and much less prevalent. One of the most frequently noted characteristics of great men who have remained great is loyalty to their subordinates." This should apply to Microsoft employees too.

But you got to get into the game so I invited my cohort to get an GMail account to learn what the other guy is doing - here is why - to paraphrase Patton (if even from the film) metaphorically --

'Google are Microsoft's enemy. Wade into them. Spill their blood. Shoot them in the belly. Lift their software and interface ideas.'

“For over a thousand years, Roman conquerors returning from the wars enjoyed the honor of a triumph - a tumultuous parade. In the procession came trumpeters and musicians and strange animals from the conquered territories, together with carts laden with treasure and captured armaments. The conqueror rode in a triumphal chariot, the dazed prisoners walking in chains before him. Sometimes his children, robed in white, stood with him in the chariot, or rode the trace horses. A slave stood behind the conqueror, holding a golden crown, and whispering in his ear a warning: that all glory is fleeting.” -Patton

Last,

Very much enjoyed working with my team – it was a blast!

“We're jammin'
I wanna jam it wid you
We're jammin',
And I hope you like jammin', too
Ain't no rules, ain't no vow, we can do it anyhow
I'n'I will see you through;
Everyday we pay the price with a little sacrifice,
Jammin' till the jam is through. Ooh, yea.

We're jammin'
To think that jammin' was a thing of the past
We're jammin',
And I hope this jam is gonna last
No bullet can stop us now, we neither beg nor we won't bow
Neither can be bought nor sold
We all defend the right; Jah - Jah children must unite
Your life is worth much more than gold. Ooh, yea.
[1]

[1] Song lyrics from Robert “Bob” Nesta Marley, “Jammin’” Release Date: 1977 Genre: Reggae Label: Tuff Gong Downloaded Monday December 9, 2006 from http://www.hotlyrics.net/lyrics/B/Bob_Marley__amp__The_Wailers/Jammin_.html Lyrics originally published on the album.

Sunday, November 05, 2006

Solomon's Mine in Time -- on Children's Information Retrieval Behavior and Survey of MP3 Usage by Mark Latonero

"Children's information retrieval behavior: A case analysis of an OPAC," by Paul Solomon, 1993

“Survey of MP3 Usage: Report on a University Consumption Community,” by Mark Latonero, 2000


Solomon's Mine in TimeOn reading "Children's information retrieval behavior: A case analysis of an OPAC," Paul Solomon’s 1993 study published in the Journal of the American Society for Information Science, 44(5): 245-264, I learned how important context, especially the date a study was written, is to critical analysis when reading articles in our rapidly changing information environment. Overall I enjoyed his kind and informative tone. He showed real empathy with his study subjects and introduced new ideas to me, which I enjoyed the best.

Solomon opened his introduction with a literature review. By using the term “excitement” in the second sentence I felt Solomon might be a writer who possesses enthusiasm, and finding his mention of Case, knew that this writer was someone to read thoroughly. Solomon also assumed that studying new algorithms for search would not add as much to the field as the study of human subjects would. I was encouraged by this viewpoint.

Solomon’s article was written in a clear, factual manner. I especially enjoyed his self aware sense of humor and sense of playfulness as expressed in his problem statement:

“Searchers, in turn, have their own way of thinking about their topics and interests. Although tools such as the four-volume tome, Library of Congress Subject Headings, are sometimes made available, users for the most part either avoid them, are unaware of their availability, or do not know how to use them. (Solomon 1993)”

By using the term “tome” he gives some idea of what remains unstated – that information searchers are probably not going to read a huge set of books on subject headings to become expert in the science of information seeking and retrieval. This is especially true since we later hear about young children looking up “dinosaur” and having trouble with their spelling.

In the problem statement, Solomon addressed the ubiquitous answers computers give to not finding searches (“TERM NOT FOUND” or “QUERY ERROR”) and suggested that information retrieval systems provide instruction and support instead of dead ends. His main theme, supported by the evidence he collected, was the importance of practical solutions to such problems, so that even a child can use search systems effectively.

The feeling of respect he imparted regarding the children he interviewed and observed was very enjoyable. As a result, I felt he did not go into the field knowing it all, or with something to prove, but that he actually did his work with a marvelous sense of discovery.

Solomon’s observations and call for future research – “Continued testing with different groups of children has helped to refine the interface into one that lessens the skill barriers that searchers face. These barriers, such as search term generation (recalls) are often problems for adults. Thus, workable interface solutions for children may influence designs for other users as well.” (Solomon 1993) and when discussing Grade-level impacts –

“…the syntactic idiosyncrasies of the OPAC software influenced all users from time to time.” (Solomon 1993)

-- struck me as hilarious, because rewording with his prior observations it adds up to:

“Everybody, regardless of age, likes more well designed tools for search, not brain dead ones.
[1]

This is humorous because I am reading this study as someone who has had search engines like Google available for many years -- Solomon didn’t have advanced search and neither did the children he studied. To find information, even with a computer-based OPAC system, they had to know how to spell and how to remember a search. They also had to understand related and broader search concepts. I have the luxury of terribly garbling
[2] my spelling in a search and then most online search engines will attempt a correction. In addition, I can completely forget a search, because I can store the results as a favorite. There are many ways to stumble onto the same information I once found, to recall it, through tags, and other tools commonly available to those on this side of the digital divide.

In fact, the reason I noticed the date of the study is because the OPAC search tool Solomon was using at the time sounded like some kind of torture tool to me; using graphics effectively he included the user interface as a screenshot, details with other screenshots, with the description of how searches returned results. Those graphics and description led me to check the date.

Prior to that I wondered who would put their kids into such a backwards school, were they neo-luddites
[3], or did they have other reasons such as the context of the study itself? The date told me everything. Then my mind turned completely and I felt these students may have done better in their lives as a result of Solomon paying attention to them. As a result of the training that occurred naturally, they learned how to find information faster than other students[4].

In a way his problem statement can be reduced to: ”Information retrieval systems need to be designed for real people, even kids.” He reasons that children are a perfect example of people who use an information retrieval system with no expectations, and learn it. Researchers can learn about what information retrieval solutions needs are to improve these systems. Solomon’s research question was “How do children use Information Retrieval Systems?” using the OPAC system. The methodology was very appropriate for his research problem; I was especially fascinated by searching for information rituals that he discovered in children in his study
[5].

Clearly in light of new search engine technology we see that his conclusions and recommendations were true and correct. Possibly his own studies brought forth fruit. Those very things he recognized and wrote about have changed in modern retrieval methods on the World Wide Web.

In hindsight we see that having too much information return in a retrieval can be nearly as bad as nothing being returned, but he brushed by delving much into that, possibly due to the nature of difficulty of returning large amounts of data successfully.

I could not interpret some of Solomon’s statements. On page 247 of the publication of his work in the Journal of the American Society for Information Science, he speaks about “children of average intelligence investigated more themes,” and I wondered in contrast to what kind of intelligence in performance? Offering only the middle point is difficult to understand if you mean higher or lower intellects investigate more themes. Some highly intelligent people focus more on one thing so may not have a broader range of understanding.

On page 254 the truncation reference to “e.g. (hurr@)” raised questions. Perhaps the @ sign was being used as some kind of wildcard. In such a way would someone from the future be unable to interpret code, software, hardware or related terms embedded in a current Hacker Koan
[6]? If you use symbols, it’s important to reference their meaning in some way so it’s not lost in time.

My plans are to return to Solomon’s study and mine it for more information in the future.



Latonero’s MP3 Study

Upon the recommendation of my cohort Jagadish Yadavadri I read Mark Latonero’s survey results on University of Southern California students’ consumption of MP3 sound files and self reported purchasing patterns. The fact that as a master’s degree student he obtained funding of $2,000 dollars to perform the study
[7] while others just cried foul, reminded me of the old adage, “Everyone talks about the weather, but no one does any thing about it.” Latonero took up the actual inquiry into the subject of MP3 use, its effects on purchasing patterns, and published one of the first empirical studies on the subject.[8] He deserves credit for his thoughtful approach, although his study reports results, and does not serve as well to inform.

One of the notable differences in the style of these two kinds of reports, Solomon’s case analysis and Latonero’s survey, was the amount and kind of information provided. The survey stands alone lacking outside reference materials; it contained no references and no recommendations for further studies, related or otherwise. The study particulars are visually very well documented with graphs and short explanatory interpretations. The reasons driving the study refer to “speculation” and “most media reports” without quoting one professional publication or news article. However, readers can imagine the worried music production company executives pacing back and forth wringing their hands and wondering about depressed marketshare, Dr. Latonero’s survey focuses on what 275 randomly selected respondents actually reported at the time.

His main conclusion was clearly expressed on the first page and second paragraph of his study, where he stated that –
“MP3 File sharing is wildly popular, but contrary to most media reporting, the majority of students surveyed are still willing to pay for recorded music. The study found little persuasive evidence to indicate that student’ aggregate use of MP3 technologies has been harmful to either the recording industry or artists.”

Since this study is self reported and does not focus on the actual marketplace I wondered how Latonero could backup this statement. Stating facts and backing them up with more evidence lends more weight to evaluation and analysis. Clearly there is something going on in the music industry related to file sharing and the Internet.

For example as reported in our class the popular music store Tower Records filed for Chapter 11, on Feb. 9, 2004
[9]. At the time this was widely reported in the media, and articles written at the time said Tower “suffered from rapid changes in the music business, especially the exploding popularity of downloading music for free from the Internet.[10]” Not presented in our class was that Tower Records pulled out of Chapter 11 protection only 35 days after filing[11]. This calls into question not only the causes but also what exactly the problem was. The reason provided by the U.S. Securities and Exchange Commission quoted in the same article was that Tower, after borrowing money for expansion, failed to make a profit -- “revealed the retailer had lost money for 13 straight quarters.”
Similarly contradictory reports from record companies and artists call into question just where and how people purchase music, such as in which formats
[12]. This also creates questions regarding changes in the music industry which appear that their actions are now and will be enforced in the future by the new technology more than the law enables enforcement of anything.

There are such a wide number of variables, and possible solutions to what some view as a problem. Others in the music community view these same issues as an opportunity. No longer do individual artists require huge marketing machines to promote their music, which prior to this meant locking themselves into a unique form of debt termed “an advance”. These same artists can promote themselves to their audiences directly using new Internet based marketing techniques and many business and technical models.

Internet wags offer that “major record labels have been criticized for failing to take advantage of the potent marketing opportunity presented by the Internet and the MP3 download rage
[13]” are in my estimation correct. That industry is resisting inevitable change through a newly enacted law, THE DIGITAL MILLENNIUM COPYRIGHT ACT OF 1998[14] in the Web’s Wild West environment. Regarding the law, educated and informed individuals’ express confusion of what the laws even are and how such laws are related to digital media, as repeatedly shown in studies including our own “IMT510 – Final Report – Group 5” detailed on pages 5-7.

Though I appreciate Dr. Latonero’s survey it is far too simplistic to say downloading music doesn’t appear to be affecting the industry based on just one survey. Even taking into account the date it was written the opinions seem naïve.
[1] My original margin note read “Stupid software hurts everyone.”
[2] While I draft this paper in Microsoft Word, Word fixed the word “garblling” to “garbling” but I could not make it stop correcting it for this note, nor stop auto correcting a capitalized word unless I turned off the function for the entire page.
[3] Reference term Friday November 5, 2006 located description at: http://en.wikipedia.org/wiki/Neo-luddism
[4] “Change in Competence of Children”, Solomon, P. (1993). "Children's information retrieval behavior: A case analysis of an OPAC." Journal of the American Society for Information Science, 44(5): 245-264.
[5] Rituals may be something not well understood in information retrieval.
[6] Reference example Friday November 5, 2006 located at:
http://en.wikipedia.org/wiki/Hacker_koan
In the days when Sussman was a novice, Minsky once came to him as he sat hacking at the PDP-6.
"What are you doing?", asked Minsky.
"I am training a randomly wired neural net to play Tic-tac-toe", Sussman replied.
"Why is the net wired randomly?", asked Minsky.
"I do not want it to have any preconceptions of how to play", Sussman said.
Minsky then shut his eyes.
"Why do you close your eyes?" Sussman asked his teacher.
"So that the room will be empty."
At that moment, Sussman was enlightened.
[7] Reference downloaded Tuesday December 5, 2006 located at: http://www.usc.edu/student-affairs/dt/V142/N44/01-napster.44d.html
[8] Reference downloaded Tuesday December 5, 2006 located at: http://www.stanhopecentre.org/about/
[9] Reference downloaded Tuesday December 5, 2006 located at: http://www.cbsnews.com/stories/2004/02/09/entertainment/main599008.shtml
[10] Reference downloaded Tuesday December 5, 2006 located at: http://www.cbsnews.com/stories/2004/02/09/entertainment/main599008.shtml
[11] Reference downloaded Tuesday December 5, 2006 located at: http://www.findarticles.com/p/articles/mi_m0FNP/is_7_43/ai_115080290
[12]Case, D.O. (2002) p. 263. Looking for Information. New York: Academic Press. “Journal of Marketing …”How do Customers and Consumers Really Behave?,” Donald Lehmann (1999)… the focus must shift, Lehmann says, away from viewing the consumer as a conscious, rational “decision maker” and toward the customer as an emotional, unfocused, learning human. Allegedly “irrational” behavior should not be merely identified as an aberration but should be modeled and explained as much as possible.”
[13] Reference downloaded Tuesday December 5, 2006 located at: http://www.goingware.com/tips/legal-downloads.html
[14] Reference downloaded Tuesday December 5, 2006 located at: http://www.copyright.gov/legislation/dmca.pdf



Dr. Paul Solomon's Website at The University of North Carolina, Chapel Hill







Review of two papers for the IMT510b, Masters of Science in Information Management, at the iSchool, University of Washington, Seattle. Wednesday, December 6, 2006.

Saturday, November 04, 2006

It Works and We Like Using It

No matter how comfortable and well upholstered a chair is, if a person’s goal is not to sit down but to take a shower they need a shower not a chair. With basic and common sense approaches to system design authors on task analysis and usability outline ways to test and examine real people performing actual or visualized tests so that the resulting system designs both function and do so elegantly; these methods can compliment each other to derive the best from both forms of analysis.

In the early days of the Web, basic text sites, with just simple links sold merchandise; one classic site that sold quite a bit of merchandise was a Christmas gift site, center-justified colored text with many links running straight down a single page decorated with randomly placed candy canes. Certainly such sites were not easy to find, nor easy to use and, in a word, ugly. But they were useful.

One might think by now we were way past questions around online goals, and into customizing beautiful interfaces, but with the plethora of reasons to use Webs the need to evaluate what people’s actual goals are in unique situations and combine ease of use customized with real goals has grown as the world reaches past the 100 million mark of live sites(1). We seek to both have things work and enjoy using them; using these techniques ensures both are likely.

To help designers improve systems Task Analysis focuses on what real people do to achieve their goals (Greenberg, 2003), and Usability Evaluations are based on evaluating how discoverable and possible the interface allows for people to achieve their goals (Krug, 2000). Both have the same goal – usable systems – but by different means. The difference is Task Analysis captures the working environment and demonstrates who the user is and what they are trying to achieve, what their goals are including failures. In the Usability Evaluation method the goal is to help designers increase how well end users can accomplish tasks, and even measure the difference from old systems to new ones.

Following the advice of these authors, from the beginning envision incorporating task centered design to follow and watch how users actually work, and make notes as they demonstrate the Web based software for the design process.

As you learn more about a system you tend to forget that you are making due, using workarounds to make up for system flaws, so it is just as you enter a system that it is best to carefully document and record what your own experience as well as the users immediately.

Paper prototypes are a swift approach to get to the first level of task centered design, and it is with this approach that the beginnings of usability start. Working with teams dispersed worldwide one plan of action is to rely first on local teams, using their feedback begin to construct clickable wire frames, iteratively requesting feedback. Scenario based design (Carroll, 2000) will also help make the designers job easier in terms of what it takes to display lots of data and make it useable.

Several authors make the same point that having just a few people perform some usability tests is better than no data at all, notably Nielson. All in all combining pulling from several methods from beginning to end will make both the process and the results better for everyone.

(1)“Web reaches new milestone: 100 million sites” CNN article located at: http://www.cnn.com/2006/TECH/internet/11/01/100millionwebsites/index.html?eref=rss_topstories

Written for IMT 540



Dr. Dave Hendry's University of Washington's iSchool Website

Friday, November 03, 2006

Tuesday, October 31, 2006

Docusign.net heuristic evaluation

https://www.docusign.net is the subject of this heuristic evaluation.

This application uses the technical convention of an authenticated user on a website printing a document to a local service which has been previously installed on the local box to obtain a legal signature from a remote party or to send or respond to such a request. This “printed” document then appears in a registry in the Web interface on which the user will perform actions which the Web services provides. The document with its various suggestions for use, such as SIGN HERE, grants the ability to have legal digital signatures.

From the point of view of a user the convention is sending a letter, with the contents, envelope, and stamp of approval, proof of receipt and similar mail conventions.

While I found it stunningly easy to use, there arose what I refer to as “Omissions of the 3rd Kind” which means they are not intuitive and require more in depth experience with the system to understand, or some simple reason prevents the enduser from understanding the interface such as fear of use.

The first one was encountered after successfully following the steps to install the application locally, and printing the document I wanted to send it to someone to have it digitally signed. As I went through the crabwise steps appearing and clicking “Next”



Addressing the header in the Envelope.

After passing through all the steps, it became apparent that the application was going to allow me to send a document to be signed but not to open and digitally sign a document myself, and then forward it. I stepped through the entire process, taking screenshots of the process. I located the help files and played them and found that the interface did support signing and sending. But first the document needed to be prepared with the locations for signing embedded in the file.

So I stepped through the application again. I felt that instead of “New” in the interface it might have a option to Request Signature, and one for Send Signature as a scenario based design could offer. But as I used it the second time it seemed more intuitive.

I took it at face value, I trusted it. Signers IS Signers – it is anyone including me. So I addressed the “Envelope” to myself.



Adding myself as the addressee for sending and signing

Then I simply followed each step as it was encountered. Forwarded the document to myself through the application and voila, it was done.

The only real limitation I could immediately discover considering the purposes I wanted to use it, is if the new window is open, any documents you have not “printed” will not appear in the open window. This application detests the back button which is not a familiar scenario for some kinds of web uses.

Eureka! This application works from the heuristic point of view and it works well, with three simple caveats
1. View the basic instruction presentation
2. Trust the application to lead you, don’t overthink it
3. Read the interface.

For most users I believe they could get this to work the first time.

Empathy in Well-considered Human Centered Design

Reviewing three basic value propositions to well-considered human centered design by activating the humanistic standard ‘empathy’ in real ways presented by Leonard & Rayport, Dr. Friedman and Holtzblatt & Beyer (see details at bottom of post) I feel that as humans make products it only seems practical for design concinnity to include human-involved practices in the field, resulting in recursive feedback into existing and new systems.

Each author offers a slightly different view of what effective empathy means, but all see it as helping individual people in particular and the masses in general, by listening and asking questions through a variety of methods. All mentioned work-arounds which people employ unconsciously to combat commonplace non-functional technical environments.

Empathy is the ability to feel affection for other living beings, like in a mirror image, to understand other’s motivation, from the dictionary –
“Identification with and understanding of another's situation, feelings, and motives.”
Or in less romantic terms from Holtzblatt and Beyer – “We want our feet to be sore where their shoes pinch ”

Leonard and Rayport see empathy as an exciting way to “delight the customer ” through a process of market research with observers capturing data, analyzing the brainstorming to create prototypes. They also consider it as culture shift to ensure sustainable successful companies. The AOL section seemed misplaced – who cares if a company is technical or not – nobody wants their private contact information sold without consent.

Friedman uses a business based phrase to capture the attention of managers with “Value Centered Design ”. Friedman championed people strongly, with her powerful view of empathy, she framed the wording and examples to convince businesspeople to attempt these solutions. Her crowning materials were the moral views on informed consent particularly where web based user tracking was outlined, illustrated with “how a user might benefit or be harmed by it’s use. ”

Holtzblatt and Beyer use empathy because people just want get their work done on computers, not focus on the tool itself. They elucidated the processes of contextual inquiry. They want users as “strong participants in the design process.”

There are nothing but advantages to the methods outlined with only a few disclaimers:
1. These adaptations consume cycles (resources) and increase the “time to market”; a clear short term disadvantage: as engineers say:
“What do you want for your product? Good quality? Inexpensive? Quick to get to the market? Good, cheap, quick: pick any two.”

2. Change to refocus on the real needs of consumers is impossible for some well established producers (dinosaurs). As Donald A. Norman states in “Want Human-Centered Development? Reorganize the Company”
“It is difficult for a company to make the transition to a consumer-driven marketplace.”

These megalithic monstrosities drive themselves out of business -- with top down management they will not allow employees to have input, much less customers.


3. From experience how could anyone think for a New York second that the practice of tracking end users through cookies does not affect their work? ‘Sniffers’ and ‘click trackers’ grind robust browsers down to a snail’s speed – to read these articles online SpyBot, defragger, and “anti-virus” software had to run to restore the browser’s speed to normal. Less knowledgeable users have to pay for support.

4. Democracy as a human value; living in a failing democracy one wonders if the highly prized human values stated in these article will linger long enough to overcome greed.

empathy. (n.d.). The American Heritage® Dictionary of the English Language, Fourth Edition. Retrieved October 12, 2006, from Dictionary.com website: http://dictionary.reference.com/browse/empathy

Holtzblatt, K., & Beyer, H. (1993). Making customer-centered design work for teams.Communications of the ACM, 36(10), 92-103. Retrieved 1 Dec 2004 from http://doi.acm.org/10.1145/163430.164050.

Leonard, D., & Rayport, J. F. (1997). Spark innovation through emphatic design. Harvard Business Review, 75(6), 102-113.

Friedman, B. (2004). Value Sensitive Design. Encyclopedia of human-computer interaction. (pp. 769-774). Great Barrington, MA: Berkshire Publishing Group.

Wicked Problems in User Interface Design

The wicked problem examples from urban planning that Rittle & Webber (1973) present ring true for information systems design because when addressing and serving more and more people’s diverse needs naturally wicked problems arise, hopefully to be solved, in large part with monkey-like mischievous solutions.

Working with Apple Computers, Mountford (1990) expressed those wicked problems in computer information systems outlining on the first page:
“The world is rich with data, rapidly becoming more and more varied in media type…
The challenge is how to best present and represent such data within the interface, to transform it into useful information.”

Making this suggestion for resolving these problems:
Future interfaces need to incorporate new information types and to accommodate new types of users with additional customized real-world interface metaphors that make information easy to find and use.”

Suggesting merging the efforts of two groups not generally thought of working together, scientists and artists. Comparisons from design traditions, animation, theater, architecture, industrial design, and information display (using Tufte’s famed cartography example of Napoleon’s March to Moscow: The War of 1812”). Suggesting looking at real world tasks and environments to find new ideas which in the technology and music fields we call “mashups” today, Mountford writes:
“Some people believe that new ideas are almost always the result of collisions –juxtapositions or recombinations of ideas” (Koestler, 1964)

These are outlined based on Adam’s (1986) brainstorming steps, as new uses for the object, adapt the object to be like something else, modify, magnify, minimize, substitute, rearrange, reverse or transpose, combine the data into an ensemble. This advice seems virtually the same as Jasper Johns’ esthetic theorem, now considered basic advice to artists --
"Take an object. Do something to it. Do something else to it."

Role playing is suggested as a creative exercise to delve more deeply into the change the idea or object metaphor, and outlining four personality and functional roles, the Explorer, the Artist, the Judge, the Warrior, that could be worn like a costume on Halloween, but accurately providing a warning that if interacting all at once, perhaps the role of the judge should wait to sort the ideas presented instead of eliminating them.

In a way Johns is a good example of the polar differences between scientists and artists, with information science providing solutions to needs looking for something one doesn’t know or have and Johns ‘something’ becoming something else based on “things the mind already knows. ”

Mountford ends advising interface designers to live in the present and future, anticipating the challenges for designers in new ways to use computers having suggested prototyping models, and these several techniques that are in wide use today.

Life too far in the future isn’t always economically feasible, but combining with role playing should help software projects remain practical and satisfying for those of us who enjoy building successful information tools and toys, or just imagineering we are. I feel the analysis is especially accurate as far as customizable user interface design goes.

Jasper Johns sketchbook, page 42 from 1963–1964 http://www.thenation.com/doc/20001218/danto/2

Quote obtained Oct 31, 2006 from http://www.metmuseum.org/toah/hd/john/hd_john.htm

Rittle & Webber / Mountford on Wicked Problems

Rittle & Webber (1973) present the concept that due to the complex nature of human beings scientific answers fail because of the nature of the problems (in the context of Urban planning), such as hard to measure or soft things - societal concerns - which as stated:
“do not have a solution in terms of definitive and objective answer. ”

Mountford (1990) collects ideas from a variety of sources, and advises In effect doing the same thing for information system design - advising finding ways for artistic and scientific people to collaborate, approaching things from a variety of levels of human experience, stating:

“some of our new interface ideas will come from people who study thought, language, entertainment and communication, as well as from people who study hardware, algorithms, data structures. ”

However some wicked problems can only be resolved in granting end users rights and freedoms when it comes to information. Some problems are not served by direct end user participation because it won't help anything and it would not make sense for the many.

Take a WAP (wireless) phone application which has a GPS function (locator that knows where the end user is all the time), and a Search function, so if an end user wants to find a coffee shop within a short distance, they run a Search and the 5 closest coffee shops are returned.

What users may be interested in doing is setting their own preferences to Starbucks Only coffee houses, or only hotwired coffee houses which have computers available for rent. They may be interested in knowing how other people who went there rated the coffee, etc. They may also be planning to meet someone there for reasons other than coffee (but that is for an adult audience).

Google weighs query responses using a variety of ways, but one of them, perhaps the strongest, is by how many times someone clicks on it. This is just like voting - there is a good argument that personalization is the greatest contribution that the American post war baby boomers, with their large purchasing power have made and continue to make today. Companies, and other ensconced or older established organizations still experience enormous trouble facing these kinds of 1 to many, 1 to 1 individualization or personalization changes.

During today’s and yesterday’s job interviews I advised allowing end users to set their preferences on a Web site when they are at a full sized computer to help them find whatever they want on the smaller screen, even if some “father knows best” defaults must be present.

While there are things that the end user may wish to configure, the typical end user is not interested in exactly how the algorithm returned the Search sort to the database, and has no interest in writing it, or contributing to writing it, or even ever hearing the word "algorithm" -- users just want the results and fast.

One of the questions I was asked in a recent interview was a standard sort question for an algorithm, my response was true to that of a designer (or an end user) – “Find a database engineer, sorry that’s not how I think about or consider these problems.”

This remains a problem that inexperienced or less well educated technical or scientific approaches believe that individuals should know everything – most end user/customers can not function in this manner and should not be expected to think about how the machine runs to obtain the results they want, even if they have some kind of mental model.

Imagine if Google functioned only as well as the user’s understanding of search engines permitted – they wouldn’t find anything – they have to rely on Google’s code poets to figure out how to take Search from the functional status of a hammer and make it into a starship. Same goes for Live Search, in my humble option, but that’s a completely different subject.

The wicked quality of being human means that solving ill-defined and sticky problems should not be and can not be the domain of just one facet of thinking about a problem or a system, but as my recent interview demonstrates simplistic thinking about designers roles and customers needs still dominates the software industry.

One solution is everytime a designer uses the term BRAINSTORM and wants to use this technique they should define it so that all present understand that some wild and crazy ideas are likely to form, and just as likely they will go away later, leaving just the good stuff, it's all part of the process. If critics make their presence known immediately, the uber creative will find someplace friendlier to be.

Holtzblatt, K., & Beyer, H. (1993). Making customer-centered design work for teams.Communications of the ACM, 36(10), 92-103. Retrieved 1 Dec 2004 from http://doi.acm.org/10.1145/163430.164050.

Leonard, D., & Rayport, J. F. (1997). Spark innovation through emphatic design. Harvard Business Review, 75(6), 102-113.

Friedman, B. (2004). Value Sensitive Design. Encyclopedia of human-computer interaction. (pp. 769-774). Great Barrington, MA: Berkshire Publishing Group.

Sunday, August 21, 2005

How do you go about developing a good design?

Developing good design intiality can be instant, but then refined iteraratively. If working with other people agreeing on a style of working together, process, and communication are very important.

Depends on what I am designing but generally I start on paper and work through wireframes and the relationship to other products, flesh out the design and maybe do a high end first pass.

I like to gather other people's opinions and datapoints so I will show it around and ask for input. Make some changes and go to the next step.

Sometimes a project also requires advising people what they need to learn or to understand in order to accomplish a very flexible interface. Elements like using the proportion of the golden rectangle (also called the "golden mean") makes user interface design beautiful.

Visio plans often help in visualization for everyone involved.

When we have something we are somewhat happy with I like to run it through user interface studies, even if they are informal using volunteers or paying to do a brief study. Oftentimes this will back up what you already believe about a design but what is really great is when you learn something totally unexpected and you can use it.

With my experience in fine art and design, I enjoy the critical review cycle, but it's always nice to give some positive feedback.

Most of my work is in product or program management so in this way I work interactively with lots of very smart people to design a composite of what we need, using the best ideas and best practices in a cooperative manner.

When designing a small business website, after meeting with the client I begin by structuring the information, and visualizing the look and feel of their site design. Then I follow my iterative process as time and their budget permits.

What is your definition of a well-designed product? Example/Why?

A well designed product is one which seamlessly performs as the customer thinks it should, and expects it to, and is easy to use.

An example is a product which gets fewer support calls.

Another definition is a product that is reliable, and doesn't cause systems or the OS to fail in the worse case, or leaks memory. On the web you don't want to over burden the client or make too many trips to the server.

A well designed product is one that in a way you don't notice, because nothing bugs you. A poorly designed product, for example is one that you can't even authenticate (in otherwords you can't use your userid and password to get into or there are severe complications.)

For an example of a good platform design; within the .Net framework, code is compiled rather than interpreted as ASP script is; this aids in early binding of objects directly resulting in performance gains. Since state management is handled within .Net, lines of code can be eliminated and this reduces the time required to load functionality.

Less processing time between pages contributes to an improved end user experience. A cleaner code set makes upfront development costs per feature less expensive, Web applications quicker to test and deploy, and as a bonus are easier to maintain and update.

I think a great product should be fun to use.

Monday, June 13, 2005

UI / UX Interview with Microsoft

Today I interviewed for a perm position at Microsoft to help redesign a product's training Web site.

What was cool about it was that in the course of our conversations I was shown the original designs for the Web site, and I quickly analyzed it and got everything right in terms of what they had already done and the improvements they needed to make.

But better than that I knew exactly where I could take them successfully to the next stage in functional design.

I discussed what basic changes to make it user friendly and easier to read and negotiate. I mentioned, because the audience would be predominately male, that the images and shapes should be attractive and relaxing to the eye, and begin with some females, then show people, including people of color working together on systems, laptops and with handheld devices.

Also I showed that the straight lines were too formal and tended to zoom the enduser's eyes right off the screen.

Then the interviewer showed me the next design, executed by two additional designers which surprise! surprise! surprise! - showed curved lines and a pleasant looking woman. It was "sexier" in the sense of appealing, and more relaxed.

Each time the interviewer showed me a new revision, I discussed what needed to happen - and I was correct each time - what an ego booster!I showed him some modern designs of a group of programmers and IT guys working in a friendly environment, but using futurist fonts, with a slightly Star Trek style design, that it was much more appealing to the audience they are designing the site for.

Speaking about flexible design (such as with CSS) and how to communicate process I showed him some designs that include process, and discussed how showing breadcrumbs and numbering processes is OK, it sets the enduser's expectation that it is a process, and how many steps to expect.

He also showed me some very bright red designs that covered the entire screen - I had to agree that it was more than a bit overwhelming. Color as used by a trained artist, who is also a colorist and understands the physiological and physical responses people have to strong color can be a useful tool, or it can fail to achieve useful goals if misused or misunderstood.

I discussed four primary design elements and strong design considerations for Web page design:
1. Who is your audience?
2. Where is the most useful real estate on a page and why is that vital?
3. What is the golden rectangle or golden mean and how is it used to direct the eye in refined designs?
4. How mammals, including human beings react to being presented with any screen or vista.

For me design is often spontaneous, it comes complete, or nearly complete in a flash of insight. Which is not to say that there are not going to be any changes. Often too I draw things on paper and evolve, consult with others, redesign, and rework until it is very close, and then do a final version which is submitted to be tested.

The UI testing, such as performed by information architect testers, often will uncover unexpected or unanticipated design flaws, which can be fixed and retested on an iterative basis.

In the case of working with Developers I found that they are readers pure and simple - if something is a huge red circle reading BUY ME HERE RIGHT NOW, they will skip it, and probably perceive it as an advertisement. But if it is in even a small font and reads, Buy name of product now then they will perceive it and click on that text.

This is exactly what the world's leading experts have been saying all along about design. For those interested in what is new in the field, considered checking out and subscribing to Dr.
Jakob Nielsen's http://www.useit.com/alertbox/ current issues in Web usability.

Microsoft is a great company that has a lot of wonderful technology at it's fingertips - getting things right with the human - computer interface and interaction is a bit more difficult.

Friday, February 04, 2005

Intuitive Understanding of Systems and Design - new word "urbanophile"

Well nothing as deadly to a blog as posting a poem, so much for being a rule breaker!

All the real bloggers' rules I am breaking - you know who, where and what I am because I have associated my writing with my business, or at least with my business resume. And because I want you to know. But blogging in a freestyle with energy may be more effective and fun if you don't know the author, and if the author doesn't let on who he or she is.

It's like putting your business sign on your car - it's fine if you are a careful and considerate driver, but if like to drive your sportscar fast and you cut someone off accidently or they take offence, it is your business that is represented on the road.

Reading the real bloggers you don't even know what gender they are (Say hello George Sands). The wild and woolly days of self expression on the information hiway are here, to stay. There are ways to control traffic and monitize these sources of information, but real writing by real people is out and loose in the world.

So why did I do it this way-- because as a creative it must be sort of well, restrictive? Yes, well fundamentally it is, one only has so much time to do things like write. But for the greater good as both a left and right brained person, I want to have the left brained ones be able to find me so they can make clever use of my right brain & left brain bridges to help build a better world.

The techies, the geeks, and nerds thought we had our brave new world in our hands - even some retired before the snakeoil salesmen took over what had been a grand fun time leading up to the high tech craze and crash of 2001. Nothing was as hollow as the white man's getto of Silicon Valley in 2000.

I even laughed off my "psychic friends" who warned me, prior to 1995, that things were going to hit the wall and turn ugly after about 2000 - they warned me that money would be more difficult to come by. Look at all this money I am making I thought! Hey I'll be able to buy a house, continue to travel and meet some of my nerdy interior goals. It doesn't even matter that I left millions of dollars worth of stock on the table at Microsoft in '93 and at RealNetworks in '96.

But my feeling that despite how much torture I had to endure in the linear thinking, instructional based, right brain repressive, non-expressive universe of the technical knowledgeworker, that some day it would be worth the trauma appears to be coming to fruition.

In the old days my heart hurt alot. After working in tech my personality changed significantly - I became kinder, truer, and gentler. I found that there is no where to hide and nothing to defend, because you are always with you. The wildchild was tamer, but rather than sensing immediate changes, continued to use my intuition to sense things as they might become - with some accuracy. I gave the first public speech at Microsoft on the advent of the Internet, asking the user education folks to store their files intended for printing instead of deleting them so we could distribute them in the future.

Being fundamentally (one could say 'terminally') creative is not something you erase by working with technology, but it is important to get along with people in the world. To me not just get along with them, by hopefully to teach by example, and encourage them on their mission in the world. It is not my job to change others, I found, only myself.

The tech industry now needs me to be a nexialist - a jack of all trades - a designer with an INTUITIVE urbanophile understanding of systems, software and design so we can more effectively combine it with meeting human needs.

We are very much in the early days of technology, and even if I and other can see clearly into the future, it is step by step that we meet that future creating it as it arises.

Yes, I still love Paul Simon's melodic ballads and Green Day's rants, En Vogue is major eye candy but who cares? I can't spell worth a darn because I still think words can be spelled all kinds of different ways. Sometimes I have to hear something twice to memorize it. I was made to feel terrible about that in a work review 15-20 years ago - "Some times Linda has to hear information twice". But then I was reading the life story of one of the world's great ancient pandits, and there it was, "Sometimes I have to hear something twice" What a relief! If the smartest man in the world admitted that sometimes he had to hear something twice, what hope is there for the rest of us?

People have their own problems, it does not one twit of good if we take it on ourselves.

NOTE: Torture is a word so uncommon to my use that I looked it up on the front page of CNN - some woman named Linda is happily married to some man named John and they love to torture kids in Florida by pulling out their toenails and beating them with a hammer - and people worry about Jackson - harm comes in all kinds of ways and affects people really differently. I could not spell torture well enough to find it via Dictionary.com - technology is for me not against me - at least I can spell it.