HomeProjectsSelf-Service Access and Role Management

BENEFITS / ENSURANCE SAAS

Self-Service Access and Role Management

Replaced a manual workflow with a centralized, self-managed platform; cutting processing time by 72%.

Benefits enrollment workflow and dashboard preview

Year

2025

Role

Senior Product Designer (Growth & Monetization)

Client

Paychex & Flock

72%

Reduction in processing time

500+

Employees self-managed

3 mo

End-to-end design & delivery

Overview

Structure

Team Members

  • Product Owner
  • Program manager
  • Business analyst
  • Researcher
  • Dev team (12)
  • UX manager
  • UX Lead
  • UX/UI designer
  • Service architect
  • Scrum master

My Role

  • User Research
  • UX/UI Design
  • Product Thinking
  • Narrative

Tools Used

  • Jira
  • Miro
  • Webex
  • Outlook
  • Copilot
  • Hotjar

Timeline

3 months

Case Study

The Problem

Internal users couldn't change users' roles and permissions on their own, which increased support tickets and development work.

Manual workarounds wasted users' time and increased the risk of costly errors.

Each unsupported enrollment request took 5-7 business days and was multiplied across hundreds of clients.

Supporting signals

Adding new employees required support tickets and manual development effort.

Data needed to be collected, validated and sent across teams. Changes were tracked through emails.

No centralized governance or clear permission structure.

Task

Design a self-service enrollment experience that reduced support dependency, clarified permissions, and fit the product's existing operational model.

85%

of HR teams reported enrollment errors

3 weeks

average time to complete enrollment cycle

40%

of employees confused by their benefits

User Research

Spoke directly with platform users to understand their pain points, day-to-day workflow, and where the experience was creating friction.

Pattern Alignment

Balancing the product's existing patterns with user needs without disrupting the experience.

Role Mapping

Mapped internal roles, governance rules, and permission boundaries before UI implementation so the system would support real operational needs.

Flow Validation

Validated the enrollment lifecycle against exceptions, support scenarios, and admin edge cases before moving deeper into delivery.

Cross-Team Review

Worked closely with product and engineering to keep the experience coherent while aligning with system constraints and delivery pressure.

Actions

Methodology

1. Empathize

User interviews & stakeholder sessions

2. Define

Problem framing & pain point mapping

3. Ideate

Flows, architecture & wireframing

4. Prototype

Hi-fi screens & interactive prototypes

5. Test

Post-launch Hotjar analysis

Definition

Design Strategy

Define the underlying architecture and logic before changing the UI.

Find what parts of the system work well and build around those.

With no design system, collaboration with the development team ensured the forward-facing UI remained cohesive throughout.

Solution

The Platform

The dashboard below is an interactive example — click the tabs to explore the User Accounts and Roles & Permissions views.

ClientsUsersReportsFormsBilling
Settings

User Accounts

Manage platform access, account status, and assigned permission roles.

Add User
Search by name, role, or branch
NameRoleBranch LocationSign InStatusActions

Hanks, Tom

tomhanks@mail.com

Benefits AdminCompanySep 12, 2022Active···

Pons, Tamara

tamarapons@mail.com

Reporting & Form AdminCompanyInvitation sentInvitation pending···

Laczko, Billie

laczkobillie@mail.com

BillingCompanyAug 24, 2022Active···

Davila, Ryan

davilaryan@mail.com

Benefits AdminCompanyAug 19, 2022Active···

Smith, Ava

avasmith@mail.com

Forms ManagerCompanyJul 28, 2022Active···

Chen, Mia

miachen@mail.com

Payroll ViewerCompanyJul 11, 2022Active···

Reyes, Mateo

mateoreyes@mail.com

Reporting AdminCompanyInvitation sentInvitation pending···

Walker, Noa

noawalker@mail.com

Benefits AdminCompanyJun 30, 2022Active···

Validation

Results

Metric
Before
After
Change
Processing time
Manual, multi-step support workflow
Centralized self-service flow
72%
Access request handling
IT tickets and manual role assignment
Governed self-service and faster approvals
-78%
Authorization error rate
Email-based coordination and unclear permissions
Centralized role model with clearer access rules
-41%

Outcome Signals

35%

Security incidents

Fewer unauthorized access incidents after centralizing role governance and access control.

4.6/5

User experience improvements

Positive internal feedback on ease of access, navigation, and role clarity inside the platform.

100%

Compliance and audit

Audit-ready role structure and clearer permission ownership across supported user types.

+18%

Authentication success rate

Improved successful access outcomes after clarifying permissions and reducing friction in account setup.

32%

Cost-benefit analysis

Lower support effort tied to manual account changes, access requests, and user administration tasks.

8.9/10

Security team feedback

Strong qualitative confidence from internal stakeholders in the updated access model and control patterns.

Outcomes

Impact

Following the rollout of the redesigned self-service workflow, product, support, and security reporting showed improvements in operational efficiency, access clarity, and compliance.

OutcomeResult
Processing time72% reduction after centralizing request, approval, and role-assignment workflows
Self-service adoption500+ employees able to manage standard access tasks independently
Unauthorized-access incidents35% reduction through clearer role governance and access controls
Authentication success18% increase after reducing setup friction and clarifying permissions
Support effort32% reduction in effort related to manual account changes and access requests
User experience rating4.6/5 from internal user feedback on access, navigation, and role clarity
Security-team feedback8.9/10 rating for the updated access model and control patterns
Compliance readiness100% of supported roles had a documented owner and audit-ready permission structure

Measurement period: Post-launch product, support, and security reporting. Metrics reflect the released self-service access and role-management workflow.

Learnings

Architecture before UI

Investing time in mapping the permission model before designing screens prevented costly rework. The logic had to be airtight before any pixel moved.

Trust through constraints

Working without a design system forced tight collaboration with engineers. Constant syncs kept the UI cohesive and the handoff smooth even under timeline pressure.

PaychexIBX

NDA notice: Parts of this presentation,including some screens and project details,have been redacted or blurred due to a confidentiality agreement signed with the client. The work shown is real; full details are withheld to protect client privacy.

Tools

JiraMiroWebexOutlookCopilotHotjar

Tags

BENEFITS / ENSURANCE SAASUX ResearchIAInteraction DesignDesign Systems

More work

Other Projects