Labs/Course/UCD/planning: Difference between revisions
< Labs | Course/UCD
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
*Apply UX techniques in the course that both the faculty and the community are interested | *Apply UX techniques in the course that both the faculty and the community are interested | ||
* | |||
*Select a course topic that both the design community and Mozilla will be interested and benefited. | |||
*Create a environment to encourage easy participation: | *Create a environment to encourage easy participation: | ||
**a place to share students work | **a place to share students work | ||
| Line 19: | Line 21: | ||
*If the course involves user research, make sure user privacy is well protected. Use [[Labs/Test Pilot/userstudyreleaseform|Mozilla User Study Release Form]] if needed. | *If the course involves user research, make sure user privacy is well protected. Use [[Labs/Test Pilot/userstudyreleaseform|Mozilla User Study Release Form]] if needed. | ||
*If it is important to get consistent exposures for the course, have a UX media follow up the course from the beginning | |||
*If it is important to get consistent exposures for the course, have a UX media follow up the course from the beginning. (Johnny Holland might be interested) | |||
*To maximize the value of course outcome, define a product team that could potentially pair up with the course at the first, and be clear with what kind of outcome they are interested. | *To maximize the value of course outcome, define a product team that could potentially pair up with the course at the first, and be clear with what kind of outcome they are interested. | ||
Latest revision as of 21:47, 4 January 2011
Back to Open Design and Research
Two principles to define an Open UX effort
- All work is shared under CC licenses
- Encouraging participation
Key elements for a successful collaborative course
- Apply UX techniques in the course that both the faculty and the community are interested
- Select a course topic that both the design community and Mozilla will be interested and benefited.
- Create a environment to encourage easy participation:
- a place to share students work
- a template for organizing students outcome
- a panel that could give targeted feedback (e.g. UX professionals, industry insights, technology trends, etc.)
- ways to allow panel or public feedback (within or beyond the course itself)
Other useful details
- If the course involves user research, make sure user privacy is well protected. Use Mozilla User Study Release Form if needed.
- If it is important to get consistent exposures for the course, have a UX media follow up the course from the beginning. (Johnny Holland might be interested)
- To maximize the value of course outcome, define a product team that could potentially pair up with the course at the first, and be clear with what kind of outcome they are interested.