elise pace

Fair Work Commission.

Sole designer on a new national service portal that 50,000 people a year rely on.

RoleLead UX/UI Product Designer, via Exco Partners
DurationDec 2024 – Aug 2025
SectorGovernment, workplace relations
The client

Australia's Workplace Umpire.

The Fair Work Commission is the national workplace relations tribunal, administering the Fair Work Act, setting minimum employment standards, resolving disputes and approving enterprise agreements for millions of workers and businesses.

33K+Applications processed every year, most lodged by people facing the process for the first time.
20KConciliations and hearings managed annually.
MillionsOf Australian workers and businesses relying on a trusted national institution.

What One Designer Shipped.

−30%Support request response times, with journeys designed for accessibility and efficiency end to end.
8 moResearch to national launch. The new portal went live in August 2025, meeting all government accessibility requirements.
1Designer, research to delivery, with every decision evidenced, documented and defended.
Story one

Ship the Portal.

The brief

How Might We Develop a Responsive, Accessible Service Portal for Users Seeking Critical Info?

Problem key insights: manual paper-based processes, fragmented user experience, limited visibility and data integration, duplication of effort and rework
Four problem insights that framed the whole engagement.
The evidence base · 2020 research

Standing on Prior Research, Then Pressure-Testing It.

The Commission's 2020 personas and journey maps (employee, small business owner and union representative) were the starting evidence for who the portal serves and where the old journeys broke down.

Prior user personas from 2020: employee, small business owner and union representative, each with services sought, triggers and motivations
The 2020 personas set out who lodges, when, and why.
Prior user journey maps from 2020: employee, small business owner and union representative journeys with emotion curves and opportunities
Prior journey maps: where the old journeys hurt.
The problem · legacy lodgment

A Legal Process at a Stressful Moment, Split Across Downloads, Uploads and Disconnected Screens.

The legacy Online Lodgment Service asked applicants to download a form, fill it offline, then return to upload it, with fees, waivers and attachments handled on separate screens. Processing and scheduling was manual, driving up workforce effort behind the scenes.

Portal pain points: the old lodgment flow asked users to download the appropriate form, then pay or apply for a fee waiver
Legacy lodgment: download the form, then sort out fees before you even begin.
Portal pain points: the old F8C form split upload, document types and additional information across dense screens
The old F8C: upload, document types and extra detail split across dense screens.
Redesign a complex portal: prior to transformation, processing and scheduling of all lodgements was complex and manual, driving up workforce effort
Behind the scenes: processing and scheduling done by hand, matter by matter.
The structure · information architecture

One Map of the Whole Service.

The new portal's information architecture: login and account creation, dashboard, lodgments and forms, with the navigation, right-hand help panel and notifications mapped screen by screen.

Service portal information architecture: from landing page and login through dashboard, lodgments, forms and profile
One information architecture: login and account through dashboard, lodgments and forms.

In text: the portal branches from a landing page and login into a dashboard, then into lodgments, forms and a profile area, with global navigation, a right-hand help panel and notifications carried across every screen.

Shipped · MyFWC service portal

One Front Door for Everyone in a Workplace Dispute.

Claimants, respondents and representatives can draft forms, lodge applications and track progress on any device, without the paper. Designed end to end by one designer: research, journeys, high-fidelity UI and accessibility documentation at every step.

Final design: the Fair Work Commission service portal landing page, with account creation and lodgment types
The new front door: account creation and every lodgment type in one place.
The portal dashboard on desktop and mobile: draft forms, lodgments and apply-now cards under one Welcome view
The dashboard, desktop and mobile: drafts, lodgments and apply-now in one view.
Lodgments: searchable, filterable list of matters with payment status at a glance
Every matter searchable, with payment status at a glance.
Forms with filter and sort: my forms and start a new form on desktop, filter and sort panel on mobile
Filter and sort built to work one-handed on mobile.
F2 form submission step 2, then and now: the legacy multi-pane form beside the new guided six-step flow
Then and now: the same F2 step, redesigned as a guided flow with help in reach.
The craft · final design solutions

Four Fixes, Annotated on the Shipped Screens.

Usable navigation, status clarity, a clean interface and accessible support. Each fix visible in the final UI, from the desktop view-form screen to the six-step mobile form flow.

Final design solutions annotated: usable navigation, clean interface, status clarity and accessible support called out on the F8 view-form screen
Four fixes, called out on the shipped F8 view-form screen.
Final design solutions: the six-step new form flow on mobile, with step selector, inline validation and eligibility guidance
Six form steps, one thumb, and validation that explains itself.
Final design solutions. Responsive designs that enhance new features: review updates, join meetings, upload and download files from any device
Every feature on every device, conciliation details included.
The delivery · agile with the build team

Designed in Sprints, Supported After Launch.

Daily stand-ups, user stories per sprint, showcases to the FWC committee, then a two-week Hypercare period with Azure DevOps and telemetry before handover to the Commission's operational teams.

Agile delivery: documenting user stories and showcasing progress each sprint on the Azure DevOps board
User stories documented and showcased every sprint.
After delivery: final launch follow-up and future state management during the two-week Hypercare period
Hypercare kept issues monitored and resolved in real time after launch.

Then the Results Came In.

−30%Support request response times, for a legal process most users face exactly once.
<1 in 5Experienced a technical issue, and support call volumes fell after launch.

MyFWC portal user survey, 18–24 August 2025, the first pulse taken after launch.

Story two

Redesign the Service Behind It.

The portal is what the public sees. Behind it sat a conciliation service run on hand-offs, so the second half of the engagement redesigned the service itself, with a design objective of 75% straight-through processing.

Service design · scenarios & personas

Start With Who's in the Room, and What "Resolved" Means for Each.

Service scenarios and personas for unfair dismissal conciliation (applicants, respondents, case managers and conciliators) defined the future-state concept and scoped the proof of concept.

Design objective75%The design objective, in writing: three in four applications processed straight through, without human intervention.
Conciliation service design: future state concept with a design objective of 75% straight-through processing, plus scenarios and personas
Service design scenarios and UX journey mapping: conciliation scheduling and pre-conciliation resolution flows with user experience swimlanes
Scenario journeys: conciliation scheduling and pre-conciliation resolution, step by step.
Proof of concept co-designs: the customer portal dashboard and unfair dismissal application, co-designed for the future-state service
Proof-of-concept co-designs: the customer portal that tests the future-state service.
The transformation · current vs future state

From Fragmented to Connected.

Story one shipped the portal the public sees. This is the service behind it: the same matter, from intake to resolution, rebuilt so the manual hand-offs that slowed everything down become connected steps.

Service journey, from fragmented to connected: intake, categorisation, routing, scheduling and resolution, before and after
Five stages, two states.

And the detailed service blueprint the delivery teams built from: the same five stages, mapped screen by screen.

Service blueprints for unfair dismissal conciliation: fragmented current state above, connected future state below
Service blueprint: current state above, future state below.

In text: the fragmented current state runs on paper, phone, the old lodgment service and CaseHQ; the connected future state runs a single blueprint on a customer portal with rule-and-AI triage and one workflow.

When you're the only designer, every decision is yours to defend, so the evidence has to be airtight.