Skip to content

Latest commit

 

History

History
69 lines (45 loc) · 3.6 KB

README.md

File metadata and controls

69 lines (45 loc) · 3.6 KB
Raw

Odd-Jobs

An app to help students do small simple jobs to keep their schedules busy and their pockets full!

UX Team Members

Nick- Created Draft Protocol, worked on Draft Prototype, and conducted user tests Gabe- Created Draft Protocol, worked on Draft Prototype, and conducted user tests

User-Centered Design Artifacts

Phase I: Analyzing Users, Competitors, and Initial Designs

Executive Summary

Initial research and design for Odd-Jobs was focused on identifying who students and normal people were, as well as an easy way to post and take jobs.

  • Competitive analysis revealed an opportunity to focus on a specific audience of users:
    • College Focused: Intended for use by college students and those that live around those communities
    • Simple jobs: Keep the scale/scope of jobs low to ensure proper completion
  • Heuristic evaluation identified competitor strengths and weaknesses in user interface:
    • Unified design elements
    • Opens new tabs instead of staying in one tab
    • Inconsistent menu placement across new areas
  • New personas and scenarios indicate the needs of the users:
    • Easily identifiable student status
    • Accessible way to accept and post jobs
  • Sketches and diagrams detail initial design concepts:
    • Quick navigation through various menus and submenus
    • Seach filter for new job postings
    • Icon for student status next to username

Full phase I report

Phase II: Refining interaction and designing wireframes

Executive Summary

Phase II was dedicated to developing new features and improving existing ones. We set out to make a UI that would ensure we achieve strong user retention through solid features and good UI design.

  • Over this sprint, we elicited informal feedback and had independent testers perform Cognitive Walkthroughs on existing wireframes
    • We learned our original designs didn’t have enough depth to accomplish core functionality
    • Users prefer a separate interface for posters and “employees”
  • Over this next sprint, we will work to improve wireframes to make our app more learnable and make it clear to users the expected workflow
    • The caveats from this research are that our app was not fully functional at the demo, which limited our ability to get deeper feedback

Full phase II report

Phase III: Prototypes and User Testing

Executive Summary

Phase III was dedicated to finalizing our prototype and conducting user tests on that prototype. This was done to find oversights in our design and provide feedback on what could be done better.

  • Our Phase 3 started with a Usability Test plan that included initial User Tests designs such as our objective, our screening parameters, and an early draft of our test workflow.
  • Our team took the Figma wireframes from the last phase and expanded on them to develop a working prototype for our user tests.
  • The UX team developed a draft of our testing protocol and ran a pilot test to see where our protocol/prototype were ready for the full User Tests and to help prepare the team to conduct these interviews.
  • Our UX team conducted a series of 6 user tests with selected users from the CSCI 431W student pool on 12/10. We utilized our final protocol and prototype to gather information on whether users were able to complete the tasks and their feedback which we compiled into our records to discover common concerns and pain points.

Full phase III report