Company
Government (NZ)
ROLE
UX/UI Designer
PLATFORM
Salesforce
duration
1 Year
KEY IMPACT
TL;DR
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
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.
What Became Clear Across User Groups
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
Key Quotes
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:
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:
Challenge No. 3:
How might we help transport providers complete tasks confidently and independently within the portal?
Key design decisions:
Challenge No. 4:
How might we help schools and transport providers complete reporting efficiently and on time, without adding unnecessary effort?
Key design decisions:
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.
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.





