Redesigning School Transport Assistance at Scale

Redesigning School Transport Assistance at Scale

Turning a fragmented legacy system into a unified Salesforce-based ecosystem

Turning a fragmented legacy system into a unified Salesforce-based ecosystem

Company

Government (NZ)

ROLE

UX/UI Designer

PLATFORM

Salesforce

duration

1 Year

Outcome

Outcome

KEY IMPACT

Improved accuracy, efficiency, and trust across 3 designed portals and 12+ forms through consistent, predictable UX patterns

Improved accuracy, efficiency, and trust across 3 designed portals and 12+ forms through consistent, predictable UX patterns

Improved accuracy, efficiency, and trust across 3 designed portals and 12+ forms through consistent, predictable UX patterns

Consolidated 8 application form sets into 1, cutting backend maintenance by 87.5%

Consolidated 8 application form sets into 1, cutting backend maintenance by 87.5%

Consolidated 8 application form sets into 1, cutting backend maintenance by 87.5%

Eliminated 20+ day reprocessing delays by reducing application errors and submission failures

Eliminated 20+ day reprocessing delays by reducing application errors and submission failures

Eliminated 20+ day reprocessing delays by reducing application errors and submission failures

Reduced customer support burden by minimizing user errors, rework, and task-level training needs

Reduced customer support burden by minimizing user errors, rework, and task-level training needs

Reduced customer support burden by minimizing user errors, rework, and task-level training needs

Background

Background

TL;DR

The School Transport Assistance program supports students in New Zealand who face distance or transport barriers to attending schools.

However, the system(Pokāpu waka kura) behind was fragmented across siloed tools, leading to incorrect applications, long processing times, duplicated data, and high operational effort. These issues directly affected school attendance, data reliability, and the ability for a lean team to operate effectively.

This project focused on consolidating the system into a single, reliable that caregivers, schools, and transport providers could trust and easy to work with.

The School Transport Assistance program supports students in New Zealand who face distance or transport barriers to attending schools.

However, the system(Pokāpu waka kura) behind was fragmented across siloed tools, leading to incorrect applications, long processing times, duplicated data, and high operational effort. These issues directly affected school attendance, data reliability, and the ability for a lean team to operate effectively.

This project focused on consolidating the system into a single, reliable that caregivers, schools, and transport providers could trust and easy to work with.

The School Transport Assistance program supports students in New Zealand who face distance or transport barriers to attending schools.

However, the system(Pokāpu waka kura) behind was fragmented across siloed tools, leading to incorrect applications, long processing times, duplicated data, and high operational effort. These issues directly affected school attendance, data reliability, and the ability for a lean team to operate effectively.

This project focused on consolidating the system into a single, reliable that caregivers, schools, and transport providers could trust and easy to work with.

Challenge

Challenge

What Made This Hard

  • Different user group and portals with one shared system underneath

  • Distinct workflows that still had to produce consistent, reliable data

  • Platform constraints and a high-risk environment

  • Real consequence tied to accuracy, eligibility, and trust

Process Overview

Process Overview

How the Work Unfolded?

My contribution spanned three phased efforts - portals redesign, reporting forms design, and application redesign, all of these were delivered incrementally over the course of the project.

Discovery

Discovery

What Became Clear Across User Groups

Drawing from surveys, workshops, and internal conversations, these patterns show where the system broke down for each group and how those failures cascaded downstream.

Drawing from surveys, workshops, and internal conversations, these patterns show where the system broke down for each group and how those failures cascaded downstream.

Drawing from surveys, workshops, and internal conversations, these patterns show where the system broke down for each group and how those failures cascaded downstream.

Caregivers

Where it broke

Scattered and unclear information, often spread across external sites, made it difficult for caregivers to choose the correct application type.

Why it mattered

Wrong applications → resubmissions → delayed transport support→ Caregivers forced to reschedule schooling

Schools

Where it broke

School and caregiver portals looked identical, leading schools to submit applications without logging in and receive false success feedback.

Why it mattered

Applications appeared submitted but were never received → loss of trust → increased follow-up and manual checking

Transport Providers

Where it broke

A new reporting approach assumed higher technical literacy, creating reliance on training and support.

Why it mattered

Inaccurate data → delayed reporting → Manual intervention → increased operational load

School Transport Team

Where it broke

Headcount reductions combined with eight separate application form sets made the system difficult to maintain.

Why it mattered

Outdated information → slower assessments → delayed assistance → students unable to receive transport support on time

Findings

Findings

Key Quotes

“I spend 5+ hours per week correcting the same errors from customers.”

“I spend 5+ hours per week correcting the same errors from customers.”

-School transport team

-School transport team

“The information we have been given has been very slight, and that means we are unable to support school teams when they have request about submitting applications/ are trying to track where they are etc..”

“The information we have been given has been very slight, and that means we are unable to support school teams when they have request about submitting applications/ are trying to track where they are etc..”

-School transport team

-School transport team

“Very little or no information in FAQ section; it would be helpful to have links for video on 'How to use PWK'…”

“Very little or no information in FAQ section; it would be helpful to have links for video on 'How to use PWK'…”

-School transport provider

-School transport provider

"When to update one single thing, we have to make changes eight times...”

"When to update one single thing, we have to make changes eight times...”

"When to update one single thing, we have to make changes eight times...”

-Project manager

-Project manager

UI Phase

UI Phase

Solutions

Here are a few of the design solutions as they related to the discovered core problems

Challenge No. 1:

How might caregivers and schools submit applications accurately and reliably, without applications being lost?

Key design decisions:

  • Made each portal clearly distinct through visual and branding cues, so schools could immediately recognize where they were and avoid starting applications in the wrong place

  • Made each portal clearly distinct through visual and branding cues, so schools could immediately recognize where they were and avoid starting applications in the wrong place

  • Made each portal clearly distinct through visual and branding cues, so schools could immediately recognize where they were and avoid starting applications in the wrong place

  • Embedded critical guidance directly into the application flow, allowing users to make the right application choice without relying on external websites

  • Embedded critical guidance directly into the application flow, allowing users to make the right application choice without relying on external websites

  • Embedded critical guidance directly into the application flow, allowing users to make the right application choice without relying on external websites

  • Made application status and assessment steps visible, so schools could track progress confidently instead of waiting without feedback or contacting the transport team for updates

  • Made application status and assessment steps visible, so schools could track progress confidently instead of waiting without feedback or contacting the transport team for updates

  • Made application status and assessment steps visible, so schools could track progress confidently instead of waiting without feedback or contacting the transport team for updates

  • Guided schools to the correct portal before taking action, reducing misrouted applications at the point of entry

  • Guided schools to the correct portal before taking action, reducing misrouted applications at the point of entry

  • Guided schools to the correct portal before taking action, reducing misrouted applications at the point of entry

Before

After - Caregiver Portal

After - School Portal

Challenge No. 2:

How might we reduce effort across the application process for both applicants and internal teams?

Key design decisions:

  • Consolidated eight separate from sets into a single modular flow, reducing duplication while still supporting different eligibility scenarios

  • Consolidated eight separate from sets into a single modular flow, reducing duplication while still supporting different eligibility scenarios

  • Consolidated eight separate from sets into a single modular flow, reducing duplication while still supporting different eligibility scenarios

  • Structured the application into clear, manageable steps, using plain language to help applications progress without feeling overwhelmed

  • Structured the application into clear, manageable steps, using plain language to help applications progress without feeling overwhelmed

  • Structured the application into clear, manageable steps, using plain language to help applications progress without feeling overwhelmed

  • Enabled data sharing across the system, minimizing repeated data entry and reducing effort for both users and internal staff

  • Enabled data sharing across the system, minimizing repeated data entry and reducing effort for both users and internal staff

  • Enabled data sharing across the system, minimizing repeated data entry and reducing effort for both users and internal staff

Before

Before

Application Form Design

Application Form Design

Challenge No. 3:

How might we help transport providers complete tasks confidently and independently within the portal?

Key design decisions:

  • Structured content and navigation deliberately, helping providers understand where to go and what to do at each step

  • Structured content and navigation deliberately, helping providers understand where to go and what to do at each step

  • Structured content and navigation deliberately, helping providers understand where to go and what to do at each step

  • Surfaced critical information at the point of use, supporting task preparation and reporting while reducing reliance on training sessions

  • Surfaced critical information at the point of use, supporting task preparation and reporting while reducing reliance on training sessions

  • Surfaced critical information at the point of use, supporting task preparation and reporting while reducing reliance on training sessions

  • Designed a dedicated support space with scale in mind, allowing new content to be added over time without increasing complexity

  • Designed a dedicated support space with scale in mind, allowing new content to be added over time without increasing complexity

  • Designed a dedicated support space with scale in mind, allowing new content to be added over time without increasing complexity

Before

Before

After - School Transport Provider Portal

After - School Transport Provider Portal

Challenge No. 4:

How might we help schools and transport providers complete reporting efficiently and on time, without adding unnecessary effort?

Key design decisions:

  • Enable data sharing across system, reducing repetitive work and manual re-entry.

  • Enable data sharing across system, reducing repetitive work and manual re-entry.

  • Enable data sharing across system, reducing repetitive work and manual re-entry.

  • Introduced a "save for later" flow, allowing users to pause, return, and complete reports flexibly without losing progress.

  • Introduced a "save for later" flow, allowing users to pause, return, and complete reports flexibly without losing progress.

  • Introduced a "save for later" flow, allowing users to pause, return, and complete reports flexibly without losing progress.

Report Design Example

Report Design Example

Challenges

Challenges

How I navigate constraints along the way

This project required balancing ideal UX against Salesforce platform limitations, tight timelines, and limited direct access to caregivers.

To move the work forward without increasing risk, I focused on a few deliberate strategies:

  • Bridged gaps in user insight by working closely with frontline staff who interacted directly with caregivers, ensuring decisions were grounded in real-world context.

  • Designed within platform constraints first, prioritizing native Salesforce components and introducing custom solutions only where they delivered clear value.

  • Partnered closely with developers, working side by side to align on feasibility early and maintain momentum within tight delivery windows.

  • Validated clarity through internal testing, using staff unfamiliar with the program to pressure-test navigation, language, and task understanding.

Reflection

Reflection

What This Project Taught Me and What Comes Next

This project was a practical lesson in designing within real-world constraints. Platform limitations, tight timelines, and limited user access required me to adapt my approach and make deliberate trade-offs across design and collaboration.

The experience reshaped how I think about designing within live systems, especially the importance of anticipanting downstream impact and designing for reliability as much as usability.

Key Takeaways

Talk often and bridge gaps

Frequent communication helped surfaced blind spots early and prevented misalignment later.

Turn limits into leverage

Constraints can spark creativity when treating them as prompts, not barriers.

Transparency saves time

Sharing priorities openly helps teams focus and cut down on wasted effort.

Negotiate what truly matters

Being clear about what was flexible and what was not helped protect outcomes without slowing delivery

An Ideal Next Step

Although analytics tooling was not in place during this project, I would advocate for it as a foundation for continuous improvement, especially in a system where small changes can have outsized downstream impact.

thanks for stopping by

©2025 by Emma Wang

thanks for stopping by

©2025 by Emma Wang

thanks for stopping by

©2025 by Emma Wang