The next Workday Feature Release is just around the corner. Now is as good a time as ever to dust off your release management best practices. This ensues you take advantage of not only the mandatory but also optional features to get the most out of your Workday investment.
Here are some top tips that can help both IT admins and leaders avoid the most common pitfalls when managing Workday feature releases.
1. Planning approach to manage Workday feature release
Workday delivers release features every spring and fall. This gives the opportunity to take advantage of many new features and functionality.
It’s a good idea to develop a project plan, establish timelines and secure additional resources that may be needed to support the feature releases in areas like user acceptance testing. This is essential if the updates occur during business-critical periods such as annual enrollment, performance or merit cycles. Don’t get caught underestimating the overall project management time and coordination efforts to review release notes. Complete an impact analysis on enhancements, properly test updates, and execute a thorough change management and communication plan.
Make sure your subject matter experts (SMEs) are actively involved in the release management team. Trust us, they’re important to the overall success. They’re responsible for thoroughly reviewing mandatory features (within their areas of expertise) to identify potential impact. Their participation in regression testing is a good way to avoid downstream impacts too.
Without the proper planning, resources and tools available to support this twice a year effort, the task at times can seem daunting and often times organisations just do the bear minimum, failing to take advantage of the newest optional features and functionality or properly regression testing their current set up. This can leave you at risk for falling behind in uptaking features or introducing issues into your tenant.
2. Information is key to success
You have access to a great resource, the Workday Release Center, located in the Release Information drop-down menu on the Workday Community home page, the Center is updated for each release. It covers all release-related communications and materials. We understand reviewing this information and then determining the impacts to your specific business is a lot to tackle in a small window of time. We encourage you to identify resources to be focused on this activity and have them available the week the ‘What’s New Release’ notes are released. Take the time to plan in advance as it is a lot of information to digest and you don’t want to overlook key features or fail to communicate to stakeholders due to lack of time to review.
Resources available to you include:
- Welcome to Workday—highlighting key enhancements and adoption tools
- Feature release guidebook—release planning resources
- Solution catalog—best practice tips submitted by community members
- Product dashboards—aggregate information for specific features, functions and products
- Documentation—the Workday Administrator Guide, Workday’s official documentation site
- Uptaking features in weekly service update—instructions for the review and uptake of new features * Service update notes—new enhancements by product area
- Features still in the works—enhancements soon to be delivered
- What’s new videos—feature details by product management
- Customer alerts—official notifications about verified issues
- Ideas delivered—client-submitted ideas that have been incorporated into the release
- Ideas available in preview—client submitted ideas available in preview
- Trending questions—frequently asked questions about the current release
3. Test and test again
Save time and reduce your risk by identifying baseline test scenarios for each feature release ahead of time. This allows you to reuse the test plans and cases and helps ensure crucial scenarios are functioning correctly. Use test plans from past implementations or major Workday initiatives. This can identify critical or common scenarios to test in the new-feature release.
It can take a lot of preparation, we know. So, at the very least, focus your new release planning and testing efforts on:
- Running and reviewing output from critical integrations
- Validating existing system data
- Testing critical business processes and critical custom reports
With a Workday update, it’s not only important to understand and test all the new functionality, but also assess impacts to current functionality. This can be accomplished with regression testing of current key processes and functionality. Workday provides resources to help build the planning and testing framework needed to ensure a successful release. potential impacts within their domain and build the test plan accordingly. Utilising an automated regression tool can be a great asset to reduce testing time and improve quantity of test scenarios executed,
Also, if you are using Workday Payroll, we recommend a payroll be processed to ensure results are as expected.
4. Communicating to embrace change
All of your end users need to key know what’s happening in Workday and how changes impact their work activities. Keeping them posted with clear messaging and providing updates on changes will not only help avoid confusion but also give line of sight to all the great new features and functionality that are being provided with each release. Make sure to get credit for the work being put into the Feature Releases by communicating them to your stakeholders!
5. Mandatories first, optional features later
Walk before you run. Wait a few weeks after the release has been in production before implementing optional features. But don’t forgot to revisit them! This way, you can really gather intelligence to focus on exactly what is needed to improve the functionality of daily activities for your end users and processes affected by the feature changes.
When in doubt, ask a partner for support!
Strada has rolled out a new ongoing service to support our clients to ensure they stay up to date with their ongoing release management needs. Focusing not only on ensuring staying on top of the impact analysis and regression testing required with the mandatory features, but also providing change management tools, weekly release notes, and support of optional features, Strada’s Release Updater allows you to make release management a year round focus.
Recommended roles to support release features
We recommend assigning the following roles:
High-level recommended timeline
| Six weeks out | Five weeks out | Three weeks out | One week out | One week post go-live |
| Prepare for release | Identify scope | Configure and test | Client sign off | Post go-live monitor |
| Identify resources | Review release notes and impacts of mandatory changes against client-specific tenant configuration | Complete required tenant configuration | Complete final testing | |
| Kick off project | Identify any optional features recommended for later adoption | Complete testing and resolve defects and issues | Communicate to users | |
| Review session with client stakeholders | Update training materials and documentation | Conduct training | ||
| Present required tenant updates |
