ADP Workforce Now & TeamPay

ADP was in the middle of a strategic corporate transformation. The mandate from the top was to shed the identity of a back-office processing company and reposition as a design-forward technology enterprise. The vehicle for that transformation was the Visual Design Language, a unified design system built by ADP's Global Design Team to standardize components, typography, color, and interaction patterns across the company's entire product ecosystem.

The problem was the ecosystem itself. ADP Workforce Now had grown over decades by acquiring and stitching together smaller platforms. The result was an interface that worked, but had accumulated years of inconsistent UI patterns, dense data entry forms, and multi-step workflows built on top of each other. TeamPay, dominant in the Canadian market, was the other end of the spectrum: a highly reliable, transactional payroll tool built for speed and exactness, where users navigated almost entirely by keyboard and whitespace was treated as wasted screen real estate.

Applying a modern design language to either product meant working against the grain of how their users actually operated. An HR administrator running payroll for 500 employees had built muscle memory around every form field and data grid. A design change was not cosmetic from their perspective. Moving a button or adding padding to a table row was a real disruption to a workflow they ran every week.

As a UX Designer on the product team, I worked across both Workforce Now and TeamPay, translating VDL patterns into production-ready designs for my assigned areas:

• Reporting dashboards — applying the VDL's card and charting language to WFN's reporting and analytics surfaces
• Payroll grids — adapting the data density of payroll entry and approval workflows to meet VDL standards without degrading the speed and scannability that power users depended on
• Onboarding flows — redesigning multi-step employee setup and registration flows within the VDL framework
• Forms and compliance — updating data entry forms across both platforms, including year-end tax workflows and compliance-sensitive screens where field validation behavior had to remain intact throughout any visual change
• Stakeholder alignment — using prototypes and demos to build internal support for changes in areas where users and stakeholders questioned the need for redesign

Day-to-day work covered wireframing, interaction specs, and annotated handoffs to development, with occasional direct collaboration on technically constrained areas.

The hardest constraint was not technical. It was philosophical. The VDL was built on modern web principles: clean whitespace, generous padding, readable type scales. Those are the right choices for most interfaces. They are the wrong default for a payroll grid where a user needs to see 40 employee rows and six columns of financial data on a single screen without scrolling.

Every area required a negotiation. How much padding is enough to satisfy the VDL's legibility requirements without costing the user the row density they need? Where can components be updated to match the new design language without triggering revalidation of the tax calculation logic running underneath them? The answers were never universal. They were worked out screen by screen, with the VDL as the target and the user's operational reality as the constraint.

Getting internal sign-off on changes in areas where users were resistant required showing the work in motion. Prototypes and interactive demos consistently moved stakeholders who would not have approved static redlines. Seeing a redesigned payroll workflow behave exactly like the existing one, just cleaner, addressed the fear of disruption more directly than any written rationale.

Outside the core product work, ADP gave designers time for independent exploration. I used mine to prototype mobile versions of core Workforce Now and TeamPay flows, a direction that leadership in 2016 largely viewed as peripheral. The prevailing assumption was that no one would run a corporate payroll or process tax compliance on a smartphone.

The prototypes argued the opposite: that while a payroll administrator might live on a desktop, a manager on a warehouse floor or a construction site needed real mobile capability, not a watered-down dashboard. Approving a timecard, checking a schedule, or authorizing a payroll adjustment were tasks that happened away from a desk. The demos made the case by showing what that actually looked like in practice.

The full realization came after I had left. ADP Mobile Solutions eventually grew to support tens of millions of active users globally and became a central pillar of the company's product strategy, consistently rated 4.7+ stars on both major app stores. The manager-facing capabilities that drive significant engagement today — timecard approval, team scheduling, payroll authorization on the go — directly reflect the use cases those early prototypes were built to demonstrate.