Anoop V
Case 01 · UX Writing

The app wasn't broken.
The language was.

HR365 TalentPro had working features and confused users. I audited the language and proposed the rewrites that would close the gap.

ProductHR365 TalentPro
RoleUX Writer + Critique
YearApr to May 2024
ScopeMicrocopy, visualization, tone
The Fix

Three rewrites that did the most work.

Each one solves a real moment of user confusion the team had been getting tickets about.

Fix 01 · Salary screen
Killed the donut chart. Surfaced the answer.
Before · Original screen
HR365 tablet salary screen with donut chart
1
2
3
1
"Salary Summary": names the screen, not the answer. No net pay anywhere.
2
Donut chart with overlapping % labels. Users have to do mental arithmetic to find their take-home.
3
Line items buried below: the actual data is below the fold on a tablet.
The #1 user complaint. A chart that asked users to do work the system should have done.
After · Rewritten
11:28July 2023 · 2023-24
Your Salary Breakdown
July 2023 · paid 1 Aug
3
Net pay: what you received
₹ 32,000
Credited · A/C ending 4471
Summary
Earnings
Deductions
Earnings · 4 components
Basic Pay
Core fixed salary
₹ 20,000
House Rent Allowance
HRA · tax-exempt up to limit
₹ 4,000
Dearness Allowance
DA · cost-of-living adjustment
₹ 3,000
Special Allowance
Variable monthly
₹ 5,000
Title renamed to "Your Salary Breakdown". Net pay ₹32,000 surfaced first. Linear list with context hints. Every line speaks for itself. No chart needed.
Fix 02 · Dashboard
Group by frequency. Lead with what users do daily.
Before · Original screen
HR365 tablet dashboard original layout
1
2
3
1
Welcome card takes 20% of width and enables nothing. Pure decoration.
2
Clock In / Out controls have no confirmation state. Users tap and don't know if it registered.
3
Seven services at equal weight. Leave Balance and Birthday Buddies look equally important.
No priority signal. The thing users open the app to do every morning had no visual hierarchy.
After · Mobile redesign
11:2844% ▣
Good morning, Rohan
Sat, 26 Oct · Clock in to start
T1 Do this first · Today
TAP TO CLOCK IN
Start your day
Location shared securely
Clock In →
T2 This week
Leave
14 left
Team
3 out
Holidays
2 Nov
T3 Social & updates
◉ Announcements
◉ Birthdays
◉ Anniv.
◉ Wedding
Three tiers, visually distinct. Tier 1 = the daily action (Clock In) gets a green hero card with confirmation state. Tier 2 = weekly tiles with live data. Tier 3 = social, visually quieter.
Fix 03 · Side menu
Separated destructive actions from daily nav.
Before · Original menu
HR365 side menu mixing nav and destructive actions
1
2
1
"Hide all seen events": sounds like deletion. No confirmation copy.
2
"Clear Attendance" sits next to Dashboard at the same weight. No warning, no recovery hint.
Destructive actions and daily nav at the same visual weight, with no warning and no separation.
After · Three zones
R
Rohan Kapoor
Research Manager · ID C-001
Clocked in 9:15 AM14 leave left
Navigate
⌂ Dashboard
◔ My Profile
Preferences
✓ Mark all notifications as read
⚐ Language & Region
⚠ Account actions · handle with care
⟲ Reset attendance cache
You'll be asked to confirm.
⎋ Sign out
Three labelled zones. Destructive actions get a red-bordered "Account Actions" zone with a confirmation hint baked into the label.
Fix 04 · CTAs across the app
Every button that asked "submit what?" got a verb and an outcome.
Before
Submit
After
Save your details
Verb + object. Implies the action is reversible.
Before
Earnings Pie Chart
After
Your Salary Breakdown
Names the answer, not the chart container.
Before
[ Silent after Clock In ]
After
You're clocked in. Have a great day, Rohan.
Confirms, names the user, and adds warmth in eight words.

Four shifts. Every word lined up against one of them.

01
Technical language
Human language
02
Data display
Data understanding
03
System silence
Confirmation & warmth

UX writing isn't about making interfaces sound better.
It's about making systems understandable.

HR365 had the features. The data was accurate. The app failed because it expected users to interpret raw output without help, and that's a writing problem, not an engineering one.