Michael Gaigg: Über UI/UX Design


Download: User-centered Design Menu

Posted by Michael Gaigg

User-centered Design Menu

User-centered Design Menu

Welcome back!

This time I literally have a special treat for you: the User-centered Design (UCD) menu. It's like a menu that your clients can choose from and range from inexpensive ($) to rather expensive ($$$$).

Tip: Please digest slowly and most importantly: ENJOY!

Download: UCD Menu (PDF)


Every Proposal is the entrance to something great.

Paper Prototyping $$

Hand-drafted mockups and sketches, carefully selected and laid out, sautéed with your ideas.

UX Storyboarding $

A portion of your end-users and their needs
topped with their stories and actual problems.

Heuristic Evaluation $

Draft designs, wireframes or fully implemented systems
evaluated by a choice of 2-3 hand-picked experts.

Survey $

Freshly picked set of questions, sliced to identify
your users and their needs, served with lots of insights.

Main Courses

Let us delight your users with our house specialties.

Rapid Prototyping $$$

Lightly functional demos or prototypes,
served in high or low fidelity, grilled to perfection.

Usability Testing $$$

Home-made end-user observations that feed
right into the next design iteration, served by 3-5 users.

Focus Group $$$

Choice of nutritional opinions and beliefs,
shared and discussed by a group of people.

Field Study $$$$

Real end-user behavior observations collected by
following people in their daily job and environment.

Card Sorting $$$

Delicious index cards sprinkled with individual
concepts, tossed into meaningful piles, served hot.

Server Log & Search Log Analysis $$

Crisp log statistics piled high with insights of
user’s navigation and search behavior. Very tasty!

Chef’s recommendation:

Make the User a stakeholder!
Involving the user early and throughout the cooking process will improve the experience and usability of your app and save you and your client money.

18% gratuity added to projects of 250k or more.

Please ask your server for the recommended selection of user-centered design methods that suits your project.


Save the Users [Video]

Posted by Michael Gaigg

1000's of designers are standing by to assist you... LOL

Thanks to Frank for pointing me to this video link.

Tagged as: , No Comments

Highlights of Week 39/2010

Posted by Michael Gaigg


Highlights of Week 36/2010

Posted by Michael Gaigg


Esri listens to their Users and changes Pronunciation of its Name

Posted by Michael Gaigg

Esri Emblem

Esri Emblem

This is big!


And here is why: ESRI, a privately held company with more than 2700 employees, was founded in 1969, over 40 years ago. The company name is an abbreviation for Environmental Systems Research Institute and therefore

not pronounced as a word but as distinct letters similar to IBM, SAP and other software companies with an acronym based name. It is thought within the GIS (Geographical Information Systems) circles, and even joked that 'old' users prefer E-S-R-I, while novice users use the 'ez-ree' pronunciation.

(from wikipedia, March 2010, which has its own section called "Pronunciation of company name").

Insides and Myths

Over time a divide elapsed, employees were proud to pronounce their company name E-S-R-I and by doing so showing they are insiders and distinguishing themselves from the 'newbies'. It became part of company culture and identity.

Rumor has it that the first week of orientation for new employees is to train them to say "E - S - R - I" spelled out instead of trying to pronounce it as a word (ez-ree), though I cannot personally confirm this. There's also been a rumor of Jack Dangermond [the presiding of ESRI] having a version of the "swear jar" on his desk, and anytime someone says "ez-ree" they have to put a dollar in.


Around the world users were confused. While it seemed to be natural to pronounce the company name ez-ree, users found themselves being corrected and lectured: "It's not ez-ree, it's E-S-R-I". Hearing "It hurts me to say "ezree". =)" from employees were not uncommon.

Forum threads tried to shed light on the ongoing discussion and various sides were quick to elaborate about the correct pronunciation in (mostly humorous) detail, e.g.

  • Here in San Antonio, my new home, it is pronounced "ess-ray y'all".
  • In austria we say: äsri
  • When I'm in a hurry- I say 'eS-ree', and when I'm trying to sound sophisticated and smart I say 'E-S-R-I'. Isn't that the way it always works?
  • As for ESRI or esree I have always called it EE ESS ARE EYE.
  • Lately I've noticed that people, who aren't sure of what they are talking about, pronouce it 'Uhh, [pause] Ezree' or '[PAUSE] Eszree'. The pause before gives it away...
  • Canadian pronunciation: ez-ree-eh?, or ee-ess-arr-eye-eh?
  • One thing I've noticed, though, is that the tendency to elide sounds has some people pronouncing E-S-R-I rather like yes-are-eye (without the y). Will the next step in this evolution be yes-rye? (Then the only question will be Do you want that with mustard?)
  • Down Under we say 'Bloody ezree' when things go ferral.

Change and Resistance

To the surprise of many employees an internal notice from 3/19/2010 read:

[...] we will be transitioning the pronunciation of ESRI to “ezree.” This effort will ensure a consistent name recognition around the world.

What followed was a big uproar from the employees side. Many of us felt robbed of our identity and culture. What seemed to work well for over 40 years should not be changed and trashed that easily!


As it turned out, after merrily 4 months and a hugely successful User Conference with almost 14.000 people (the biggest gathering of GIS professionals ever) the name change was perceived as a relief by the user community. A sense of unity was felt, finally we speak the same language, the confusion was lifted, no more lecturing, no more division between insiders and outsiders, everybody became part of the family.

Esri stepped into icy waters and in risk of p***ing some of its own employees off it opened a new world of opportunities by Speaking the Language of Its Users - I'm loving it!!

What do you think?

Have you ever heard of a comparable change / step taken? Could you imaging IBM spelled Ei-bm?


Benefits & Principles of User-Centered Design

Posted by Michael Gaigg

We, the people, have been around for quite some years now. Computers, software, applications and the web not so much. Therefore it is clear that applications have to adjust to the people and not the other way round.

Many design principles have developed throughout the decades, but the main difference of user-centered design to others is that

UCD tries to optimize the user interface around how people can, want, or need to work, rather than forcing the users to change how they work to accommodate the system or function.

Purpose of UCD

UCD answers questions about users and their tasks and goals, then use the findings to make decisions about development and design.

UCD seeks to answer the following questions:

  • Who are the users of the application?
  • What are the users’ main tasks and goals?
  • What are the users’ experience levels with the application?
  • What functions do the users need from the application?
  • What information might the users need, and in what form do they need it?
  • How do users think the application should work?

Benefits & Return of Investment

  • Increased usability
    • Higher degree of customer satisfaction
    • Continued business
    • Higher revenues
  • Project management optimization
    • Focus on important functionality early
    • Unforeseen user requirements
  • Reduced costs
    • Training costs
    • Help-Desk calls and service costs

UCD Principles

  • Focus on users’ needs, tasks and goals
  • Spend time on initial research and requirements
    • Identify your target audience and observe them (accomplishing their tasks)
    • Let users define product requirements
  • Emphasis on iterative design process
  • Evaluate system on real target users


Nobody could state it simpler than Susan Dray: "If the user can’t use it, it doesn’t work".


What is Accessibility?

Posted by Michael Gaigg

The purpose of web pages is to interactively display information. The Hypertext Markup Language was designed to encode meaning rather than appearance. Therefore

Accessibility is the extent of access to information on a webpage through user agents (e.g. browsers, screen readers,…) which translate HTML into hypertext structures (links, headers, tables, forms,…) in order to give the users a surplus value.

“As long as a page is coded for meaning, it is possible for alternative browsers to present that meaning in ways that are optimized for the abilities of individual users and thus facilitate the use of the Web by disabled users. Those disabilities are:

  • Visual Disabilities
  • Auditory Disabilities
  • Motor Disabilities
  • Cognitive Disabilities” [NIELSEN96]

Since Web pages are highly visual and interactive the most affected groups as far as accessibility is concerned are the visual disabled, i.e. blind users or users with other visual disabilities like color blindness and users with motor disabilities using alternative input devices or sometimes even just the keyboard instead of the mouse.

Everybody benefits!

In the same way a sidewalk curb is necessary for wheelchair accessibility it also benefits parents with strollers, children with rollerblades and elderly persons trying to cross the street. The same is true for web pages. Designing for accessiblity will not only benefit users with disabilities but will also increase your:

  • Market Share Benefits
    • SEO (search engine optimization)
    • Repurpose
    • Literacy
    • Bandwidth
  • Technical Efficiency Benefits
    • Maintenance
    • Server Bandwidth