Skip to content
andres@andresclavijo.comResume (PDF)  (opens in a new tab)LinkedIn  (opens in a new tab)

Simplifying Payroll

Hourly's payroll confirm-and-run screen with its summary panel, on a desktop monitor.
  • Review → Runevery payroll is reviewed and confirmed before money moves, so fewer manual errors
  • 94%customer retention, with ease of use among what customers value most

In short

Redesigning a high-stakes financial workflow so business owners can review, calculate, and run payroll with confidence. In minutes.

Overview

Payroll is the highest-stakes action in Hourly, a workforce management and payroll platform for SMBs with hourly workers. Business owners are committing significant funds and need accuracy, clarity, and confidence before they submit.

Timeline
2023
Role
Product Design Director · Strategy & Execution
Hands-on
Research, the UX goals and the web flow changes. Delegated, reviewed and approved the iOS and Android designs.
Partnered with
Product on business definitions, Engineering, and the stakeholders who approved the designs

The Problem

The existing payroll experience created friction and uncertainty at the worst possible moment. Users didn’t know what was included in the payment, feared making irreversible mistakes, and had no clear visibility into what was happening between calculation and submission. The result was anxiety, errors, and support tickets on the most time-sensitive action in the product.

Users ranged from tech-savvy HR leads to business owners with minimal digital experience. Top concerns from research: not knowing what’s included in the payment, fear of making irreversible mistakes, and needing a sense of control before money moves. The existing flow provided none of these.

Flow diagram of the original payroll run, each step flagged with a problem: calculation with no visibility into what is included, a review screen where the numbers are unclear, and a submit with no confirmation.
The original run, step by step. Every step left the user unsure what was included or whether it worked.

The Thinking

High-stakes financial workflows fail when users can’t tell what’s about to happen or confirm that it did. That was the core insight. Each step needed to do one job and signal clearly that the job was done before the next step opens. I partnered with engineering and compliance early to map every technical constraint and regulatory requirement into the interaction design, rather than treating them as handoff problems to solve later.

Before and after comparison of the payroll run. After adds an overview and summary up front, reviewable calculated values, a confirm and run modal, and a processing state that ends in explicit success.
Before and after: each new step does one job and confirms it's done before the next one unlocks.

The Solution

An intuitive guided flow: payroll overview, trigger calculation, review calculated values, confirm and run modal, confirmation dialog, processing animation, success state. Each step was designed to eliminate a specific anxiety. Duplicate submissions, unclear amounts, accidental triggers, and uncertainty about whether money actually moved.

The payroll dashboard listing pay periods down the left with their amounts and paid status, beside an employee table showing hours and net amounts.
Step one, the overview: every pay period with its amount and status, next to the people being paid.
The Confirm and run modal: delivery option, shipping address, payment method and pay date on the left, with a summary panel showing the debit date and a total of 1,664.05 dollars next to a Run Payroll button.
The confirm step: the debit date and the total sit next to the button that moves the money.
The processing state, showing a spinner and a Processing Payroll message over the dimmed payroll table so the run is never ambiguous.
Processing is a visible state, so no one wonders whether the run went through or clicks twice.

Impact

After launch, manual errors and duplicate submissions went down: every run now goes through an explicit review and a confirmation before money moves, so customers run payroll on purpose and with confidence, not by accident. Customer retention on the platform holds at 94%, and in surveys and feedback interviews customers name the app’s ease of use among what they value most. Business owners described the payroll flow as “the reason we stay.”

The result handled complex backend processes, pay cycles, off-cycle runs, tax payments, and bank transfers, while feeling simple to the person running it. That gap between backend complexity and front-end clarity was the whole design problem.

Reflections

Designing this flow taught me that interaction design for high-stakes workflows is inseparable from the engineering and compliance constraints underneath. The best decisions came from bringing those teams into design reviews early, not at handoff.

I’d also invest more in error and edge-case states from the start. We prioritized the happy path in early iterations and retrofitted edge cases later. That created rework. For financially critical flows, the edge cases are the product.

More case studies

Case study The Hourly Design System

Hourly · Ongoing since 2018 · One system feeding web, iOS and Android

Case study Multiple Pay Schedules

Hourly · 2026 · Several pay schedules per account, shipped on web and mobile