The first time your work meets the gaze of a user, time stands still as you scrutinize every user's expression, sigh, and movement.
User Testing never about the user and should be about the product, but it is natural to feel like they're judging both you and your work.
Sometimes, the user performing the test is — you. You performed a user test whenever you've tested a competitor's product or an existing project. That testing likely produced a document of observations that guided your later work. Those observations were the body of your first audit.
The audits we perform in the wake of a test are always opportunities for growth. Only ignore tests that generate no guidance for improvement. There is value in all others.
The unique aspect of this exercise at this point in your project is that you've recently finished the Interface course. In addition to the observations collected, you can also apply your new knowledge to improve the work.
Exercise
Length: One-to-two hours to complete.
This exercise will significantly define the scope of your work ahead. While several exercises are remaining, this audit will determine how many aspects of your prototype require adjustment. Follow the steps below to complete the activity.
- Duplicate your current prototype within the same file.
- In a new Google Doc, write a summary that encapsulates the major themes of your user testing results. Link to your user testing documents in this summary.
- Document items that tested well in your user test.
- Create a list of at least five things to consider for updating. Be detailed in identifying the problem and possible solutions.
Once complete, update your Program Journal with links to the assets produced for this exercise. Post your Journal in the #Feedback-Loop channel for review.
///
Up next Fresh Market: Visual Foundation