2020 / Design Challenge

Design Challenge - HuskyMend

January 2020

5 days

My Role

Interaction Design

Team

N/A

Project Overview

This project is a required 5 day design challenge as part of my interview process for Google's Internship. I designed an accessible app that allows better communication and connivence for students and faculty in a guided process.

These are the Core Screens for the Faculty

Full process walk through

1.0 Research

1.1 Initial Design thinking & Timeline:

Since this design challenge has an extremely short time frame of only 5 days, setting a schedule is important to understand what process I plan to follow.

1.2 Deep dive into the problem space :

With my scope, target user, and research methodology defined, I quickly conducted secondary research and began my first step in primary research and naturalistic observation.

1.3 Quantitative Data (Surveys)

After gaining a better understanding of the context surrounding campus facilities through my own observations, I began surveying students across campus to have a holistic understanding of the problem space.

1.4 Qualitative Data (Interviews)

As most of the survey responses returned and synthesized, I began interviewing students to have a more in depth understanding of why students think and act in a certain way in regards to campus facilities.

Student Interview Report
Staff Interview Report

1.5 Synthesized Insights

The insights were synthesized into specific pain points to propose a refined problem statement for myself.

1.6 Proposed Problem Statement

After detailed research during the 2 day time frame, this was the problem statement I proposed for myself.

2.0 Design

2.1 Design Principles

2.2 Design Requirements

Based on my design principles, a list of design requirements were created for both the student and faculty side. A table of action objects and context was used to understand what needed to be designed within the given time frame for efficient testing.

A different table was created for the staff side, since the product would have a very different use for them.

2.3 Information Architecture

This information architecture was created to help me create low fidelity prototypes for testing.

2.4 Paper Prototype (Lo fi)

Using paper prototypes, testers can sketch and make suggestions on the prototype. Therefore, this method was chosen for a rapid testing session over a one day period of time.

3.0 Usability Testing

3.1 Stakeholder Testing

With the limited time I had, I was only able to schedule 3 total participants. Ideally I would have wanted more in a usability test to ensure more stable results, however, for a design challenge like this it would not have been realistic. Each individual was a direct stakeholder for the proposed project, therefore their feedback and results were very valuable. Each testing session lasted approximately 30 minutes. During the session, each task scenario was explained by me as test administrator. Test participants attempted completion of six prompted tasks, alongside solving a self directed task.

3.2 Results

The feedback mainly came from the UI outlines of the paper prototype. Since the benefit of paper prototyping encouraged testers to sketch and give suggestions, I was able to synthesize the results into straight forward redesigns for the final mockup.

4.0 Final Deliverable

The final product for this design challenge is an accessible app that allows better communication and connivence for students and faculty in a guided process.

4.1 Style Guide

4.2 Interaction Showcase

This is an interactive showcase of the overall task flows available in the product.

4.3 Why QR codes?

QR codes are not as popular in the US compared to asian countries, however, in this case the reason for design is justified.

4.4 Mock up Analysis

Finally specific design language is analyzed.

4.5 Next Steps

This was a very successful design challenge, it was a great opportunity to showcase my skills as a designer. In the future, I would like to show an interactive prototype with Invision or Principle!