Usability+Testing+What+did+we+learn?

=**What did we learn from our usability testing?**= =**Results and Implications**= **December 9th, p.m.** **Ahhh ... I know what I was going to say in the email ... someone could take the text below - __How we tested, limitations, & what we tested__ and write it in a narrative/sentence format. I'm working on the 'results of testing' tonight, then we can combine efforts and work on implications of the results. Okay?** **:-)**


 * How we tested:**
 * users were invited to navigate through a mock-up of our application in Mocking-Bird
 * users were observed during their interactions with the mock-up and notes were taken on their reactions/experiences
 * in two cases, a record was made of the verbal responses made by users
 * designers interacted with users and responded to questions as they arose
 * after interacting with the mock-up, users were invited to fill out a short response form asking for further information on their user experience - was it intuitive? were paths easy to follow? etc. (don't have sheet in front of me)


 * Limitations/Evaluation of Testing Methodology:**
 * we found that during the testing situation the checklist was difficult to use - users didn't necessarily follow the progression of screens as we had anticipated and it was easier to simply keep running notes on their experiences. Agreed
 * in future, we will not use the checklist format, but rather keep notes on the user experience in a more free-flowing format Agreed
 * we found that using the mock-up also had its limitations and did not allow users to fully experience the application - consideration is being given to ways in which we could create a more realistic user experience that would allow users to create actual content Agreed
 * some users were not comfortable with a 'think aloud' but responded well to particular directives followed by questions to elicit feedback and suggestions
 * it would have been useful to have a completed example as a demonstration of the devices end product...even if used a combination of other apps to produce the sample.


 * What we tested:**
 * ** we invited users to follow the paths for three main tasks: read/get a story, edit a story, create a new story **
 * ** we tested to see if the paths we have set up are easily navigated and intuitive to use **
 * we provided an open-ended series of questions to check for understanding of the products purposes
 * we tested for understanding of each of the functions embedded on each screen


 * Results of testing:**


 * What the results mean for our design/direction:**