Last week, I stated, “In User Experience (UX) Design, creating a simplified version of a product before its full development is called Prototyping.” Prototype is the fourth stage in the UX Design Thinking Process. This week, I tested my prototype with two users. Although Design Thinking is an iterative process, the final stage of the 5 stage-model is called Test.
Stage 5: Test
Testing is a crucial component of product development that involves real users. Users interact with a prototype and provide honest feedback. This stage helps UX designers determine whether their product or solution is valid and works effectively or if it needs reworking. Amid a testing session, alterations and refinements may occur as designers observe how users experience and interact with their prototype. Furthermore, the test results may lead back to prior Design Thinking stages, or even as far back as identifying additional needs users may have and redefining the problem.
User Testing vs. Usability Testing
User testing and usability testing take place in the testing stage of Design Thinking. The two sound similar, have similar end goals, and are UX terms often used interchangeably (even by me). However, CareerFoundry makes it clear that they are distinctly different.
Here are the similarities between the two:
- Both tests seek to design a product or solution that meets user needs
- Both tests take note of user interactions, experiences, and challenges while utilizing the product or solution
- Both look for ways to combat and address the identified challenges
Here are the differences:
- User testing focus on the user. A product or solution is presented to a user to determine whether the user would actually want, need, or make use of the product. User testing asks the user if this product would be of any benefit to them.
- Usability testing focuses on the product. It “looks at users’ needs in the context of an existing product.” The goal is to observe a user’s interactions with the product to see if the product works for them. There are often tasks for the user to complete which help UX professionals identify how users might journey through the prototype to accomplish their tasks.
Usability Testing in Practice
This week, I performed two usability test sessions using a prototype of an app I am designing for the city of Baltimore called Baltimorean. I’ll take you through the preparation of my usability tests as well as my test results.
Creating Tasks Prompts
Every usability test is performed by observing participants through activities. Within a test session, users have specific tasks to complete. According to Leow Hou Teng, writing good task scenarios for usability tests allows us to “test our products more robustly to collect the insights we need.”
I wanted my tasks to be realistic and relatable for a potential resident of the city of Baltimore. I recently created user flow diagrams, detailing three specific user journeys within Baltimorean. For my usability test sessions, I converted these three user stories into task prompts to observe how these user flows would take place with real users.
- User Flow 1: Finding Relevant Articles
- User Flow 2: Finding a Local Event
- User Flow 3: Submitting a Service Request
- Task 1: You would like to read one of the most recent news articles published by the City of Baltimore. After reading the story, favorite or save it for later reference.
- Task 2: You have noticed a pothole developing on a road you frequently use. You would like to view all services and notify the city by submitting a service request.
- Task 3: You would like to view upcoming events within a specific event category. Once you find an event you are interested in, add it to your calendar.
Drafting a Script
To prepare for my test sessions, I created a script. My script assisted me with guiding and coaching my users through each session. Following an example test script, I drafted my own script to read aloud during my test sessions and keep each session controlled and focused. The session script helped me do the following:
- prepare each user for the session
- ask for their consent to record the session
- inform them that we would be testing the product and not them
- ask questions concerning their daily device usage
- walk them through each task
- inquire about any additional questions, comments, and feedback they have
You can read my full script within the full usability test document linked below.
Prototyping with POP
Although I created my first prototype for the app last week, this week I took it one step further by using a prototyping app and web platform called Prototyping on Paper (POP). POP allows designers to turn basic prototypes into interactive ones. Here’s an example of how the app works.
I took photos of my screens from last week’s prototype and formatted them for POP’s iPhone X. Once all screens were formatted correctly, I uploaded them using the POP app and then took to the web platform to link pages and add in interactivity. After testing my digital prototype a few times to ensure the interactivity worked as intended, it was time to get testing! Here is a link to my POP prototype.
Although usability tests are traditionally performed in person, I performed my tests virtually via Zoom. Whether remote or in person, test sessions are typically recorded for later reference.
Usability Test 1
Participant Background
Aideh O., 26
- Maryland resident, Baltimore County
- Engineer, Illustrator/Designer/Visual Artist
- “Looks at computers all day”
- Spends about 12 hours a day using devices to access the internet
- Mobile devices include smartphone, tablet, and smartwatch, all Apple-branded
- Utilizes mobile devices and desktop devices comparably
- Favorite app: Procreate
Usability Test 2
Participant Background
Tolani B., 26
- Maryland resident, Prince George’s County
- Cyber Security Analyst, Videographer
- “Works all day”
- Spends about 10 hours a day using devices to access the internet
- Mobile device: Apple-branded smartphone
- Utilizes mobile device more than her desktop/laptop
- Favorite apps: Twitter, HBO Max
Test Results
As you may have noticed while watching my testing sessions, the usability test sessions gave great insight into what works well within the Baltimorean app and what needs revising. Both participants mentioned that the app was very straightforward and clear.
The following potential problem areas were highlighted during user testing sessions:
- The app needs a back button in case users want to return to a previous step within their journey.
- The icons on the event pages should be revisited to represent and communicate “add to calendar,” “register,” “turn on notifications,” and “contact event planner” more clearly.
- The language selector and online payment icons need to be substituted with other icons or text. Language selection can potentially take place on a screen before the app’s home screen.
- The “more” page may not be necessary because users can access more information on Baltimore city’s website. Additionally, the bottom icon navigation feels more solid and direct with five icons.
- On the “services” page, “all services” can be read as “view all services by category.” Options on the “services” page can be labeled with descriptions
- for clarity. Pages within “services” could also use description blurbs so users
- are aware of what they are viewing and what options they have.
Altogether, users were able to utilize the app and perform tasks seamlessly, finding what they were looking for quickly. They stated that the bottom icon navigation worked well and the app was easy to navigate.
Final Thoughts
All great products have been tested and tested again. Apps update, websites are refreshed, products are upgraded, etc. The testing does not stop, even after a product, solution, software, or service has been released to the public. Testing is a critical part of product development because improvements can always be made. The more a product is refined and perfected to meet a user’s needs, the happier the user will be. So if you have identified pain points within your first prototype, rework it. If at first you don’t succeed, try again!
Sola's Thoughts 