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 (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 |
|---|---|
| TestNew label and field order, same Workday process, tried in a non-production tenant | FitsYes |
| TestTile visible, process startable only by a pilot security group | FitsYes |
| TestTwo event types split by a coin flip | FitsNo |
| TestA vendor log of worker id and variant | FitsConflicts with storing no worker records |
| TestBuilt-in Leaf A/B product | FitsNot 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. There is still no one-click rollback in the public description.
Describe the screen you want to try first, and say which Workday process it must submit. Coming next.