This article defines the four types of projects used by the BPM team: Core, Strategic, Operational, and Future Optimization. Each type is explained with its effort level, focus, and examples to support consistent classification and prioritization. A comparison table and visual diagram are included to help stakeholders quickly distinguish between project categories.
This article outlines the standardized discovery process for HCM projects at the University of Arkansas. It defines roles and responsibilities, details each discovery phase and planning session, and provides fillable templates with field explanations to ensure consistency, compliance, and stakeholder alignment across all project initiatives.
This guide provides a standardized framework of default milestones and timeframes for managing both change requests and full projects. It outlines key phases—from intake and discovery to testing and post-implementation review—to ensure consistent tracking, communication, and delivery across all project types. The model supports efficient planning, transparency, and progress reporting within the Business Process Management lifecycle.
This article explains the purpose and importance of project plans for Workday business process enhancements. It outlines when to use the Initial Version (during intake and early analysis) and the Full Version (after discovery and scope validation). Project plans support alignment, communication, and successful implementation across teams.
a template for a Business Process Change Request document that captures all the necessary details about a process change, including security roles, responsibilities, the order of review (swim lanes), document attachments, questionnaires, and security role adjustments. This structure will allow the requester to be clear about what they need and help streamline the approval and implementation process.
The Go-Live Checklist ensures all critical activities are completed before a Workday configuration or process change is promoted to production. It provides a structured way for the BPM team to verify readiness, confirm approvals, validate documentation, and coordinate communication across stakeholders. By completing the checklist, teams ensure a smooth transition to production and maintain accountability for each step in the implementation process.
The Lessons Learned Template provides a consistent structure for capturing key insights at the conclusion of a BPM project. It promotes reflection, continuous improvement, and documentation of recommendations that strengthen future initiatives.
The Project Decision Document provides a standardized framework for recording key decisions made throughout the lifecycle of a BPM project or Workday optimization initiative. It ensures that rationale, stakeholders, and impacts of each decision are clearly documented for transparency, accountability, and future reference. This KBA includes a draft layout of the decision document to guide teams in capturing consistent and well-structured decision records.
This article provides an overview of the Workday Project Closure document used for all Workday projects at the University. It formalizes the end of a project by summarizing the project’s objectives, results, and any outstanding items or actions. The document includes a final evaluation of project success, captures stakeholder feedback, and obtains necessary approvals.