---
title: "A/B Testing Employee Screens When Workday Is the System of…"
description: "How to try two employee screen layouts without splitting Workday business processes or storing who saw which one."
url: https://kiweely.com/blog/ab-testing-employee-ux-workday-system-of-record
---

# A/B Testing Employee Screens When Workday Is the System of Record

You can change a Leaf layout because Leaf stores layouts. You cannot send half the company through a different Workday process. The public page also stores no worker records, so a test that logs who saw which variant does not fit the design.

-   By Kiweely
-   November 16
-   2 min read

A/B testing a button label is harmless. A/B testing the business process behind the button is two different companies inside one tenant. Workday is the system of record for the election, the expense report, the time-off request, and the learning completion. Both versions of a screen have to submit that same process, under the signed-in worker’s own security.

[Kiweely Leaf](https://kiweely.com/leaf) (coming next) stores layouts, branding, and the tenant connection. It does not store worker records. The public page does not describe an experimentation product, a percentage rollout, or a report of who saw variant B. This is the room you actually have.

## What you may vary

Wording, order, and which fields are on the first view. Those live in the layout. Publish a layout to a non-production Workday tenant and watch one worker complete the real process there. Workday’s open enrollment notes say to test eligibility, dates, and deductions in non-production before you initiate. Use the same discipline for any screen that writes.

You can also limit who has the tile. Leaf shows published screens inside the company space. If only a pilot group’s Workday security can start the business process, everyone else gets an empty or forbidden result from Workday even if they open the tile. That is a pilot by permission, not a random split. It matches how you already roll out a business process.

## What you may not vary

Do not send half of open enrollment through a different event type, a different waive rule, or a SOAP replace that the other half does not use. Do not approve expenses in the screen for one group and through the Expense Report Event for the other. Outcomes would depend on which layout loaded, and Workday’s audit would show two procedures for one policy.

Do not record “this worker saw layout B” inside Kiweely if that record is tied to the worker. The published storage line excludes worker records. A test that needs that log belongs in a place your privacy review already accepts, or you skip the log and compare Workday outcomes you can already report: completion of the business process, time to submit, validation errors. Those facts are in Workday because the worker submitted, not because a screen assigned them a bucket.

| Test | Fits |
| --- | --- |
| New label and field order, same Workday process, tried in a non-production tenant | Yes |
| Tile visible, process startable only by a pilot security group | Yes |
| Two event types split by a coin flip | No |
| A vendor log of worker id and variant | Conflicts with storing no worker records |
| Built-in Leaf A/B product | Not on the public page |

When the non-production run looks right, publish that one layout for the company. The previous layout is what you [republish if you need to go back](https://kiweely.com/blog/versioning-rollback-ai-built-employee-screens). There is still no one-click rollback in the public description.

[Describe the screen](https://kiweely.com/leaf) you want to try first, and say which Workday process it must submit. Coming next.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 16 ### PEO and ASO Employee Apps on Each Customer’s Workday Tenant](https://kiweely.com/blog/peo-aso-white-label-employee-apps-customer-tenants)
-   [November 16 ### Multi-Brand and Franchise Screens on One Workday Tenant](https://kiweely.com/blog/multi-brand-franchise-leaf-spaces-one-workday-tenant)
-   [November 16 ### Vine, Nest, Bridge, Leaf, and Roots: One Workday Tenant, Five Jobs](https://kiweely.com/blog/vine-nest-bridge-leaf-and-roots-one-workday-tenant)

### More guides on Tenants and developer accounts

[All 25 guides](https://kiweely.com/guides#tenants)

-   [Is Kiweely free for a Workday personal developer tenant?](https://kiweely.com/guides/is-kiweely-free-personal-developer-tenant)
-   [Testing in a Workday Implementation: What’s Tested, by Whom, How Long, and What Can Be Automated](https://kiweely.com/guides/workday-implementation-testing)
-   [How Long Does a Workday Implementation Take? Workday’s Own Timelines by Scope](https://kiweely.com/guides/how-long-does-a-workday-implementation-take)
-   [Start a proxy test after an AI-suggested Workday change](https://kiweely.com/guides/workday-start-proxy-testing-after-ai-changes)
-   [When a Successful Payroll File Still Has the Wrong Tax or Garnishment](https://kiweely.com/guides/payroll-files-that-succeed-while-tax-and-garnishment-are-wrong)
-   [What Breaks a Workday Payroll File the Night Before Pay](https://kiweely.com/guides/what-breaks-a-workday-payroll-file-the-night-before-pay)
-   [Separating Production and Sandbox Workday Endpoints So Demos Miss Live Workers](https://kiweely.com/guides/separate-production-and-sandbox-workday-endpoints)
-   [Employee Screen Languages Without Changing the Tenant Default](https://kiweely.com/guides/localization-beyond-one-language-without-tenant-default)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
