RiseKit

 

(If on mobile, please turn your phone side-ways for the best experience)

My Role.

As the lead Visual/UI Designer, I lead this project from constructing accessibility & baseline guidelines for my visual design process to producing new style guides, interactive prototypes, and final designs. I worked alongside the Dev team & UX to redesign RiseKit’s candidate facing mobile experience.

 
 

Core Collaborators.

Lead Software Engineers
Lead UX
Developers
 
Begin your job journey…

The Project.

RiseKit is a company that partners with several non-profit organization to give people from under-served communities equal access to jobs. Individuals from those organization are brought on to RiseKit’s platform through that partnership and are guided through the process of finding a job or resource. What is needed is a mobile app that communicates this and aids those individuals to complete their job search journey. 
 
 
 

The Strategy

Internal Business Problem:

RiseKit’s mobile platform design wasn’t comprehensive resulting in alarming drop-off rates. 

External Business Problem:

1) Consistently breaking down and 2) Wasn’t understandable. This resulted in the push for a mobile re-design.

The Process:

To attack these short comings, I had to make numerous documents to track what Orgs needed, what was feasible, and in my position: base the UI off of the “why” and the user-centered design process.

Made by me (People under an organization are referred to RiseKit; once joined, RiseKit is able to connect them to a variety of services and job opportunities)

 

Made by me

Why?

Why are we doing this?

As I looked through the platform I found that there were errors that needed attention:
  1. Prior information given by the UX Team was not considered

  2. No design system

  3. No consistency across the mobile platform.

 

Early Statistics:

(change in stats are at the bottom of this study)

(out of 233) —This refers to onboarding; it does not include those who A) Got a job, but didn't show up, B) Got an interview, but didn’t show up, or C) Dropped-off on a step once signed up

 

I got these numbers from a website called FullStory, on Aug 31, 2020 — These are a few specific drop-out stats before sign up and tracking outside of RiseKit.

 

Email Click-through-rate: 1.78% (in Q3)

Examining & Specifying Design Needs

Competitive Analysis & Personas

 
Due to not enough user interviews, we were left to use what we had to understand the common wants of the average RiseKit individual:
  1. Goals

  2. Motivations

  3. Influences

  4. Frustrations

My Accessibility Guide & Interface Checklist
&
New Design System

Because it’s ONLY mobile design, the design system is a little smaller than a usual one would be. However, I wanted it to capture the essentials so that it would make it easier to refer back to components and icons used throughout the platform.
 

Before I joined RiseKit

After I joined RiseKit

Following accessibility guidelines of 44x44 dp icon sizing. Also making sure that the Dev Team receives icons that are 44x44 CSS

 

Before I joined RiseKit

After I joined RiseKit

Site Map

Sitemap

Wireframes

Wireframe examples

Motion Use

When choosing motion, it came down to a few things:

  1. Will we use one motion throughout the entire experience?

  2. If not, why?

  3. How will we settle on this motion?

Most users don’t want to spend too much time watching an ease-in or ease-in-and-out when they just want to get something done without waiting for a motion to die down.

This custom Bézier curve is what I used in the Interaction Details, and the Home page to the right is how the drawers and sliding pages look using the custom animation.

RiseKit platform design & flow.

All icons and illustrations shown are made by me in Illustrator.

Sign Up.

User’s are personally invited to Risekit by whichever organization they are linked to. Once they click the invitation, they are taken to a quick sign up process. If a user’s information has already been filled out by their organization, they just need to verify the information and continue in to RiseKit.

Onboarding.

  1. Documents

  2. Receive links

  3. Be able to pin comments (place chat anchors) so that they can later refer to a stage in Chat if they’d like to.

 

Home.

  1. Documents (sent & received)

  2. Links (jobs & resources)

  3. Where they are in their journey to find a job/build a professional career, which is communicated through the progress bar.

  4. They can complete their Profile here as well.

  1. Documents (sent & received)

  2. Links (jobs & resources)

  3. Where they are in their journey to find a job/build a professional career, which is communicated through the progress bar.

  4. They can complete their Profile here as well.

Pathway Progress.

Here is where users check their progress as they work towards building a strong profile for hiring managers to see and simply building their professional portfolio. By giving a general overview, I was able to give users a high level idea of:
  1. Which step they are currently on and

  2. What that step contains

    *Note: Actual words (“Active” vs. “Non-Active”) were used to communicate what they needs to focus on; not just colors due to red-green color blindness.

(Click to expand some screens) Screenshots of basic functionality. Fluidity of prototype can be seen in video.

Profile.

All of a user’s information will be settled in their Profile section. Basic information, job seeking information, current situation information, and simple settings. 

Results & Reflection.

Click rate was 1.78% in Q3 and has jumped to 2.5% in Q4!

Only .1% away from the average stat.

With a clear CTA and preview of what’s awaiting, user’s became more prone to return to RiseKit’s platform. CTA’s are known to make it clear to user’s where they need to go next, while also communicating that by clicking the button, they'll be directly taken to the message as opposed to having to get on whichever browser they commonly use to navigate to RiseKit’s platform.

Retention rate & Adoption rate changes

Looking back.

1.

Wish I had spoken up about data rates before development started.

2.

The sorting function should have been consistent. The “New to Old” sorting tool wasn’t intuitive at all and didn’t have a label on what it did.

Next steps:

1.

I didn’t get to test the product on the actual user’s under the organizations joined with RiseKit…Only the organizations saw the designs and gave their feedback.

2.

Get quantitative feedback from recently launched product and reflect on how to update next release/update.