Never Finished. Always Tested.
Workday Testing Lessons from Sagrada Família
Introduction
A basilica that has been under construction for 144 years turns out to be a surprisingly good guide to Workday testing.
If you are in Barcelona for Workday Rising EMEA on 17 to 19 November 2026, you may visit Sagrada Família between sessions. Its slow, staged build holds five lessons in Workday testing best practices: model first, build in stages, keep the plan alive, stay open while you work, and keep going after each milestone.
You will get the five lessons, a worked example and a checklist to use when you are back at your desk.
Key takeaways
Long projects succeed through staged checks, not one big test at the end.
Test changes in a sandbox before production, as Gaudí tested forms with models before building.
Test in layers and write the plan down, so it outlives any one person.
Stay live while you build: a small regression set protects daily payroll, HR and finance.
A finished milestone is not the end, so rerun your checks after every release.
Why Workday testing best practices matter now
A building that is never “done”
Sagrada Família’s first stone was laid on 19 March 1882. On 20 February 2026, a crane lifted the final piece of the cross, its upper arm, onto the Tower of Jesus Christ, taking the basilica to its full height of 172.5 metres and making it the world’s tallest church. Yet the building is still unfinished, with work on the rest of the basilica expected to take about another ten years, according to AP coverage carried by SAN.
What Gaudí did first
Gaudí is widely known for working out structural forms with hanging string-and-weight models before committing to stone. The idea is simple: test the shape before you build it.
Your Workday tenant is the same
Workday is never finished either. Updates arrive through the year, your business changes, and new tools such as AI agents arrive. Many teams treat testing as a one-off project, when in practice it is a habit.
Why this matters before you leave Barcelona
Rising sends you home with long lists of features and ideas. The weeks after the event are when testing plans get decided. A short plan written on the flight home beats a big plan written in January.
Example: five lessons, five first actions
A people-systems team returns from Barcelona with plans to enable one new capability for a single region. Before touching production, the lead copies ten key processes into a sandbox and runs them. The team then checks each layer (data, security, approvals and integrations) against written pass marks.
The test cases go into a shared document, so any team member can rerun them. After the pilot goes live, they rerun a small set every week and calendar a full check for each Workday update. Two weeks later a configuration tweak breaks an approval route, and the weekly set catches it before payroll closes.
Lessons from Sagrada Família
Sagrada Família lesson | Workday testing practice | First action |
|---|---|---|
Model before you build | Workday sandbox testing before any production change | Copy your top ten processes into a sandbox and run them first |
Build in stages | Test in layers: data, security, approvals, integrations | Write a pass mark for each layer |
Keep the plan alive | Document test cases so knowledge outlives any one person | Store cases and results where the whole team can see them, then move repeat checks into Workday test automation |
Stay open while you build | Protect live operations with a small Workday regression testing set | Rerun it after every change |
A milestone is not the end | Retest after every update with Workday release testing | Put a check in the calendar for each release |
How PeopleFlow helps
Great buildings are checked as they rise, and great Workday tenants should be too. PeopleFlow brings Workday, Workday tools, data insights and HR technology expertise to teams on their digital transformation journey. Our no-code Workday testing includes 1000+ pre-built tests for HCM, Payroll, Finance and Integrations, so you can test in stages without writing scripts. Our Workday AI agents cover Configuration, Report, Support, Testing and Integration. See the Workday testing page and the AI agents page. PeopleFlow is a Workday Innovation Silver Partner.
Frequently asked questions
What are Workday testing best practices?
Test in a sandbox before production, test in layers (data, security, approvals, integrations), and write pass marks in advance. Keep a small regression set for live processes and rerun it after every change and every Workday release. Document results so the knowledge does not sit with one person.
How often should I test Workday?
Test before and after each Workday release and after any significant configuration change. Run a small core set more often, such as weekly, to catch issues early. The right rhythm depends on how often your tenant changes and how critical each process is, for example payroll or approvals.
What should I do after Workday Rising to put ideas into practice?
Within a week, turn your notes into a short list: what you may enable, who owns it, and how you will test it. Start with one pilot group, test in a sandbox first, and set pass marks. Share the list with your team so everyone knows the plan.
Why does Workday need continuous testing?
Workday changes through the year, and so does your business. New rules, entities, integrations and AI features can each affect processes that worked before. Continuous testing catches side effects early, protects payroll and finance, and reduces last-minute checking before each release.
Conclusion
Sagrada Família shows that big, lasting projects are built and checked in stages. Apply the same to Workday testing best practices: model first in a sandbox, test in layers, keep the plan written down, protect live processes and keep going after each milestone. Before you leave Barcelona, write down one thing to test first. When you are ready to start, try PeopleFlow yourself or book a short demo.




