Go-live is where most Workday programmes are declared a success. It is also where the people who built the system leave. This whitepaper is a playbook for the twelve months that follow, written for organizations running Workday for the first time.
Go-live is a handover
During implementation the partner holds the knowledge: why a business process has five steps, why a security group exists, what was traded off in the design workshops. Unless that knowledge moves to your own team, every later change starts with a discovery exercise.
Owning the system means being able to answer “why is it configured like this?” without a statement of work.
What to keep, what to outsource
The useful line does not run between tasks. It runs between decisions and labour.
Keep in-house
- Process and policy decisions
- The security and role model
- Priorities in the backlog
- The verdict on each release: adopt, wait or ignore
Can be outsourced
- Configuration work
- Integration build and monitoring
- Regression test execution
- Report building to your specification
The first twelve months
- Months 0 to 3: stabilise.Hypercare, a single intake for issues, and a weekly decision meeting that HR owns rather than attends.
- Months 3 to 6: your first release.Workday ships feature releases twice a year. Run the first one as a rehearsal: read the notes, assess the impact, test, decide.
- Months 6 to 9: optimise.Work through the backlog that built up during implementation, starting with what managers and employees complain about most.
- Months 9 to 12: take stock.Review the ownership model, the skills in the team and the support contract against what the year actually required.
Five signs you don't own your system yet
- Nobody in HR can explain why a process is configured the way it is.
- Every change request goes to the partner by default.
- Release notes are read after the release, not before.
- Reports are requested, never built.
- The backlog is a list without an owner.
We measure success by how little you need us after go-live.
In the full whitepaper
- An ownership model with roles for an HR systems team
- A release calendar and checklist
- Questions to ask an application-maintenance partner
- A twelve-month plan you can adapt to your own programme
Sample summary, written to show the format. Aim-Up replaces or edits it, and adds the whitepaper file, before launch.