Difference between revisions of "HowTo Request User Experience Assistance"
From Apache OpenOffice Wiki
Lutz Hoeger (Talk | contribs) m |
Lutz Hoeger (Talk | contribs) m |
||
| Line 8: | Line 8: | ||
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, GUI style guides, usability metrics). | 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, GUI style guides, usability metrics). | ||
| − | + | = When '''''do''''' you need UX? = | |
** High-impact features or issues, e.g. ... | ** High-impact features or issues, e.g. ... | ||
*** ...changes to the "initial" user interface (e.g. main menu, tool bars, shortcuts), | *** ...changes to the "initial" user interface (e.g. main menu, tool bars, shortcuts), | ||
| Line 15: | Line 15: | ||
| − | + | = When do you '''''not''''' need UX? = | |
** Guideline available | ** Guideline available | ||
*** [[User_Interface_Guidelines|OOo UI guidelines & specs]] | *** [[User_Interface_Guidelines|OOo UI guidelines & specs]] | ||
| Line 23: | Line 23: | ||
| − | + | = How to contact UX / how to request assistance = | |
** send an e-mail to mailto:discuss@ux.openoffice.org (later to be changed into mailto: issues @ ux.openffice.org) | ** send an e-mail to mailto:discuss@ux.openoffice.org (later to be changed into mailto: issues @ ux.openffice.org) | ||
| − | + | = What UX needs from you = | |
** issue ID | ** issue ID | ||
** short description of the change & why you changed it | ** short description of the change & why you changed it | ||
| Line 34: | Line 34: | ||
| − | + | = 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 14:38, 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, UI, graphic design, layout, terminology), through usability evaluations (requirements engineering, competitive analysis, heuristic evaluations, usability studies), up to HCI research (HCI know-how, GUI style guides, usability metrics).
When do you need UX?
- High-impact features or issues, e.g. ...
- ...changes to the "initial" user interface (e.g. main menu, tool bars, shortcuts),
- ...work flow changes (e.g. introducing new work flow steps, dialog boxes, error messages),
- ...changing default settings affecting either of the two above
- High-impact features or issues, e.g. ...
When do you not need UX?
- Guideline available
- Lower-impact features or issues, e.g. ...
- ...changes to "well hidden" parts of the UI, like the "more"-part of a rarely used dialog
How to contact UX / how to request assistance
- send an e-mail to mailto:discuss@ux.openoffice.org (later to be changed into mailto: issues @ ux.openffice.org)
What UX needs from you
- issue ID
- short description of the change & why you changed it
- if your change affects the UI, ideally provide a screen shot of your patch in action
- optionally: provide a URL to an install set (preferably Windows, but Linux/MacOSX/Solaris work, too) including your patch
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
