Difference between revisions of "HowTo Request User Experience Assistance"
Lutz Hoeger (Talk | contribs) m |
Lutz Hoeger (Talk | contribs) m |
||
| Line 6: | Line 6: | ||
= Why work with User Experience? = | = Why work with User Experience? = | ||
| − | User experience (UX) engineering '''advocates the user perspective''' by providing insights to the user’s mental model. Within the development process, UX can take on a variety of tasks, from '''UX design''' (interaction, UI, graphic design, layout, terminology), through '''usability evaluations''' (requirements engineering, competitive analysis, heuristic evaluations, usability studies), up to '''HCI research''' (HCI know-how, | + | User experience (UX) engineering '''advocates the user perspective''' by providing insights to the user’s mental model. Within the development process, UX can take on a variety of tasks, from '''UX design''' (interaction, user interface (UI), graphic design, layout, terminology), through '''usability evaluations''' (requirements engineering, competitive analysis, heuristic evaluations, usability studies), up to '''HCI research''' (HCI know-how, UI style guides, usability metrics). |
= When '''''do''''' you need UX? = | = When '''''do''''' you need UX? = | ||
| − | Some changes have a high impact on users. We strongly advise you to include UX into the development of such features or issue fixes. Here are some general examples for these features: | + | Some changes have a '''high impact on users'''. We strongly advise you to include UX into the development of such features or issue fixes. Here are some general examples for these features: |
| − | * Changes to the "first impression" part of the | + | * Changes to the '''"first impression" part of the UI''' (overall appearance, main menu, tool bars, standard shortcuts) |
| − | * Work flow changes (introducing new work flow steps, dialog boxes, error messages, streamlining the work flow) | + | * '''Work flow''' changes (introducing new work flow steps, dialog boxes, error messages, streamlining the work flow) |
| − | * Changing default settings, in particular if | + | * Changing '''default settings''', in particular if this affects one of the two above |
= When do you '''''not''''' need UX? = | = When do you '''''not''''' need UX? = | ||
| − | Changing the UI does not necessarily mean that UX engineering needs to be included. For changes that have lower impact on | + | Changing the UI does not necessarily mean that UX engineering needs to be included. For changes that have '''lower impact on users''', you can often apply common HCI guidelines by yourself. Here are a few examples for changes, where you do not need to include UX engineering: |
| − | * Changes to "well hidden" parts of the UI, like the "more"-part of a rarely used dialog. | + | * Changes to '''"well hidden" parts of the UI''', like the "more"-part of a rarely used dialog. |
| − | * Changes that have already been designed (or sketched out well) in a related specification document. | + | * Changes that have '''already been designed''' (or sketched out well) in a related specification document. |
| − | * | + | * Changes for which you '''know how to apply [[User_Interface_Guidelines|HCI or UI design guidelines]]''' on your own. |
= How to contact UX / how to request assistance = | = How to contact UX / how to request assistance = | ||
| + | There probably never are as many UX engineers as there are development engineers, so we need to dispatch UX requests efficiently. The good news is, that all tools are in place, and most people in the OOo community are used to use them. | ||
| − | + | '''When you need UX assistance''', or even when you want to know, if you need UX assistance, | |
| + | '''send an e-mail to mailto:issues@ux.openoffice.org'''. | ||
= What UX needs from you = | = What UX needs from you = | ||
| − | * | + | Your e-mail needs to include at minimum: |
| − | ** | + | * The '''issue ID''' of the issue you are working on. |
| − | * | + | *: The easiest way to do this, is to add the e-mail address to the cc: list of your issue. |
| − | + | If your request originates from an issue filed in OOo Issue Tracker, the following information should be included into the issue description. If there is no issue yet, include it into your e-mail. | |
| − | + | * Brief description of '''what''' you want to change / what your patch changes, | |
| + | * Very short statement '''why''' you (want to) change this, | ||
| + | * If your change affects the UI, ideally provide a '''mock up''' - if you actually provide a patch that affects the UI, instead, include a '''screen shot''' of your patch in action, | ||
| + | and, last but not least: | ||
| + | * '''Clearly state which action you request from UX.''' | ||
| + | Additionally - but this is entirely optional - you may provide a URL to an install set (preferably Windows, but Linux/MacOSX/Solaris works, too) where one could evaluate your patch in action. | ||
= What can you expect from UX? = | = What can you expect from UX? = | ||
| + | |||
** initial response within one week | ** initial response within one week | ||
** a name / OOo issuetracker ID of a UX engineer to assign the issue to | ** a name / OOo issuetracker ID of a UX engineer to assign the issue to | ||
** alternatively, the answer may be "no resources, go with your best guess" | ** alternatively, the answer may be "no resources, go with your best guess" | ||
** if you don't hear anything from UX within two weeks, just proceed | ** if you don't hear anything from UX within two weeks, just proceed | ||
Revision as of 15:49, 14 June 2007
|
|
|---|
|
Quick Navigation Team Communication Activities |
DISCLAIMER: This is an initial draft of a general guidance on how developers shall work with UX. Please feel free to comment on it, suggest changes, or ask questions about it at any time. As soon as a first stable version emerges, I will announce this on more public channels.
Thanks, --Lutz Hoeger 13:30, 14 June 2007 (CEST)
Contents
Why work with User Experience?
User experience (UX) engineering advocates the user perspective by providing insights to the user’s mental model. Within the development process, UX can take on a variety of tasks, from UX design (interaction, user interface (UI), graphic design, layout, terminology), through usability evaluations (requirements engineering, competitive analysis, heuristic evaluations, usability studies), up to HCI research (HCI know-how, UI style guides, usability metrics).
When do you need UX?
Some changes have a high impact on users. We strongly advise you to include UX into the development of such features or issue fixes. Here are some general examples for these features:
- Changes to the "first impression" part of the UI (overall appearance, main menu, tool bars, standard shortcuts)
- Work flow changes (introducing new work flow steps, dialog boxes, error messages, streamlining the work flow)
- Changing default settings, in particular if this affects one of the two above
When do you not need UX?
Changing the UI does not necessarily mean that UX engineering needs to be included. For changes that have lower impact on users, you can often apply common HCI guidelines by yourself. Here are a few examples for changes, where you do not need to include UX engineering:
- Changes to "well hidden" parts of the UI, like the "more"-part of a rarely used dialog.
- Changes that have already been designed (or sketched out well) in a related specification document.
- Changes for which you know how to apply HCI or UI design guidelines on your own.
How to contact UX / how to request assistance
There probably never are as many UX engineers as there are development engineers, so we need to dispatch UX requests efficiently. The good news is, that all tools are in place, and most people in the OOo community are used to use them.
When you need UX assistance, or even when you want to know, if you need UX assistance,
send an e-mail to mailto:issues@ux.openoffice.org.
What UX needs from you
Your e-mail needs to include at minimum:
- The issue ID of the issue you are working on.
- The easiest way to do this, is to add the e-mail address to the cc: list of your issue.
If your request originates from an issue filed in OOo Issue Tracker, the following information should be included into the issue description. If there is no issue yet, include it into your e-mail.
- Brief description of what you want to change / what your patch changes,
- Very short statement why you (want to) change this,
- If your change affects the UI, ideally provide a mock up - if you actually provide a patch that affects the UI, instead, include a screen shot of your patch in action,
and, last but not least:
- Clearly state which action you request from UX.
Additionally - but this is entirely optional - you may provide a URL to an install set (preferably Windows, but Linux/MacOSX/Solaris works, too) where one could evaluate your patch in action.
What can you expect from UX?
- initial response within one week
- a name / OOo issuetracker ID of a UX engineer to assign the issue to
- alternatively, the answer may be "no resources, go with your best guess"
- if you don't hear anything from UX within two weeks, just proceed
