Prashant Mukati

Job School

By Envisionists

Role

User Experience Architect, User Interface

Duration

6 Weeks

Location

London, UK

Client

Envisionists- Oxford India Forum

Prototype Link

🎯 Project Overview

Objective

The primary goal of this project was to design a user-centric interface that seamlessly integrates course discovery and job listings within a single platform. The product needed to serve three key user groups students, working professionals, and employers across diverse fields such as business, technology, and skilled trades.

Approach

We focused on building a system where each user type could achieve their goal with minimal steps, avoiding unnecessary flow-switching. The interface and data architecture were designed to dynamically adapt based on user intent, ensuring smooth interaction paths for all roles.

💼 Business Perspective

From a business standpoint, stakeholders prioritized:

Job listings with employer visibility

Personalized course recommendations aligned with industry demand

Job listings with employer visibility

Personalized course recommendations aligned with industry demand

Job listings with employer visibility

Personalized course recommendations aligned with industry demand

However, the project faced early-stage startup constraints, including:

Limited development budget

No full Learning Management System (LMS) integration possible

Time-sensitive launch goals

Limited development budget

No full Learning Management System (LMS) integration possible

Time-sensitive launch goals

Limited development budget

No full Learning Management System (LMS) integration possible

Time-sensitive launch goals

To work around these constraints:

A lightweight course management system was built using email flows, links, and structured notification chains

Some processes, like corporate training management and employer-side workflows, were partially shifted to offline or backend operations

A lightweight course management system was built using email flows, links, and structured notification chains

Some processes, like corporate training management and employer-side workflows, were partially shifted to offline or backend operations

A lightweight course management system was built using email flows, links, and structured notification chains

Some processes, like corporate training management and employer-side workflows, were partially shifted to offline or backend operations

🚧 Key UX Challenges

Diverse Offerings Without a Centralized LMS

Problem

The platform offered three types of courses:

For students

For working professionals

For employers (corporate training)

During usability testing, a single "all-courses" landing page led to confusion. Users couldn't quickly identify which courses were meant for them, resulting in high drop-off.

Problem

The platform offered three types of courses:

For students

For working professionals

For employers (corporate training)

During usability testing, a single "all-courses" landing page led to confusion. Users couldn't quickly identify which courses were meant for them, resulting in high drop-off.

Problem

The platform offered three types of courses:

For students

For working professionals

For employers (corporate training)

During usability testing, a single "all-courses" landing page led to confusion. Users couldn't quickly identify which courses were meant for them, resulting in high drop-off.

Solution

We restructured the course discovery flow to:

Segment offerings clearly by user type

Display contextual headers, icons, and summaries to guide users at first glance

Replace the LMS with a simplified flow using email triggers, assessment links, and clear call-to-actions — minimizing friction while still maintaining structure

Solution

We restructured the course discovery flow to:

Segment offerings clearly by user type

Display contextual headers, icons, and summaries to guide users at first glance

Replace the LMS with a simplified flow using email triggers, assessment links, and clear call-to-actions minimizing friction while still maintaining structure

Solution

We restructured the course discovery flow to:

Segment offerings clearly by user type

Display contextual headers, icons, and summaries to guide users at first glance

Replace the LMS with a simplified flow using email triggers, assessment links, and clear call-to-actions minimizing friction while still maintaining structure

Job Listing Workflow and Notification Architecture

Problem

The job listing flow required coordination between:

Users (job seekers)

Job School team (internal)

Employers (external)

Due to limited staffing and system complexity, this three-way interaction was inefficient and resource-heavy. Additionally, employer onboarding was long and cumbersome, which risked delays in job postings.

Problem

The job listing flow required coordination between:

Users (job seekers)

Job School team (internal)

Employers (external)

Problem

The job listing flow required coordination between:

Users (job seekers)

Job School team (internal)

Employers (external)

Solution

Introduced a mail chain system that connected job seekers directly with employers, removing the internal team from the loop post-initial verification

Simplified employer onboarding by:

Breaking it into fragments

Collecting critical info upfront

Delaying non-essential steps for later stages

This reduced perceived effort and accelerated job listing turnaround, aligning with business needs

Solution

Introduced a mail chain system that connected job seekers directly with employers, removing the internal team from the loop post-initial verification

Simplified employer onboarding by:

Breaking it into fragments

Collecting critical info upfront

Delaying non-essential steps for later stages

This reduced perceived effort and accelerated job listing turnaround, aligning with business needs

Solution

Introduced a mail chain system that connected job seekers directly with employers, removing the internal team from the loop post-initial verification

Simplified employer onboarding by:

Breaking it into fragments

Collecting critical info upfront

Delaying non-essential steps for later stages

This reduced perceived effort and accelerated job listing turnaround, aligning with business needs

Job School wasn’t my biggest project, but it really pushed me. I had to think beyond UI/UX and solve things from a business angle too. With limited resources, I ended up structuring flows even outside the product from backend to offline steps. It was challenging, but somehow everything came together and worked out great.

🔍 UX Strategy Highlights

Built flexible flows that aligned with user intent without overloading them with choices

Prioritized clarity and context to improve first-glance understanding of content

Reduced friction by offloading heavier operations to backend/manual handling when necessary

Maintained continuity through email-driven workflows, replacing full-fledged systems like LMS in a cost-effective way