Back to all work

UI/UX Design · Employee Expense Claim

Making a complex product more user-friendly

EEC is a financial platform for managing expenses and payments. The existing UI was not user-friendly, making navigation confusing and financial data hard to understand. Our goal was to improve usability, clarity, and consistency across web and mobile platforms.

Role
Senior UI/UX & Product Designer
Skills
UI/UX DesignUser ResearchFocus GroupWireframesPrototypingUsability Testing
EEC before redesign: dense, cluttered dashboard EEC after redesign: clean, scannable dashboard Before After

Drag to compare: from dense layout to clean overview

The Problem

Cluttered & confusing

Users struggled with several critical pain points: cluttered layouts made navigation difficult, poor visual hierarchy confused priorities, navigation paths were confusing, and financial data was hard to read.

Research & Insights

Understanding user needs

I reviewed competitor platforms and conducted focus groups with potential users to identify patterns and opportunities.

01

Information Overload

Too much information at once feels overwhelming and reduces confidence.

02

Lack of Clarity

Clear labels and simple layouts are crucial for user trust.

03

Data Comprehension

Visual summaries help users understand financial data faster.

Discovery & Research

Two very different users, one form

Employee Expense Claim has two audiences pulling in different directions: the employee who wants to submit fast, and finance who wants clean, policy-compliant data. Research had to hold both.

Note on confidentiality: these are internal enterprise platforms. Due to company data policy, full working files, raw research data, and complete dashboards can't be published here. The previews below use illustrative, non-production data to represent the structure, format, and thinking behind each deliverable.

Persona: Farid Hassan

Research
Farid HassanTraveling Sales ExecutiveSubmits claims weeklyUses mobile appReceipt photo reliance

Represents the frequent traveler who submits expense claims from the road, often against tight reimbursement deadlines.

Persona: Nadia Rashid

Research
Nadia RashidFinance ApproverReviews claims dailyCross-checks policy limitsComfort with tech

Reviews and approves claims daily, and needs policy violations flagged before she has to catch them manually.

Persona: Kevin Lim

Research
Kevin LimTeam Lead, Second ApproverApproves team claims weeklyReviews for budget impactComfort with tech

Second-level approver who checks claims against team budget, usually in batches at the end of the week.

Persona: Aisha Karim

Research
Aisha KarimHR / Payroll CoordinatorProcesses reimbursements biweeklyHandles escalationsComfort with tech

Processes approved claims into payroll runs and fields escalations when reimbursements are delayed.

Proto Persona: Finance Approver

Research
Finance Approver (proto)ASSUMPTION-BASED · LOW FIDELITYNeed: review and approveclaims in bulk within policyFrustration: chasing missingreceipts one claim at a time

Early-stage assumption persona used to frame the approver side of the workflow before interviews.

Proto Persona: First-Time Claimant

Research
First-Time Claimant (proto)ASSUMPTION-BASED · LOW FIDELITYNeed: understand what'sclaimable before submittingFrustration: policy rules areburied in a PDF nobody reads

Assumption persona for employees submitting their first claim, before onboarding research was done.

Proto Persona: Regional Finance Auditor

Research
Regional Finance Auditor (proto)ASSUMPTION-BASED · LOW FIDELITYNeed: spot-check claims forpolicy complianceFrustration: no audit trail isvisible inside the tool

Used to frame compliance requirements ahead of interviews with the regional audit team.

Proto Persona: Remote Employee

Research
Remote Employee (proto)ASSUMPTION-BASED · LOW FIDELITYNeed: submit claims from thefield without a scannerFrustration: mobile photouploads often get rejected for

Assumption persona representing field staff without office access, pending remote-user research.

Empathy Map

Research
SAYS"Why is this stillpending?"THINKS"Did I lose thatreceipt already?"DOESPhotographs receiptsimmediately to avoidlosing themFEELSFrustrated by slowapproval turnaround

Synthesized from interviews with 12 employees and 4 finance approvers.

Stakeholder Map

Research
ProductEmployeeApproverFinance OpsHRAudit & ComplianceITDirectInfluencing

Distinguishes the people directly using the claim flow from those governing policy around it.

Affinity Diagram

Research
SUBMISSION"Too many fields""Camera qualityissues"APPROVAL"No visibility onstatus""Escalationunclear"POLICY"Limits not shownupfront""Currencyconfusion"

Raw research notes clustered into themes during a synthesis workshop, surfacing the patterns behind user pain points.

Design Approach

Simplicity & consistency

Simplified Layouts

Removed clutter and streamlined interfaces for cleaner, more focused experiences.

Visual Hierarchy

Established clear information hierarchy to guide users through critical actions.

Consistent Navigation

Unified experience across web and mobile with predictable navigation patterns.

Redesign

Transforming cluttered data into clear, actionable information

Key improvements: removed 40% of non-essential elements, improved information hierarchy with better spacing, added visual indicators for key metrics, streamlined action paths from 5 to 3 steps, implemented consistent component design, and enhanced mobile responsiveness.

Journey & Flow

Following a claim from receipt to reimbursement

I traced the full lifecycle of a claim, from capture to submission, approval, and payout, to find where employees stalled and where approvers got stuck waiting on missing information.

Journey Map

Journey
Capture receiptFill formSubmitAwait approvalReimbursed4.5

End-to-end emotional curve across the expense submission journey, from first touch to task completion, mapped against satisfaction (1–5).

Service Blueprint

Journey
FrontstageBackstageSupport Systems

Frontstage actions, backstage operations, and supporting systems mapped against each other to expose handoff gaps.

User Flow

Journey
CapturereceiptCategorizeWithinpolicySubmitApproverreviewPaid

Primary task flow through the product, including key decision points and drop-off risk areas.

Testing & Results

Validation through user testing

Faster Task Completion

Users completed core tasks significantly faster with the redesigned interface.

Fewer Errors

Navigation errors and misclicks reduced dramatically with clearer visual cues.

Improved Usability

Users rated the redesign as clearer and easier to use in qualitative feedback.

Outcome & Impact

From confusing tool to confident platform

The redesign transformed EEC from a confusing financial tool into an intuitive platform where users feel confident managing their expenses.

35%
Support tickets decreased
40%
Task completion time improved
User satisfaction scores increased

Impact

Current Achievements in DKSH

Scale and ownership across the Employee Expense Claim platform, from strategy through to delivery.

  • Redesigned the expense submission journey, cutting user effort by ~35%.
  • Streamlined the approval workflow across Finance and HR stakeholders.
  • Designed 20+ user flows and fully responsive interfaces.
  • Ran multiple stakeholder workshops to validate business requirements.

Strategy & Prioritization

Proving the redesign actually saved time

Because this was a process fix more than a feature build, every satisfaction and effort metric here is tracked as a before → after pair against the pre-redesign baseline.

VOC Dashboard

Voice of Customer
BeforeAfterReceipt upload friction14% (was 33%)Approval turnaround13% (was 30%)Policy clarity9% (was 24%)Currency conversion8% (was 19%)Notification gaps5% (was 14%)

Share of support tickets and feedback tied to each theme, before the redesign shipped versus today.

NPS Dashboard

Voice of Customer
38NPS SCOREwas 9-100100

Net Promoter Score moved from 9 to 38, made up of 51% promoters, 34% passives, and 15% detractors (n=340).

CSAT Dashboard

Voice of Customer
91%CSATwas 58%

Customer satisfaction climbed from 58% to 91% across 260 post-task survey responses.

CES Dashboard

Voice of Customer
"It was easy to complete my task"6.0/7was 3.3/7wasCUSTOMER EFFORT SCORE

Effort score improved from 3.3 to 6.0 out of 7 across 245 responses. Lower effort correlates with higher retention.

Prioritization Matrix

Prioritization
Big betsQuick winsMoney pitFill-insAuto OCR receiptsBulk approvalPolicy pre-checkMulti-currencyStatus notificationsOffline captureEffortImpact

Candidate initiatives scored on impact vs. effort to sequence the roadmap.

KPI Dashboard

Strategy
117/mo▲ was 180/moSupport tickets87%▲ was 69%First-timeapproval rate89%▲ was 51%Adoption4.4/5▲ was 3.1/5Policy clarityscore

North-star and supporting metrics compared against their pre-launch baseline to show whether the redesign is actually working.

Business Impact

Strategy
BeforeAfterSubmission time6.2m3.7mApproval cycle4.1d1.6dError rate11%4%

Operational metrics compared before and after launch to quantify the business case.

Executive Summary

Strategy
Cut expense claim cycle time by 40%Redesigned submission form reduced requiredBulk approval view cut finance team reviewRolled out with in-app policy guidance to40%Faster completion35%Fewer tickets38NPS

One-page leadership readout summarizing problem, approach, and measurable outcome.

Why This Works

By combining thorough user research with systematic design improvements, we transformed a complex financial platform into an intuitive experience where users understand their data and feel confident taking action, without sacrificing powerful features.