Welcome to my portfolio

My Resume

UX CASE STUDY

experi logo

Introduction

A big part of the American dream are the systems we build to help people gain the skills necessary to enter the workforce. Perhaps the most critical part of this process is our education system. 

The initial assumption I have is that the experiential learning phase of workforce preparation in the U.S. is underutilized and inherently unfair. It is also neither user friendly or efficient.

The Problem

"Students are always saying, for my first job I need experience to get experience."

- College Student Advisor/ User Interview Participant

Systems, or systemic inequality?

For many this is a ladder of success. However, for others it is an avalanche of inequality. Once inequity is inserted into this process it is further magnified at every step. 

Where can we make the most impact?

My hypothesis is that improving access to experiential learning is the best opportunity for creating positive change. Experiential learning opportunities can be as agile as the market is. 

It is also the only step that does not require major policy, societal, cultural, and economic shifts to address.

Problem Statement and Proposed Solution

How Might We:

Provide college students with career building experience so that they can more effectively join the workforce.

Proposed Solution:

Create an app that connects students in the creative, marketing, or communications fields to local non-profits so they can gain valuable experience while benefitting important causes.

Project Plan

Week 1: Discovery

Ideation, Initial Investigation, Empathize, Mood Board, Branding.

Weeks 2, 3, 4: Research

Background Research, Surveys, Comp. Analysis, User Interviews.

Weeks 3, 4: Analysis

Research Report, Card Sorting, Personas, User Flow, Storyboard, Sitemap Draft.

Weeks 5, 6, 7: Design & Iteration

Sitemap Final, Wireframes, Prototyping, User Tests, Iterations, Error Testing.

Weeks 8: Presentation & Report

Initial Flow, Practice, Final Flow, Final Presentation, Case Study.

Research - User Survey

In order to being to understand how users related to the problem statement, I conducted an online survey and had 24 total respondents. There were a few eye opening finding from their responses. 

Research - Competitive Analysis

Now that the problem is becoming clearer it is time to look at what other companies are doing to solve it. Are they focusing primarily on the business solution or the student solution?

Research - User Interviews

User interviews were extremely helpful in working towards forming a specific solution. Every user I interviewed had over ten years of experience and experienced success in their fields. Yet they all reported struggles while entering the workforce.

In my interviews I could tell that people were excited to participate in this process and willing to help. This gave me a great sense of hope for successfully creating a solution that would be viable in the market place.

Design - User Personas

Using the data gathered, I created two user types and matching personas which helped guide further product solutions.

Design - User Flow

Key Points

1. Is the user interested in pursuing a project? If so, they mark it in the application and the non-profit is notified.

2. The non-profit selects their primary candidates. They then notify the candidates using the Experi app. 

The non-profit gives a specific timeframe for a response and the app automatically moves down the candidate list as necessary.

 

Design - Low/Medium Fidelity Prototype

  • The core idea behind Experi was validated by users. At some level participants empathized with or had directly experienced issues that my primary persona had. 
  • The customized slider for the app but it did not meet the mental model of the users I tested and needed to be altered or abandoned.
  • There were positive responses to the purple color scheme and the initial branding attempts so I pushed them further in my next iteration.

Design - Initial High Fidelity Prototype Testing

User Feedback - Structural, visual, and identity issues

Assumption #1: Users will follow the path I have laid out for them.

This was a resounding no. They took every path possible and went click crazy working to discover what they were dealing with. My approach to testing was more hands off and I did not give them multiple specific tasks. I gave them general goals and watched them go to work. They really disintegrated the early iterations. This was extremely helpful information.

Assumption #2: Users want a bright and colorful interface.

This was also resounding no. My hierarchy was not supported by the color scheme and there were elements that did not function as expected due to the lack of controlling the user’s eye.

This was hard for me to take an honest look in the mirror because I was violating core graphic design principles everywhere I looked and I didn’t notice until the users shone a light on it.

Assumption #3: Users will intuitively understand my product.

This was the most powerful no. Everyone wanted an explanation at every step of the way. At this point I had built it to show in class and everyone had already heard what I was working on. This fed my assumption.

I was going to need to bring them into the subject smoothly using branding tools and an introductory flow. Now this was exciting. I think I can fix this!

Design - Improving Structure and Branding

Goal: Create a cohesive and expected experience.

Create a better sitemap.

Remove the confusion by simplification and cleaner UI.

Create specific flows that feed into each other.

Make sure buttons and interactions are consistent.

 

Goal: Improve user trust with a more professional appearance.

Inform user with highlighted content.

Control the user’s eye with improved hierarchy.

Use interactions that are easily understandable and help achieve goals.

 

Experi Branding

Design - Final Prototype

Experi - Next Steps

  • Further iterate upon prototype. Add features and improve depth.
  • Solidify incentive system.
  • Build sharing and notification features.
  • Research non-profit business user needs, pain points, delights.
  • Build non-profit desktop interface based on user flow.
  • Use case study to connect stakeholders to project.
  • Raise money to hire developers to build upon prototype.
  • Connect two user flows/prototypes and test/iterate.
  • Buy hosting, build product, and launch!