Summary
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.
Body
This article provides the standardized Lessons Learned template to complete after a Workday project or change request goes live. Capturing lessons learned supports transparency, continuous improvement, and better planning for future work.
Print Version: Print Version of Lessons Learned Template
Section 1: Project Information
| Field |
Description / Example |
| Project Title |
Name of the Workday project or change request |
| Functional Area |
e.g., Human Capital Management (HCM), Finance |
| Project Lead |
Name of BPM Project Lead |
| Business Analyst |
Name of assigned BPM Analyst |
| Functional Partner(s) |
Central HR, Budget, Payroll, etc. |
| Go-Live Date |
MM/DD/YYYY |
| Date of Review |
MM/DD/YYYY |
Back to Top
Section 2: Project Objectives & Results
| Question |
Response |
| What were the original objectives of this project or process change? |
|
| Were these objectives achieved as planned? |
|
| What measurable results or improvements were observed post-go-live? |
|
| Did the project meet stakeholder expectations? |
|
Back to Top
Section 3: Successes
| Area |
Description |
Impact / Benefit |
| Project Management |
What went well in project planning, scheduling, or coordination? |
|
| Collaboration & Communication |
What team practices or communication methods were effective? |
|
| Testing & Implementation |
Which steps in the testing or deployment process worked best? |
|
| Stakeholder Engagement |
What approaches successfully gained stakeholder buy-in or feedback? |
|
Back to Top
Section 4: Challenges
| Area |
Description |
Impact / Resolution |
| Process or Scope |
Were there unclear requirements or scope changes? |
|
| Configuration / Technical |
Were there unexpected configuration or system issues? |
|
| Testing / UAT |
What testing challenges or delays occurred? |
|
| Communication |
Were there gaps in communication or documentation? |
|
| Resource or Timeline |
Did staffing, workload, or deadlines impact progress? |
|
Back to Top
Section 5: Recommendations for Future Projects
| Category |
Recommendation |
Priority (H/M/L) |
Owner / Responsible Party |
| Process Improvement |
|
|
|
| Communication |
|
|
|
| Training / Documentation |
|
|
|
| Project Management |
|
|
|
| Technical / Configuration |
|
|
|
Back to Top
Section 6: Follow-Up Actions
| Action Item |
Assigned To |
Due Date |
Status |
Notes |
| |
|
|
☐ Not Started ☐ In Progress ☐ Complete |
|
Back to Top
Section 7: Sign-Off
| Role |
Name |
Signature / Date |
| Project Lead |
|
|
| Functional Lead |
|
|
| BPM Director |
|
|
Back to Top