Contributed by Mark Anderson
As we shared recently, our intent with reporting and analytics is to provide all the day-to-day reports you need to do your job on day one of go-live (read more in this article). So what will the Reporting & Analytics team be doing between now and July of 2022? We'll be assessing user needs, evaluating delivered reporting functionality from Workday, as well as building and testing the reports that you'll need on Day One.
Here's a further breakdown of the team's strategy between now and go-live:
- Assess Current State Reporting Landscape: understanding stakeholder and business needs, developing a comprehensive list of key stakeholders and conducting discovery sessions, gathering information on current reporting needs, developing a roadmap for reporting and analytics and supporting technology solutions.
- Evaluate Delivered Reporting Capabilities: gathering information on current capabilities and challenges, evaluating Workday's delivered functionality for reporting and analytics, evaluating user experience and interface design considerations, and evaluating planned data security configuration.
- Define Reporting Scope, Level of Effort, and Prioritization: finalizing full reporting inventory with stakeholder input, documenting business and functional requirements, documenting future state support model including scope and governance, and finalizing report development schedule.
- Build, Test, Deploy, and Change Management: building, testing, and deploying reports, delivering training to end-users, and implementing the future state support model.
UVA has extensive reporting requirements. As our team has worked with functional areas to gather up their needed operational reports, we've collected 360 to date. Grants management alone has 74 required reports!
In an upcoming update, I'll share more on the Workday Reporting & Analytics toolset, including dashboards, discovery boards, worksheets, Prism Analytics, and more -- so stay tuned.
No comments
Post a Comment