Implementation Milestones and Deployment Timeline
Vickers: In May 2021, we signed the contract and selected a partner, Invisors, to help with the Workday implementation and Workday to help support the Workday PSA rollout from a design and product point of view. We started with Workday Financial Management first in July 2021—including accounts payable, general ledger, procurement, and assets—because we wanted to look at the accounting and make sure we had our base levels set up correctly.
We also started with financials because we knew HCM and PSA were going to be the biggest pieces and we had over 200 integrations between them. We needed a lot of time to work on those. With phase one, we went live in May 2022. It took less than a year, which we thought was pretty good.
We partnered with Invisors to help identify pain points of our phase two work, which was a huge reason why this second phase was a big success. It level-set Invisors on who we were and our pain points, and that clarified how we wanted to approach the architecture sessions as we went into the implementation.
We had two customer confirmation sessions. The second one became a focus group session, which was important for us because it helped us get buy-in. We brought together 80 owners, partners, principals, and employees in Chicago for two sessions. We gave them fixed scenarios that they ran through right after our first session.
We got feedback immediately from our end users on what worked and what didn’t. And thankfully there was a lot more that worked than didn’t, but it highlighted what we needed to work on before we got too far into the implementation.
The people in the focus groups became our change agents and helped us understand what our employees needed for the go-live. We used them for decisions and for bouncing ideas. For example, we didn’t go live with one revenue recognition option because we got the feedback that we’re not ready for it. And that was important.
Performance Testing
Stephanie Lai: We began performance testing in November 2022, which included setting baselines and identifying the initial set of issues.
We worked together with three types of stakeholders: RSM, Workday services, and the Workday product and development team. Typically in a scenario like this, we first have to understand the problem. We talked to our services folks, who are on the ground and really understand the problem, use cases, and creative solutions. They could assess any identified functional gaps.
And then once we understood some of those gaps, we engaged with our Workday product and development team to help create a solution prototype for RSM review.