Hipnotiza a tus amigos

La página http://ajaxload.info/ permite crear fácilmente pequeños gráficos de progreso en varios estilos.

Test your users!

AskTog on interaction designers:

If they don't test, don't hire them!

How to write a report

Tog de askTog.com escribe sobre cómo escribir un informe de evaluación heurística, sin ofender al destinatario.

Haiku error mesages

Salon posts a nice
challenge: writing some error
messages in Haiku.

Cómo crear una sesión de test de usuario

Creating usability test tasks that really motivate users

The magic of usability tests is that you get to see what people actually do with a system (rather than what they say they do). This gives you great insights into how people behave and how to improve your design. But if your tasks lack realism you’ll find that people just go through the motions and don’t engage with the test — reducing the credibility of your results. Here are 6 ways to captivate participants with great test tasks

HCI social Design patterns

Design patterns for social sites:
http://designingsocialinterfaces.com/patterns/Main_Page


A good example of user badges:
http://stackoverflow.com/badges

A rating algorithm for popularity in forums:
http://www.vbulletin.org/forum/showthread.php?t=199556

Good names for faceted search

Microsoft gives some advice on creating good names for facets in a faceted search - in the context of its new pivotviewer control.

Facet Naming

In general, you want concise and clear names for facets and facet categories that don’t get truncated in common usage. Below are some guidelines:

• Capitalization – Facet categories should follow headline/title style conventions for capitalization. Facet values are case-sensitive, so make sure the values use consistent casing throughout.
• Plurality - Use the singular form of the category name. For example: Rather than naming a category "Countries," use "Country."
• Brevity and Redundancy - Use as few words as possible to name categories. Keep in mind that the user is already browsing within the context of your collection, so any concepts or words which inherently make sense in that context can be taken as implied. For example: in a collection named "Major League Soccer Players," a facet named "Player Position" could be shortened to "Position." A facet named "Average Points Scored per Game" could be "Average Points / Game," or simply "Average Points." Finally, use the active voice to avoid unnecessarily long phrases.
• Acronyms - While they help with brevity, acronyms may add confusion. Avoid them where possible, unless you know that the target audience will be inherently familiar with them. Try using abbreviations instead.
• Numbers - Use Arabic numerals ("1, 2, 3") rather than spelling them out ("one, two, three"). They’re shorter and easier to read quickly.
• String vs. LongString - LongString is a special type only used for info panel content to be wrapped onto multiple lines. LongString should be used for any text longer than a few words.
• Sorting Behavior - Sorting and grouping is strictly alphabetical. That means that when values starting with "The" appear in PivotViewer, they will be grouped with the T’s.