UX / UI · mroads · 2 months · shipped to production
A multi-client timesheet SaaS for a consulting firm, designed and shipped. On-time submissions rose 25% and QA errors dropped 20% in the first quarter after launch.
[ 01 · The brief ]
Nobody resents timesheets. They resent friction.
Consultants at the firm were logging hours across several clients, and submissions were consistently late and error-prone. The existing flow asked people to remember structure they did not hold in their heads.
The design goal was to reduce the number of decisions per entry, not to add reminders.
[ 02 · Process ]
What I did
- Shadowed consultants through a full weekly logging cycle to find the abandonment points
- Restructured entry around client and project selection first, then time
- Designed a confirmation and submission state that makes completeness obvious at a glance
- Built the component set and handed off with QA annotations
“On-time submissions up 25%. QA errors down 20%. First quarter after launch.”
Measured outcome, production
[ 03 · Findings ]
What moved the number
Most late submissions were not procrastination. They were people stalling on an ambiguous field and closing the tab. Removing ambiguity in selection removed most of the delay.
The confirmation screen did more for QA errors than any validation rule, because it let people catch their own mistakes before submitting.
[ 04 · Outcome ]
What changed
The product is live and in daily use across the firm. Both headline numbers came from the client after the first full quarter of operation.
The cheapest usability win is almost always removing a decision, not adding a nudge.
Reflection