501
edits
Labs/Ubiquity/Usability/Usability Testing/How To: Difference between revisions
Jump to navigation
Jump to search
m
Labs/Ubiquity/Usability/Usability Testing/How To (view source)
Revision as of 00:34, 24 March 2009
, 24 March 2009→Analysis and Sharing of Data
Indolering (talk | contribs) |
Indolering (talk | contribs) |
||
| Line 168: | Line 168: | ||
== Analysis and Sharing of Data == | == Analysis and Sharing of Data == | ||
Spreadsheets are the easiest, fastest, and most flexible way of tracking your data. After a recording session, immediately watch video and record each error. Doing this immediately cuts down on the tedious work when writing your final report and allows you to immediately compare errors from each session. For future sessions, you will be able to automatically assign a mistake to a specific category, instead of trying to unify all the different sessions at the end. | |||
Spreadsheets are the easiest, fastest, and most flexible way of tracking your data. After a recording session immediately watch video and record each error. Doing this immediately cuts down on the tedious work when writing your final report and allows you to immediately compare errors from each session. | |||
=== Local Development Team === | === Local Development Team === | ||
The general rule is that all stakeholders (from programmers, to managers, to Quality Assurance people, and even marketers) are required to sit through at least one live session. During that session have them write down their thoughts and different errors into separate sticky-notes. Once the testing is complete buy some pizza and try grouping the stickies together on a white board and talk over what everyone saw. | The general rule is that all stakeholders (from programmers, to managers, to Quality Assurance people, and even marketers) are required to sit through at least one live session. During that session have them write down their thoughts and different errors into separate sticky-notes. Once the testing is complete buy some pizza and try grouping the stickies together on a white board and talk over what everyone saw. | ||
=== Remote Development Team === | === Remote Development Team === | ||
Contact is especially important if you are working with a remote development team. Blogging, video podcasts, and steaming data analysis are all very important but very hard to balance. Take the path of least resistance to each one. | Contact is especially important if you are working with a remote development team. Blogging, video podcasts, and steaming data analysis are all very important but very hard to balance. Take the path of least resistance to each one. | ||
An incredible Wordpress skin would be great, but for now just download a free one and move on! Don't provide too much analysis, especially this early in. Be a reporter of what is happening and ask for analysis by the team. Good analysis takes a lot of time and also discourages others from analyzing your data and becoming engaged. It's a blog, not a scientific journal. | An incredible Wordpress skin would be great, but for now just download a free one and move on! Don't provide too much analysis, especially this early in. Be a reporter of what is happening and ask for analysis by the team. Good analysis takes a lot of time and also discourages others from analyzing your data and becoming engaged. It's a blog, not a scientific journal. | ||
| Line 185: | Line 180: | ||
Make your data accessible hosting your spreadsheets on Google Docs, for example, but don't get caught up in having an interface that generates graphs. Your data may look ugly, as long as the delivery mechanism looks okay and your put up a sign that says "This data is raw, ugly, and unfinished. I just threw it up here so you can look at it if you want" people won't judge ''your ability'' to do your job well. | Make your data accessible hosting your spreadsheets on Google Docs, for example, but don't get caught up in having an interface that generates graphs. Your data may look ugly, as long as the delivery mechanism looks okay and your put up a sign that says "This data is raw, ugly, and unfinished. I just threw it up here so you can look at it if you want" people won't judge ''your ability'' to do your job well. | ||
If you have video begin by speeding video by 1.65 (link to study on library data). This is the upper limit on making everything go faster but still legible. Producing video is something we will eventually touch on (when we have a unified post production workflow) but [http://www.getmiro.com/publish/makeinternettv/ Miro] has an awesome multi-platform guide to producing and editing video we couldn't hope to match. | If you have video begin by speeding video by 1.65 (link to study on library data). This is the upper limit on making everything go faster but still legible. Producing video is something we will eventually touch on (when we have a unified post production workflow) but [http://www.getmiro.com/publish/makeinternettv/ Miro] has an awesome multi-platform guide to producing and editing video we couldn't hope to match. | ||
Again, disseminate the video as quickly as you can. If you plan on tagging the video post the video immediately after the session without the tag information and repost it again after it's been tagged. | Again, disseminate the video as quickly as you can. If you plan on tagging the video post the video immediately after the session without the tag information and repost it again after it's been tagged. | ||
Options | ==== Video Dissemination Options ==== | ||
# Upload to [http://www.viddler.com/ Viddler] and assign a programmer to tag at least one session. | # Upload to [http://www.viddler.com/ Viddler] and assign a programmer to tag at least one session. | ||
# Podcasts | # Podcasts | ||
| Line 222: | Line 214: | ||
Make sure to do this within "the fold" of how your company operates. An internal wiki, filing a word processed report, a presentation, etc. | Make sure to do this within "the fold" of how your company operates. An internal wiki, filing a word processed report, a presentation, etc. | ||
== See Also == | == See Also == | ||