Digital Design Gallery

A looping technical animation showing how aperture generates bokeh.

UX Design Process

User experience design is about far more than interface design. The design of any product or service from conception to delivery should be a continuous process of UX design, in which the design is constantly tested by potential users, improved, and evaluated according to its purpose.

The Tabletop Game Night app was a school project for a scheduling app project to help busy adults find common openings in their schedules and fill them with opportunities to get together and play games.

The Concept

The inspiration for this application came from difficulties trying to schedule events with extended friend groups. The app is named specifically about tabletop games, as many other kinds of activities and gatherings have predefined schedules (e.g., sports watching parties), or fewer scheduling difficulties (e.g., playing video games is often done online, and therefore more flexibly scheduled).

Independent brainstorming and interviews with other tabletop game players generated an initial feature list. With those features in mind, potential users were surveyed, and initial design ideas sketched.

User Research

John’s analysis of the survey results, and the resulting user profiles, user goals, and tasks can be found in the Executive Summary. It also contains more in-depth problem analysis, and developed task flow diagrams and user experience maps.

Use Case Scenario Designs

After consideration of the user tasks and use case scenarios, John sketched thumbnails of different app screens and interface elements.

Wireframes and Prototypes

After feedback on the thumbnails and analysis of the survey data, initial functional wireframes with placeholder assets were built.

You can see the initial testing prototype here in HTML.

User Testing Procedure

User testing was conducted in two groups: a group of users (3) from the Duquesne University, and a group of users (2) from outside. Each group saw a slightly different version of the prototype, due to differences in the versions of Axure available at each location (7.0 at home, 8.0 at the school). In both groups, John read a written introduction out loud to them, then provided a written list of tasks to be performed. The user interactions with the prototype were recorded via the Techsmith Morae software, which recorded the user via webcam while recording the screen and user inputs. When the user was satisfied that they had completed the tasks, recording was stopped and the user responded to an electronic survey about the interface they had just experienced. The users then filled out a short paper survey that allowed more open-ended responses.

You can view the test script and paper survey.

User Testing Results and Analysis

Most tasks were completed with little difficulty or confusion, and under 2 minutes average per task. Lack of appropriate feedback in one case led a user to believe they had correctly completed a task when they had not. Task test results are graphed below. Task 1 was signing up and creating an account, task 2 was setting their personal availability, and task 3 was creating a new event.

Results of the electronic survey can be downloaded here, and the completed paper surveys can be viewed here. Several users noticed that in the testing prototype the home page calendar and the other calendars presented in the app are cosmetic in nature and do not respond to user interactions or updates. John did this to limit the amount of programming involved in the prototype, but it led to user difficulties as they attempted to interact with those elements and looked to them for feedback.

Feedback-Based Improvements and Future Testing

Multiple changes are required to help resolve the issues observed during testing and mentioned in the user feedback. The images below show some of those feedback-based improvements. See the Executive Summary for more information on this project.