← back

user test systems in workday

operations · workday · hagerty · 2017 — 2023

every time workday's sandbox environment refreshed, the hr systems team had to manually rebuild a full set of demo employees for training and testing. the process took hours, was inconsistent across team members, and delayed training sessions. i designed an automated workflow that replaced all of that manual setup.

workday sandbox environments refresh periodically, wiping out test data. before each training session, someone on the team had to manually create demo employees — entering names, job profiles, org assignments, compensation data, and benefits elections by hand. every person did it slightly differently.

the result was inconsistent test data, wasted hours, and training sessions that sometimes started late because the environment wasn't ready. other teams that relied on the sandbox (compensation, benefits, recruiting) had no visibility into whether test data was current or accurate.

i started by documenting the existing manual process — what data was being created, in what order, and what assumptions each team member was making. this surfaced inconsistencies: different people used different naming conventions, skipped certain fields, or created employees in configurations that didn't match real-world scenarios.

from there, i designed a standardized workflow within workday that automated the creation of a complete, consistent set of demo employees after every sandbox refresh. the workflow covered the full employee lifecycle — from hire through job changes, compensation, benefits enrollment, and termination scenarios.

i also built documentation and trained the team so the process would hold up without me maintaining it.

setup time hours → minutes
data consistency 100% — same every time
teams supported hr, compensation, benefits, recruiting
sandbox refreshes covered all
training delays eliminated

this wasn't a glamorous project. nobody outside the hr systems team would ever see it. but it solved a real problem that was costing hours every month and causing downstream frustration for multiple teams.

it also reinforced something i keep coming back to: the best systems work is often invisible. the goal isn't a process people admire — it's a process people don't have to think about at all.

workday process automation systems design cross-team coordination documentation