^ This will be you by the end of this course!
Welcome to your Final Project! With your assigned team, you’re going to ideate solutions to common problems and create a prototype using Figma.
Next, you’ll design a usability test, including a usability testing script, series of tasks. You’ll test your prototype on at least 4 people in the class that are not in your group.
Once you’ll collected your data, you’ll analyze it and draw conclusions. You’ll write actionable design recommendations.
Lastly, you’ll tie your entire journey together in the form of a presentation! The presentation is ultimately what you turn in, with proof of each stage documented.
Quick Nav
| 1. Ideate + Prototype |
| 2. Create + Test |
| 3. Analyze Results |
| 4. Prototype Beta |
| 5. Present |
| 6. Bonus Menu |
| 7. Grading |
1. Ideate + Prototype ? (4 points)
You’re a product designer hired by the Athens Clarke-County Convention and Visitors Bureau to create a mobile app dedicated to exploring Athens, Georgia.
Content:
Your prototype should feature at least two of the following categories:
- Restaurants
- Sites to see
- Parks and recreation
- Events
- Music
- Hotels
Along with the usual mobile app components:
- Name of app
- An “About” section
- Menu/navigation
- Buttons
Create a high-fidelity MVP using Figma for iPhone 11 Pro/X (New > Browse Templates > select iPhone 11 Pro/X). Your prototype must have a minimum of 10 screens.
While not required, I highly recommend starting out with a paper prototype, or using a collaborative online tool like FigJam when brainstorming and selecting initial ideas.
PIP TIP:
Remember, each screen should be self-evident and accessible. Include navigation.
2. Create + Test ? (4 points)
Based on the usability tests you’ve implemented in this course previously, create a usability test designed to put your prototype to the test.
Write a minimum of 10 tasks. At least 4 tasks should measure common functionality using success/failure. At least 3 tasks should measure time on task. The other 3 tasks? Up to you!
Your usability test should also include two additional forms of testing, one preliminary and one post-test.
Preliminary testing methods (pick one):
- Create personas of target users (two personas required)
- Include in-depth interviews in your testing sessions
- Include card sorting in your testing sessions
Post-testing methods (pick one):
- Product Reaction Cards
- System Usability Scale
To summarize, your usability test script should follow the script you used previously in this class. The script needs to include one preliminary research method, 10 tasks, and one post-testing method.
Next, you need to recruit 4 users for testing. Users can be your fellow students, roommates, family members, etc. Do not test on people in your own team. Testing can be conducted in person or over Zoom. As you conduct your testing, take pictures (screenshots are acceptable), write notes, and record. You’ll need to show proof of each person you tested on.
3. Analyze Results ? (4 points)
It’s time to summarize your data.
Quantitative results:
- Task success rate per each success/fail task, shown in a graph
- Confidence intervals at the 95% confidence level per each success/fail task
- Geometric mean per each time on task
- Depending on your selection, include either your System Usability Scale score, or Microsoft Product Reaction cards results in a word cloud
Qualitative results:
- Write 3 usability findings, using illustrative quotes from your usability testing to support
- Sort errors into Major and Minor categories
- Write 3 design recommendations. These can be features or aesthetic elements to change, or further screens to develop
4. Prototype Beta ? (4 points)
Now that you’ve gathered all that data, and written design recommendations, it’s time to take your prototype from alpha to beta. Make a copy of your file in Figma (do NOT overwrite your existing prototype) and implement your design recommendations based on testing.
5. Present ? (4 points)
Create a slide deck including:
- A walkthrough of your alpha (the first) prototype
- A link to access your prototype on Figma
- Usability test script
- Lists of tasks and other testing methods used
- Pictures/video of testing on real people
- Analysis of testing—all the factors mentioned in the section above
- A walkthrough of your beta (the second) prototype
- A link to access second prototype on Figma
Lastly, include a short reflection on what you learned from this project + this course in general. This could include:
- New skills acquired
- Struggles faced
- Things you’re proud of
- Additional things you’d like to learn / work on in the future
- How can you take what you’ve learned in this course to your own area of study
You will need to present the deck as a group. You have two options to present:
- Asynchronous: Record on Zoom. Submit recording via eLC.
- Synchronous: Present in person (Friday, July 9th from 10:45A – 12:45A). If you prefer this option, let me know via Slack at least 24 hours in advance. You’ll still need to upload your slides via eLC as well.
Bonus Menu ?
Want to take your project to the next level? Choose one or more options to add. Include in the presentation.
~ An additional preliminary testing method from the list above
~ An additional post-testing method from the list above
~ Double the sample: Test your project on 8 people
~ Get an expert review from an expert in app design or development (an expert in the content area, ie, an expert in living in Athens, does not suffice)
~ Create a design system using FigJam or in a separate, linked slide deck.
Have another idea? Send me your proposal in a Slack message!
Grading
Projects are evaluated holistically. Points are earned rather than deducted.
When you’re working on a project, aim not just to complete its requirements, but rather to actively think about each step of what you’re doing: what it’s aiming to accomplish, how it works, why you’ve made the choices you’ve made, etc.
Also, it can be helpful to think of your projects as client work. You’d (hopefully) want something you’re creating for a paying client to be of excellent quality throughout. Sweat the details, stretch yourself a bit, and see just how awesome of a project you can create.
At the risk of sounding very cheesy, don’t think of this project in terms of completing the bare minimum, but in terms of challenging yourself and creating something that you’re actually proud of and want to show off to the world.
Above + Beyond Projects • 18 – 20 Points ?
Distinctive projects include all required elements and one or more bonus elements. Few if any technical errors are present, and a consistent sense of effort and care is apparent throughout. The reflection is of excellent quality, consistently demonstrating substantial thought and insight. Projects demonstrate creativity, mastery of subject material, and careful, thorough detail and preparation. You’ve gone above and beyond!
Meaningful Projects • 16 – 18 Points ?
Meaningful projects typically include all required elements and usually include one bonus element, too. One or two small technical errors might be present, and a lack of effort and care might be apparent in places. The reflection appears thoughtfully completed, with signs of substantial thought and insight.
Average Projects • 14 – 16 Points ?
The bare minimum. You must complete each and every required element. Doing so is essential, but by no means sufficient, to earn a good grade. The reflection appears hastily completed, with little substantial thought or insight.
Below 14 Points
Ineffective projects typically omit multiple required elements and contain no qualitative elements. They usually contain multiple major technical errors, and little if any effort and care are apparent. The reflection is often absent or, if present, cursorily completed. Ineffective projects often also fail to follow key project instructions.