UX Work

Visual Portfolio, Posts & Image Gallery for WordPress

Rules UI

Rules UI

The Rules UI allowed users without any programming experience to create complex queries in a visual interface. Non technical users needed to be able to attach different questions to different applications. For instance Question A may be asked if the user was: born before 1997 and from British Columbia but NOT if the user had a GPA of below 3.5. These kinds of queries can become complex and were creating significant overhead on the EducationPlanner BC staff to insert into the database as every Post Secondary Institution in BC has hundreds of potential optional questions they wish to put on their application depending on the applicant. 

Role

UX Designer

Timeline

November 2021 – June 2022

Goal

Decrease the amount of time spent by EducationPlanner BC staff on creating queries.

Problem

This project was a unique challenge because of the high change rate of engineering teams. The engineering team that signed off on the initial prototype was completely different from the team that ended up building the product. 

Solution

Create a graphical interface that can create if/else logic by users with no programming experience.

Research

The average user for this product has extremely low technical abilities therefore in order to create a product that is as easy to use as possible industry standards were researched in order to replicate their design pattern. Excel’s conditional formatting and Google’s custom question wizard in Google Forms served as a jumping off point to create a design.

Common Pain Points

“The logic becomes complicated quickly “

“I need changes to be done quickly”

“The page is too complicated”

Concept Sketches

Style Guide

Final Product Gallery

UX

Rules UI

Management Console

Management Console

Administrative software can be either a thing of nightmares or dreams – ask any admin worker. Management Console gives university administrators agency to customize the applications they will be sending out and review the applications received.

Role

UX Designer

Timeline

July 2022 – January 2023

Goal

Create a simpler work environment that university admins can use with minimal training. 

Problem

University admins were heavily reliant on EducationPlannerBC to teach them how to use the software. The software was initially designed based on developer needs, but the organization and hierarchy of the information was very unintuitive to the end users.

Solution

  1. Restructuring the pages into more logical groupings
  2. Standardizing design patterns and components so users can intuitively figure out what a page would do or behave based only on visual cues 
  3. Using consistent language in order to make users expend less energy on decision making to discern what a component would do. 
  4. Decreasing visual clutter on the page by strategically hiding or minimizing less necessary information.
  5. Creating more system feedback to the user in order to self diagnose issues.
  6. Creating more integrated help systems to give the user agency to help themselves without tech support intervention.

Common Pain Points

“It’s hard to find the features I’m looking for “

“I can’t tell if [this page] is able to do what I need”

“Too much is on the page at once I don’t know what to do”

CONCEPT SKETCHES

Style Guide

Final Library

UX

Management Console

Plan and Search

Plan and Search

Post Secondary applications are already a high stress ordeal to begin with. Streamlining applications into one portal reduces the complication for both students and post secondary administrators. My role was to make an enjoyable user experience for students of all backgrounds regardless of technical literacy, background or financial means. 

Role

UX Developer / UX Integration Specialist

Timeline

July 2021 – April 2023

Goal

To aggregate all the resources students need to make application decisions in one application.

Problem

University admins were heavily reliant on EducationPlannerBC to teach them how to use the software. The software was initially designed based on developer needs, but the organization and hierarchy of the information was very unintuitive to the end users.

Solution

  1. Restructuring the pages into more logical groupings
  2. Standardizing design patterns and components so users can intuitively figure out what a page would do or behave based only on visual cues 
  3. Using consistent language in order to make users expend less energy on decision making to discern what a component would do. 
  4. Decreasing visual clutter on the page by strategically hiding or minimizing less necessary information.
  5. Creating more system feedback to the user in order to self diagnose issues.
  6. Creating more integrated help systems to give the user agency to help themselves without tech support intervention.

Common Pain Points

“It’s hard to find the features I’m looking for “

“I can’t tell if [this page] is able to do what I need”

“Too much is on the page at once I don’t know what to do”

INTIAL WIREFRAMES (strapi integration)

Style Guide

Final Library

UX

Plan and Search
Menu