LEAD REBRANDING

LEAD
REBRANDING

ELGA Feature (English Language and General Awareness) is a core academic program offered by LEAD School and a major decision factor for new school partners. This project focused on redesigning the ELGA allocation workflow using AI-driven recommendations to reduce errors, support principals and significantly lower customer support dependency.

2022-2023

2022-2023

Problem Inspiration

High-stakes onboarding with frequent errors

Problem Inspiration

High-stakes onboarding with frequent errors

Problem Inspiration

High-stakes onboarding with frequent errors

Role

Product Designer

Role

Product Designer

Role

Product Designer

key Strategic Decisions

Guided Workflows · Error Prevention · System-Thinking UX, Visual Rebranding

key Strategic Decisions

Guided Workflows · Error Prevention · System-Thinking UX, Visual Rebranding

key Strategic Decisions

Guided Workflows · Error Prevention · System-Thinking UX, Visual Rebranding

CONTEXT & PROBLEM :
ELGA Is Critical to Successful School Onboarding

CONTEXT & PROBLEM :
ELGA Is Critical to Successful School Onboarding

Business-Critical Feature

[User Interviews & Focus Groups]

  • Principals struggled to understand how ELGA works

  • Errors were frequent during manual allocation

  • Over 70% of customer support queries were related to ELGA allocation

  • AEMs were required to hand-hold principals through onboarding

Poor First Product Experience

[Heuristic Evaluation]

Principals’ first interaction with the platform was confusing, setting the wrong tone for long-term adoption.

No Error Prevention

[Heuristic Evaluation]

The system allowed invalid configurations instead of guiding users toward correct actions.

Context

How Might We

  • How might we help principals complete ELGA allocation accurately without relying on human support prevent errors before they occur?
  • How might we guide users step-by-step without overwhelming them?

Why this matters?

Why this matters?

Why this matters?

Pain, Insight & Opportunity

Pain, Insight &
Opportunity

Complex System Logic
The backend dependencies between class, division, and student data were not visible to users, causing repeated mistakes.
Poor Information Architecture
Designing for Speed and Simplicity
Users had to repeat tasks and navigate multiple screens to complete a single workflow.
Creating simple worksheets takes approximately 15 minutes each day, indicating a need to streamline and speed up the process
Indiability to focus on instruction and student engagement. Need for streamlining these tasks and support professional growth.


Lack of Visibility into Individual Performance
While each student's performance is mapped across various topics,
there is a lack of clear visibility into individual strengths and
weaknesses making it challenging to identify areas for improvement
High Administrative Burden Reducing Instructional Focus
Indiability to focus on instruction and student engagement. Need for streamlining these tasks and support professional growth.
Heavy Reliance on AEMs
Onboarding success depended on external support rather than product clarity.

Heuristic evaluation highlighted failures in:

  • Error prevention

  • Match between system and real-world mental models

  • Aesthetic and minimalist design

While each student's performance is mapped across various topics, there is a lack of clear visibility into individual strengths and weaknesses making it challenging to identify areas for improvement

My Approach

Human-Centered Design with Intelligent Automation

I followed a Design Thinking framework and layered guidance where users needed decision support rather than more instructions. Goal is for product became capable of onboarding more schools without proportional support staffing.
I followed a Design Thinking framework and layered guidance where users needed decision support rather than more instructions. Goal is for product became capable of onboarding more schools without proportional support staffing.
Empathize - Understanding Real Workflows
  • Focus group sessions with principals and AEMs
  • Mapping onboarding journeys and common failure points
  • Identifying where users lost confidence and contacted support

01

Define - Reframing the Problem
  • Instead of redesigning screens, the core problem was reframed as: Users should not need to understand the full system logic to complete ELGA correctly.

02

Ideate - To guide, Not a Customer Support Replacement
  • Stepwise guidance
  • Auto-detecting dependencies
  • Reducing manual configuration

03

Iterative Prototype - A Recommendation Engine (Yiso)
  • Recommendation Engine suggests: ELGA level, Division mapping, Student grouping
  • Users make only three decisions, everything else is handled by the platform.

04

Deliverables

Designed for Accuracy, Speed and Confidence

  1. UX heuristic evaluation report
  2. End-to-end user flows and use-case mapping
  3. AI recommendation interaction model
  4. High-fidelity responsive web designs
  5. Design system alignment with core platform

Next Steps on Enterprise Scalability

Next Steps on
Enterprise Scalability

Balance business goals with usability, Ship features into live systems as visual rebranding effort using a new design system to improve clarity, hierarchy, and consistency across ELGA flows problems.

Lesson learned

Product Should Replace Human Dependencies, Clear Scoping Saves Design Cycles.

Design decisions had direct business impact by reducing human workload. Early ambiguity in feature scope led to repeated iterations. Aligning constraints and success criteria earlier would have accelerated design and development decisions.
Design decisions had direct business impact by reducing human workload. Early ambiguity in feature scope led to repeated iterations. Aligning constraints and success criteria earlier would have accelerated design and development decisions.

Send a Message