How a microcopy overhaul — and a set of annotated redesigns — transformed a confusing HR payroll app into a system users could actually understand.
Context
HR365 (TalentPro) manages employee salary, attendance, and HR operations for corporate users. The features worked. The language around them didn't. Users were lost — not because the product was broken, but because it never told them what anything meant.
User Signals
These weren't hypothetical pain points. They were direct signals from users trying — and failing — to understand their own financial data.
Salary details are confusing. I can't tell what I actually received versus what was deducted.
Salary ClarityHard to understand deductions. The numbers are there but I don't know what they mean or why.
Deduction VisibilityNavigation is not clear. Too many options — no idea which one I actually need.
Navigation OverloadDiagnosis
Each issue operated at system level — not screen level. Fixing one wouldn't fix the experience. All four needed to shift.
04 — Core Insight
Every piece of data was present. Every feature existed. But none of it communicated. The gap was not functionality — it was language.
Approach
Execution · 01 — Salary Visualization (Tablet)
This was the #1 user complaint. The screen showed data accurately — but made users mentally decode it before they could understand anything.
Red markers on the real TalentPro tablet screen. Each one points to a piece of UX that asks users to do work the system should have done for them.
Hi-fidelity mockup of the redesigned screen. Same data, reorganised so the system answers the question users actually bring to this screen: “What did I earn this month?”
Redesign mockup built in HTML/CSS · not a real product screenshot
Execution · 02 — Dashboard Navigation (Tablet)
7 features. No priority. No grouping. The most time-critical daily action — Clock In — competed visually with Birthday Buddies and Wedding Anniversary at identical weight.
Markers on the real screen show exactly where the hierarchy breaks down — from the decorative welcome panel to the undifferentiated service grid.
Three visual tiers — Tier 1 (daily critical), Tier 2 (weekly), Tier 3 (social). Each one looks different. Users can tell at a glance what's urgent and what's optional.
Redesign mockup built in HTML/CSS · not a real product screenshot
Execution · 03 — Side Menu Panel (Tablet)
The slide-out menu mixed personal identity, navigation, data utilities, and settings at the same visual level. No section separation. No warning language on irreversible actions.
Every row in this menu has the same visual weight — whether it opens a safe profile page or wipes attendance data. Users have no signal that some taps are consequential.
The same features, grouped by risk and intent. The destructive zone is visually distinct and the labels include what actually happens before the user taps.
Redesign mockup built in HTML/CSS · not a real product screenshot
Execution · 04 — Mobile Dashboard Navigation
On tablet, feature overload is frustrating. On mobile, it causes task abandonment. The phone version compounds every dashboard hierarchy problem into a single viewport with no room to recover.
The real mobile dashboard — annotated. Notice the attendance card with no confirmation state, the missing greeting, and the flat service grid where social and functional features collide.
The same priority system as the tablet redesign, compressed for a phone viewport. The morning clock-in action becomes unmissable. Social features shrink into a pill row.
Redesign mockup built in HTML/CSS · not a real product screenshot
Execution · 05 — Mobile Salary Screen
On a phone, the chart takes half the viewport to deliver less information than the list below it. The fix is simpler than it looks: remove the chart, promote the list, add a total.
The chart is gone. The net pay is the first thing users see. Every earnings line stays, with a short context hint underneath so users who aren't payroll-literate understand what each component is.
Redesign mockup built in HTML/CSS · not a real product screenshot
Microcopy
Microcopy isn't about tone. It's about removing the cognitive work users shouldn't have to carry.
System Framing
Four shifts in how the product communicates — not what it shows, but how it speaks.
Impact
This was a UX writing and critique engagement. Impact is measured in clarity — not dashboard numbers.
10 — Key Takeaway
HR365 had all the features. The salary data was accurate. Attendance tracking worked. The app didn't fail because it was broken — it failed because it assumed users could interpret raw output without guidance. The intervention wasn't cosmetic. It was structural: every label, CTA, section title, and status message is a decision about how much cognitive work users have to carry. This project was about putting that weight back on the system, where it belongs.