Sedgwick WorkforceOne
A full-scale redesign of the platform powering 8,000+ claims examiners — unifying two legacy systems into a modern, scalable workforce experience.
Role:
Senior Product Designer
Tools:
Figma
Duration:
1.5 Years · 2023–2025
Team:
Inspire11
2x
Productivity Increase
for First 1,000 Users
50%
Reduction in
Onboarding Time
8K+
Claims Examiners
on the Platform
$60M
Projected Business
Value Delivered
Context
One of the world's largest
claims firms. One unified platform.
Sedgwick manages claims at a scale few organizations match — operating across industries and jurisdictions with thousands of examiners processing complex, high-stakes cases daily. Their internal tooling hadn't kept pace. Two siloed legacy systems created fragmented workflows, redundant data entry, and steep onboarding curves for new examiners.
WorkforceOne (WF1) was the initiative to change that — a comprehensive internal platform overhaul designed to consolidate the experience, modernize the UX layer, and fundamentally improve how examiners manage tasks, schedules, documentation, and communication across claims.
As Senior Product Designer, I owned UX and UI end-to-end across nine epics — from requirement gathering and working sessions through process flows, prototyping, QA testing, and final handoff — embedded directly with Sedgwick stakeholders and the Inspire11 program team throughout.
The Problem
Two legacy systems with overlapping functionality, forcing examiners to context-switch constantly — slowing case resolution and driving up onboarding complexity.
The Goal
A unified, modern platform that consolidates scheduling, task management, documentation, and communication into a single, scalable experience.
My Scope
UX and UI across key epics — including Work Schedule, Communication Hub, and the shared visual design system — in close collaboration with product owners, developers, and stakeholders.
The Challenge
Designing for complexity at enterprise scale
The WF1 platform had to serve dozens of distinct roles — from front-line examiners to managers and administrators — each with different workflow needs, permissions, and mental models. Claims workflows are inherently complex: multi-party, highly regulated, and high-stakes.
The design challenge wasn't just visual modernization. It was building a system flexible enough to accommodate that complexity without exposing it — interfaces that felt clear and direct to an examiner handling 50+ cases a day, while still supporting the full depth of edge cases underneath.
That meant disciplined information architecture, modular component thinking, and constant collaboration with business stakeholders to prioritize what mattered most for the rollout.
Key Contributions
The experiences I led and shaped
Epic · Scheduling
Work Schedule Tool
A dynamic scheduling interface supporting four schedule types and a robust pattern builder. Designed to balance simplicity with depth — handling time-off requests, flexible arrangements, and manager overrides in a unified, intuitive view.
Epic · Correspondence
Communication Hub
Consolidated correspondence flows into a centralized secure message center — with filtering, threading, and quick response patterns that replaced a fragmented, multi-system communication experience.
Foundation · Design System
Visual System & Component Library
Built reusable components and patterns in Figma using auto-layout and variants — the shared library that allowed the development team to scale consistently across all WF1 epics without design drift.
Design Screens
A look at the finished work
Design System
Components built for speed and consistency
One of the highest-leverage contributions on a project this size is the design system itself. On WF1, I worked closely with Chad Sparks to build and maintain the Figma component library — auto-layout components, comprehensive variant sets, and shared token-based patterns that the full team relied on.
Investing in this foundation early meant that as the platform scaled across epics and new feature areas, consistency was built in — not retrofitted. Developers could build faster, and design reviews moved more quickly because there was a shared visual language everyone understood.
Outcome
Measurable impact, platform-wide
The initial rollout to 1,000 users doubled their measured productivity and cut onboarding time in half — concrete evidence that the redesign wasn't cosmetic. WF1 is now the active operational backbone for over 8,000 claims examiners, with a projected business value of $60M+.
The work reached the executive level. Sedgwick's CIO publicly discussed the platform's impact, citing it as a transformational initiative for the firm's operations. A company-wide launch video — designed to onboard all 8,000 employees — was part of the rollout strategy Aaron helped shape.
Beyond the numbers, the team heard it directly from users. The consolidation of scheduling across claim types, real-time access to claim IDs, and persistent column preferences — details that sound small — were the changes that drove the loudest positive response from examiners who had been working around the old system for years.
“OMG, I am so in LOVE! This is so much better — I love that we can see everything we need in one place now!”
“No more flipping back and forth! We can enter and update schedules seamlessly across claims, and having the claim number is a game changer.”
“The detail, layout, and streamlined experience are amazing! Being able to save column preferences — users are obsessed!”
Reflection
What this project sharpened
01
Complexity demands clarity, not simplification
You can't ignore enterprise workflow depth — you have to meet it and organize it. WF1 forced me to develop a sharper instinct for what to surface, what to abstract, and where to let the system breathe.
02
Client collaboration is a design skill
Active participation in working sessions — not just presenting outcomes — accelerated alignment and built the kind of stakeholder trust that keeps complex projects moving. Design influence is earned in the room, not in the file.
03
Design systems are a velocity investment