The following checklist identifies core principles and best practices to assist software designers and developers to produce software that stands out in the marketplace.

1. Concepts from the product’s subject domain (for example, systems management) should be central and apparent in the software design – The relationships among user interface objects in products should be accurate, so that users can rely on their previous experience in the domain when learning and using the software.
2. Keep it simple – Give easy access to the features that most users will need most of the time; features used less often or by only a subset of users are placed less prominently.
3. Optimise the design for the most frequent or important tasks – Understanding how users will use the software you are designing is critically important. Designers should use that understanding to anticipate the information, task flows, and features that users require at key points within the user experience.
4. Make the interface accessible and visible to users – Design your Web site or application so that users can view and easily access objects or information within the interface. Choices should be visible to users rather than hidden with cryptic key sequences. When objects and choices are immediately visible, users learn and complete work tasks efficiently.
5. Use proper default values when supporting complex tasks – Use good defaults so that users can complete tasks relatively easily and quickly rather overwhelming them with choices.
6. Be flexible – Let users customise the application to meet their unique needs. For example, specialised users could be given a way to make secondary choices more prominent in the product. Also, don’t limit users by artificially restricting their choices to a “correct” sequence. Flexibility is also enhanced by letting users select options in various sequences and in letting them modify default values.
7. Keep your users informed and in control by providing informative and timely feedback tailored to the current situation – For example, progress indicators let users know that their system is healthy and is carrying out their request. At a minimum, alert users when they take actions that will result in the loss of data. (Ideally, such choices would be disabled or even eliminated when they are inappropriate in a particular situation.) All the information included in the feedback should be meaningful to the average user.
8. Things that look the same should behave in the same way, and an action should always produce the same result – Avoid modes that change the effects of actions. Where modes are unavoidable, make them clear to the user and easy to change.
9. Provide the ability to undo and redo actions – Applications must provide users with the ability to freely explore applications (which includes the ability to make mistakes) without fearing permanent damage.
10. Make your application predictable by using industry standard user interface conventions wherever possible – For example, users should be able to use standard selection models and keyboard equivalents like Ctrl+C and Shift+→ (to copy the currently selected object and extend the current selection one unit to the right, respectively) everywhere they work with data. Use a common set of design patterns and guidelines so that users don’t have to relearn how to perform common tasks.
11. Always keep your target users in mind as the product is designed – Developing personas and identifying and defining the roles your users fulfil can help you understand how various roles will use your product. Designs based on typical workflows and the other software that users might use in conjunction with yours will delight users.
12. Avoid adding features just so they can be ticked off a list – Remember that every additional feature equals a set of choices added to what is likely already a wide array of choices. Too many choices can overwhelm users.
13. Design your user interface so that it can be localised for other geographies without redesigning the interface – For example, don’t crowd form controls too tightly so they can accommodate longer German translations.
14. Consider persons with disabilities when designing your applications – Many users of your product may have impaired vision or physical limitations that affect their ability to use a mouse or a joystick.
15. Design the application so that contextual help is available to users when they need it – Users should not have to refer to Help constantly to complete their tasks.
16. Bring objects to life through good visual design – The goal of visual design in the user interface is to surface to the user in a cohesive manner all aspects of the design principles. Visual design should support the user model and communicate the function of that model without ambiguities. Visual design should not be the “icing on the cake” but rather an integral part of the design process. The final result should be an intuitive and familiar representation that is second nature to users.
17. Create user interfaces that promote clarity and visual simplicity – The following visual design principles help create that effect:
    • Subtractive design – Reduce clutter by eliminating any visual element that doesn’t contribute directly to visual communication.
    • Visual hierarchy – Understand the importance of users’ tasks and establish a visual hierarchy of these tasks. An important object can be given visual prominence. Relative position and contrast in colour and size can be used to convey task importance.
    • Affordance – When users can easily determine the action that should be taken with an object, that object displays good affordance. Objects with good affordance usually mimic actual objects.
    • Visual scheme – Design a visual scheme that maps to the user model and lets the user customise the interface. Do not eliminate extra space in your image just to save space. Use white space to provide visual “breathing room.”

Inclusive design is where innovation and imagination flourish. Meeting the needs of the widest variety of people does not inhibit creativity. It opens our minds and inspires excellence.

In her article in .net magazine, Sandi Wassmer of Copious explains the ten principles for inclusive web design an overview of which is listed below:

1. Equitable – Be welcoming, don’t discriminate and engage with people. Create different user experiences and make certain they have equally valuable outcomes. Aesthetics matter.
2. Flexible – Provide options. Think who, how, why, what, where and when people will be using your website. Make sure there is choice for diverse users and maintain device independence.
3. Straightforward – Be obvious and not ambiguous. Make sure your website’s features add value, not complexity. Remember, good design is as little design as possible.
4. Perceptible – Don’t assume anything. Make sure your website’s purpose is clear, its content, structure and sequence are meaningful and convey information to all of the senses.
5. Informative – Make sure people know where they are on your website and provide ways for them to find what they’re looking for. Be timely, predictable, uncomplicated and precise.
6. Preventative – Provide easy to follow instructions and gently guide users in interacting with your website. Help them to minimise errors when submitting data, through well considered form design.
7. Tolerant – Handle errors respectfully and indicate precisely what the error is, where it is and how to fix it. Remember to let people know the outcome.
8. Effortless – Don’t make demands or place restrictions on your users. People should not have to work or think hard to find what they want on your website. Ensure it can be used efficiently and effectively.
9. Accommodating – Be approachable, uncluttered and give people room to manoeuvre. Make sure that your website is unobtrusive and can be accessed by different devices of all shapes and sizes.
10. Consistent – Follow standards, guidelines, conventions and best practices. Provide a familiar environment with memorable functionality.

With different devices, configurations, browsers, personal settings and assistive technologies, and no agreement on how to achieve interoperability, web builders must do their best to accommodate the diverse ways people access the internet. Building with this in mind will ensure your visitors have a quality experience.

Inclusive design enables us to create great, meaningful, on-brand internet experiences for the widest audience possible. However, inclusive design is also a new way of thinking, and its overarching aims may not mirror those of your organisation or clients. Change takes time, so you may not be able to do everything at once. If you just start thinking about accessibility and plan your projects with users in mind, you’ll be on the right path. There will be trade-offs and tough decisions, but this is where inclusive design really comes to the fore. It challenges us to hone our craft and fosters real creativity and innovation.

In her The Dimensions of a Good Experience presentation at An Event Apart in Seattle, 2011, Andrzejewski shared ten principles from urban design that provide unique lenses for evaluating and thinking about mobile and Web user experience designs.

Luke Wroblewski provides a handy overview from the talk; my take on his overview is summarised below:

1. Sense of Meaning — Does the design tell a story? How is the form a reflection of its values? Can people read and understand the environment? Visual cues in the environment can communicate meaning. For example, there’s a lot of meaning in the way that Japanese signs are structured. This enables you to read the environment. What story are we trying to tell in our information architecture (IA) through its structural design?
2. Sense of Place — Does the design leave a lasting impression on the user’s senses? Is it memorable [in a good way]? Focus on those key moments. What should they remember? What story do you want to tell the user and how can you use the language of design to reinforce that story? Show a user a home page that’s unfamiliar to them and ask if they understand the value of the product or service. How well are you communicating?
3. Sense of Structure — Does the design afford the user a sense of structure? Can they understand that structure? Can the user create an accurate mental model of what they’re looking at? When things fit together, a user will feel comfortable and in control.
4. Sense of Unfolding — Does the design get better the more a user explores? Are they ‘delighted’ by the what’s unfolding before them? Is the first time experience tempered so as not to be overwhelming? How can you get the user to leave wanting more?
5. Sense of Transparency — Does the design give a glimmer of what’s inside? This is not absolute as different groups demand different levels of transparency.
6. Sense of Fit — Does the design anticipate and facilitate the desired needs of the user so that it makes them feel positive? Observe the user throughout the site. Find the drop-off points and fix them. Ask the users questions.
7. Sense of Adaptability — Does the design afford the user the ability to adapt their surroundings to reach a more comfortable fit? Again, observe your users and learn from their adaptations.
8. Sense of Access — Does the design provide a range of choices to the user? How much and what range of choices are presented to a user at any given time? Is it too many or too few? Carry out some A/B tests to find out.
9. Sense of Responsibility — Does the design engender a sense of community, ownership and responsibility with/to your users? Holding people accountable will encourage good behaviour. How can you increase your users’ sense of responsibility to the community or website you’re trying to build?
10. Sense of Certainty — Does the design promote trust? What are the systems of control? Do these reinforce trust? Does your website behave in predictable ways? This is particularly important if your users aren’t actually in control. Examine what makes your users anxious and mitigate against those anxieties. Make your users feel confident.

You need to examine the user experience you’re creating through each of the lenses above. By doing so you will improve the experience for all your users.

1. Strive for consistency — Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
2. Enable frequent users to use shortcuts — As the frequency of use increases, so do the user’s desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
3. Offer informative feedback — For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
4. Design dialog to yield closure — Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
5. Offer simple error handling — As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
6. Permit easy reversal of actions — This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
7. Support internal locus of control — Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
8. Reduce short-term memory load — The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.

Further reading:

• Designing the User Interface: Strategies for Effective Human-Computer Interaction

Details of the current seminar series can be found on Stanford HCI website, whilst the 2009 seminar series can be found on iTunes U. The topics of which are listed below:

Winter 2009

1. Pario: The Next Step Beyond Audio and Video
2. Sculpting Behaviour: Developing a Tangible Lnguage for Hands-on Play and Learning
3. Tap is the New Click
4. Social Annotation, Contextual Collaboration and Online Transparency
5. Enlightened Trial and Error – Gaining design Insight Through Prototyping Tools
6. Computer Graphics as a Telecommunication Medium
7. Not Invented Here: Online Mapping Revealed

Spring 2009

1. Firefox, Mozilla & Open Source: Software Design at Scale
2. Social Enterprise Software Design
3. The Interaction Design of APIs
4. Far Away Up Close
5. What Still Matters About Distance?
6. How We Use Data to Win the Presidential Election
7. Social Immersive Media
8. Launching Creative Communities: Lessons From the Spore Community
9. Designing Online Communities from Theory

Autumn/Fall 2009

1. Crowdsourcing Work
2. Backtracking Events as Indicators of Software Usability Problems
3. Programming by Sketching
4. Aesthetic Science of Colour: WAVEs of Colour, Culture, Music and Emotion

Previous talks are also available on iTunes U — with the notable speakers Bill Moggridge, Bill Buxton and Donald Norman featuring — or on YouTube: 2006-07, 2007-08, 2008-09

The following are free-to-read books on user experience, available online:

Human Computer Interaction

• Mental Models in Human-Computer Interaction: Research Issues About What the User of Software Knows by John M. Carroll and Judith Reitman Olson
• HCI Models, Theories and Frameworks: Toward a Multi-disciplinary Science by John M. Carroll

User Experience / Interaction Design

• Search User Interfaces by Marti A. Hearst
• Designing Interfaces – Patterns for Effective Interaction Design by Jenifer Tidwell
• Thoughts on Interaction Design by Jon Kolko. with contributions from Ellen Beldner, Uday Gajendar, Chris Connors and Justin Petro
• The Fable of the User-Centered Designer by David Travis

Web Accessibility

• Just Ask: Integrating Accessibility Throughout Design by Shawn Henry
• Building Accessible Websites by Joe Clarke
• Dive Into Accessibility: 30 Days to a More Accessible Website by Mark Pilgrim

If there are any more you think need or can be added to the list, please leave a comment.

How does Rams’ define good design?

1. Good design should be innovative — It does not copy existing product forms, nor does it produce any kind of novelty just for the sake of it. The essence of innovation must clearly be seen in all of a product’s functions. Current technological development keeps offering new chances for innovative solutions.
2. Good design should make a product useful — The product is bought in order to be used. It must serve a defined purpose, in both primary and additional functions. The most important task of design is to optimise the utility of a product’s usability.
3. Good design is aesthetic design — The aesthetic quality of a product is integral to its usefulness because products we use every day affect our well-being. But only well-executed objects can be beautiful.
4. Good design will make a product understandable — It clarifies the product’s structure. Better still, it can make the product talk. At best, it is self-explanatory.
5. Good design is honest — It does not make a product more innovative, powerful or valuable than it really is. It does not attempt to manipulate the consumer with promises that cannot be kept.
6. Good design is unobtrusive — Products fulfilling a purpose are like tools. They are neither decorative objects nor works of art. Their design should therefore be both neutral and restrained, to leave room for the user’s self-expression.
7. Good design is long lived — It does not follow trends that become out-dated after a short time. Well designed products differ significantly from short-lived, trivial products in today’s throwaway world.
8. Good design is consistent in every detail — Nothing must be arbitrary. Thoroughness and accuracy in the design process shows respect towards the user.
9. Good design should be environmentally friendly — Design must make contributions towards a stable environment and sensible raw material situation. This does not only include actual pollution, but also visual pollution and destruction of our environment.
10. Good design is as little design as possible — Less is more – because it concentrates on the essential aspects and the products are not burdened with non-essentials. Back to purity, back to simplicity.

Many people say it is obvious that Rams’ designs have been influential on Jonathan Ive of Apple, designer of such products as the iMac, iPod, and iPhone, as can be witnessed particularly in the iPhone’s calculator application, whose design is based on the Braun ET66 calculator designed by Rams.

More

The Design Museum in London are holding a Dieter Rams’ exhibition between 19th November 2009 and 9th March 2010. The exhibition will showcase Rams’ landmark designs for Braun and furniture manufacturer Vitsœ, examine how Rams’ design ethos inspired Braun’s entire product range for over 40 years, and assess his lasting influence on today’s design landscape.

1. Visibility of system status — The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
2. Match between system and the real world — The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
3. User control and freedom — Users often choose system functions by mistake and will need a clearly marked emergency exit to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
4. Consistency and standards — Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
5. Error prevention — Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
6. Recognition rather than recall — Minimise the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
7. Flexibility and efficiency of use — Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
8. Aesthetic and minimalist design — Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
9. Help users recognise, diagnose, and recover from errors — Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
10. Help and documentation — Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.

References

• http://www.useit.com/papers/heuristic/heuristic_list.html
• Nielsen, J. (1994b). Heuristic evaluation. In Nielsen, J., and Mack, R.L. (Eds.), Usability Inspection Methods, John Wiley & Sons, New York, NY.

Human-Centered Design (HCD) is a process used for decades to create new solutions for companies and organisations. HCD can help you enhance the lives of people. This process has been specially-adapted for organisations like that work with people in Africa, Asia, and Latin America. HCD will help you hear people’s needs in new ways, create innovative solutions to meet these needs, and deliver solutions with financial sustainability in mind.

The Toolkit is divided into four sections that can be downloaded individually or together:

1. The Introduction will give an overview of HCD and help you understand how it might be used alongside other methods.
2. The Hear guide will help your design team prepare for fieldwork and understand how to collect stories that will serve as insight and inspiration. Designing meaningful and innovative solutions that serve your customers begins with gaining deep empathy for their needs, hopes and aspirations for the future. The Hear booklet will equip the team with methodologies and tips for engaging people in their own contexts to delve beneath the surface.
3. The Field Guide and Aspirations Cards are a complement to the Hear guide; these are the tools your team will take with them in order to conduct research.
4. The Create guide will help your team work together in a workshop format to translate what you heard from people into frameworks, opportunities, solutions, and prototypes. During this phase, you will move from concrete to more abstract thinking in identifying themes and opportunities and back to the concrete with solutions and prototypes.
5. The Deliver guide will help catapult the top ideas you have created toward implementation. The realisation of solution includes rapid revenue and cost modeling, capability assessment, and implementation panning. The activities offered in this phase are meant to complement your organisation’s existing implementation processes and may prompt adaptations to the way solutions are typically rolled out.

Download the complete toolkit (PDF, 30.5MB)

The list is still as relevant today as it was back in 1997.

1. Know thy user, and YOU are not thy user.
2. Things that look the same should act the same.
3. Everyone makes mistakes, so every mistake should be fixable.
4. The information for the decision needs to be there when the decision is needed.
5. Error messages should actually mean something to the user, and tell the user how to fix the problem.
6. Every action should have a reaction.
7. Don’t overload the user’s buffers.
8. Consistency, consistency, consistency.
9. Minimize the need for a mighty memory.
10. Keep it simple.
11. The more you do something, the easier it should be to do.
12. The user should always know what is happening.
13. The user should control the system. The system shouldn’t control the user. The user is the boss, and the system should show it.
14. The idea is to empower the user, not speed up the system.
15. Eliminate unnecessary decisions, and illuminate the rest.
16. If I made an error, let me know about it before I get into REAL trouble.
17. The best journey is the one with the fewest steps. Shorten the distance between the user and their goal.
18. The user should be able to do what the user wants to do.
19. Things that look different should act different.
20. You should always know how to find out what to do next.
21. Don’t let people accidentally shoot themselves.
22. Even experts are novices at some point. Provide help.
23. Design for regular people and the real world.
24. Keep it neat. Keep it organized.
25. Provide a way to bail out and start over.
26. The fault is not in thyself, but in thy system.
27. If it is not needed, it’s not needed.
28. Color is information.
29. Everything in its place, and a place for everything.
30. The user should be in a good mood when done.
31. If I made an error, at least let me finish my thought before I have to fix it.
32. Cute is not a good adjective for systems.
33. Let people shape the system to themselves, and paint it with their own personality.
34. To know the system is to love it.

References

1. Lund, A. M. (1997). Expert ratings of usability maxims. Ergonomics in Design, 5(3), 15-20. A study of the heuristics design experts consider important for good design.