The Clients

This project is an individual project which started with the short talk and QA time that Round Rock ISD folks had with our class.

They came to us and explained their pain points for their current course observation tool: a paper document that would be used to take notes in class and brought back to do data analysis for the evaluation and further use.

Final Product

After the collaborative brainstorming, we as a group came up with the affinity diagram and user journey map. Then we spent a week to do individual Lo-Fi wireframe, and another week for individual hi-Fi prototype. After these we had our presentation to our client and got feedback from them.

 
 

| METHODS |
Affinity Diagram, Wireframe, 
Lean UX, Rapid Prototyping

| TOOLS |  
Paper Sketch, Sketch, InVision

| MY ROLE |
UX Designer

| TEAM |
Individual project


USER RESEARCH

AFFINITY DIAGRAM

From the Round Rock ISD talk, we took notes and some quotes that the client had, and everyone contributed to the affinity diagram by identifying the pain point, expectation, and requirement in our data.

We categorized the data-points that we collected into four group: users, current approach, dislike/pain point, and wish. From this affinity diagram, we can get insight from what are they currently doing, and their aspiration.

USER JOURNEY MAP

Based on the limited data that we had from the interview, we went through the basic user journey map for our users. Other than the walkthrough, we also place the pain points or expectation that users have in each step of process with red text. 

User Journey Maps


DESIGN PHASES

REQUIREMENTS & FEATURES

from our discussion and affinity diagram after the kickoff meeting with our client , we all agreed that iPad would be a better device option for this observation tools, because:

  • Easy to carry
  • Virtual keyboard making less noise

So, based on the device and the requirement, each member in our group started individual ideation and sketching.

 

Some of my prioritized requirements:

  • Optimize the workflow - I wanted to make the flow more rational and flexible, no more flip page problem
  • Easy to learn - because it is designed for both experts and non-experts, the tool should not be too complicated
  • Evaluation project management - users would be able to manage their project easily within a central hub
  • Autosave feature - so that the evaluator would not lose any data
  • Customized options - avoid jargon and make the tool accessible for each evaluator

SKETCHES

 

PROTOTYPE

My final design is here, play with it or you can visit with my InVision link as well. My design is focusing on the optimization of the working process. I split the whole project into three sections: 

  • Request - Inbox, the place where the requests get received. 
  • Projects - A central hub for the evaluator to manage or plan all of their projects.
  • Analysis - We didn't have further information about 'after the class' from our client, so I did not design any interface for this part. But it will be my future work since we've heard back from them in the presentation feedback time.
 

WORKFLOW

 

The simple work flow of starting a new project actually starts from Request. The evaluator will get email requests from other people, and in the inbox which integrated with this observation tool app, our user can start a new project directly based on the information that presented in the email. After the system auto-reads the email, the basic information field is filled, user can change/edit the field if there is anything wrong. Then the system will bring the user to edit general observation page, checkboxes, qualitative fields, and then preview the project.

When it is time to use the system in-class, the evaluator can switch between different activities and tabs, so that the working process would be more flexible. The activities tab design replace the big metric table that their old paper document has, and provide a better way to take and review notes. Each field has it's own text editor, so that the organization could generate a formatted report easily, and add media like photo or audio recording real-time.

Every page will be auto-saved, there is no other action needs to be taken in order to keep the data for data analysis.

 

FEEDBACKS

 

During the presentation, each of us presented our own design and walked through the prototype for our clients from Round Rock ISD. From my peer's design and our client's feedback, I think there are some other features and design that I can and will keep working on:

  • Template management - since they have different kinds of project using different template, a template management feature would be helpful for the evaluator
  • Jargon tooltip - a better way to avoid the misuse of jargon will be providing tooltip rather than let the user customize the field name. 
  • Media - improve my prototype so that it could present how to take photo, start an audio recording, attach files.
  • Everything Google - our client mentioned in the feedback that they actually utilize Google drive very frequent, integrating Google document and Google drive would be an expected solution.
  • Collaboration - every user will need to work with different evaluators and generate a synthesized report or data analysis. Collaboration among different users would be a good feature to showcase.

I will keep working on this project and have my second design iteration improved with these feedback and suggestion.