- Never had one to begin with (please don’t tell us you’ve been using Excel for all of your HR needs!)
- Aren’t happy with your current solution
- Want to move to SaaS* (software as a service)
- Need more software functionality
Get excited because you are ready to embark on a Workday® implementation! Use this guide to get an idea of how the process works and get valuable tips for a successful go-live.
Whether you are going live with Workday® for the first time or this is one of many times you’ve deployed Workday® products, as with most things, careful preparation before you begin an implementation is key.
A Workday® implementation is typically completed in six phases: plan, architect, configure, test, deploy, and support.
During the architect phase, the team will need to determine the Workday® framework and build the foundation, or initial, tenant. In order to determine what the proper framework should be, you’ll hold SOP (standard operating procedure) sessions, or business process sessions. This is where you and your team will discuss business processes and define Workday® requirements.
During the configure phase, specific modules are built out within Workday® and the tenant is configured to meet your organization’s needs. For example, if you use a software for Payroll, an integration must be built to ensure that both systems communicate correctly. In customer confirmation sessions, the functionality is presented and stakeholders will give confirmation that the project is on the right track.
During the testing phase, the team will test the software to confirm that it meets the expected requirements and is free of bugs or defects.
Testing occurs in multiple phases. Some phases include unit testing, end-to-end testing, and parallel testing.
Want to learn more about testing?
Read about our Workday® testing approach.
This is where the magic happens! After a blackout period*, your new Workday® tenant is deployed. This will typically take place on a weekend for minimal business disruption.
*What is a blackout period? Typically two weeks or more before going live, you’ll enter a blackout period, where no changes can be made to the data within your software. This ensures a seamless transition.
Data is extracted, cleaned up, and moved from legacy systems to Workday®.
Integrations are built to ensure that other systems you use communicate correctly with Workday®.
Change can be overwhelming and is oftentimes met with reluctance. Communicating change as it relates to Workday® early, often, and clearly is important. A team should be in place to facilitate the change from start to finish.
Check out our change management white paper to learn more about our approach.
Similarly, the proper training builds a strong foundation, empowering employees to navigate and utilize the new system effectively once live.
A Workday® implementation can take anywhere from 8-18 months.
The following are the signs of a Workday® deployment done right: