ReadyWorks Implementation Project High-Level Process

For Rollout Planning and General Project Management of a ReadyWorks deployment, incorporating workshops, formal documentation, and structured sign-off processes ensures a clear, collaborative approach to implementation. By involving workflow and technical teams early and consolidating insights into a Configuration Guide and user work instructions, the deployment can proceed with well-defined requirements and clear, actionable guidance for end-users.

Key Considerations for Rollout Planning and Project Management:

1. Establish Clear Project Phases and Milestones:
   • Define Major Phases of Deployment: Structure the rollout into phases, including requirements workshops, initial configuration, testing, pilot deployment, and full launch. Phasing the project provides manageable checkpoints, allowing for early identification and resolution of issues.
   • Set Specific Milestones and Deliverables: For each phase, define milestones (e.g., workshop completion, configuration sign-off, pilot success). These milestones keep the project on track, create accountability, and align the team with project goals.
   • Coordinate with Organizational Timelines: Align your ReadyWorks rollout with other key initiatives or business cycles to ensure resource availability. This avoids conflicts and supports a smoother implementation process.
2. Conduct Independent Requirements Workshops with Workflow and Technical Teams:
   • Organize Workflow Workshops: Engage workflow teams in workshops to document and align on operational needs, business rules, and specific workflows that ReadyWorks will support. Identify critical workflows for automation, such as asset tracking, updates, or compliance checks, ensuring alignment with business processes.
   • Hold Technical Workshops for System Integration: Collaborate with technical teams to outline data integration requirements, define technical dependencies, and address any security or compliance needs. Document key details such as data mapping specifications, API requirements, and staging table structures.
   • Engage Corporate Communications for Communications Design: Engage your Corporate Communications partners early to ensure that any templated e-mail communications to be sent to your end-user community align with language and branding required in your organization.
   • Document Workshop Outcomes for Sign-Off: Capture all workshop outputs, including workflow designs, integration requirements, and any automation needs, in a requirements document. Obtain sign-off from both teams to validate the documented requirements, ensuring alignment before moving to configuration.
3. Create a Consolidated Configuration Guide for ReadyWorks:
   • Document your Configuration Guide prior to Starting Implementation: Based on the identified requirements, create a Configuration Guide that documents ReadyWorks settings, workflows, data mappings, user roles, and permissions. This guide serves as the blueprint for the deployment and supports consistent configuration across environments. This document should be compared against the platform’s Configuration Report that documents all settings within the instance.
   • Review with Certified ReadyWorks Configuration Specialists: Once documented, review the setup of key ReadyWorks components with your Certified Configuration Specialist to ensure alignment across teams.
4. Develop Comprehensive ReadyWorks User Work Instructions:
   • Create Role-Based Work Instructions: Based on the Configuration Guide, develop work instructions for each user role, covering day-to-day operations, specific workflows, and common tasks. Tailor instructions to address the core actions each role will perform in ReadyWorks, such as updating asset details, initiating requests, or viewing compliance reports.
   • Organize Live and Self-Paced Training: Conduct training sessions tailored to each role and provide supplemental resources such as video tutorials, quick reference guides, and FAQs. For extended teams, ReadyWorks recommends the use of Just-in-Time training.
   • Prepare Support Teams for Common Issues: Train helpdesk teams on ReadyWorks functionality for end-users to resolve minor issues effectively. This is critical when considering an outbound integration with an ITSM tool like ServiceNow.
5. Plan for Technical Environments and Testing:
   • Establish Separate Development, Testing, and Production Environments: Ensure you have a ReadyWorks’ environment setup to isolate configuration and testing from live data. This ensures thorough validation without impacting the production environment.
   • Conduct User Acceptance Testing (UAT): Develop test cases for each use case or workflow. Involve a small group of friendly end-users to do a shakedown test prior to engaging in full scale UAT. Be sure to document any changes for traceability.
   • Define any Rollback and Contingency Plans: Prepare rollback procedures to revert to stable configurations in case of critical issues in the case you are extending an existing ReadyWorks deployment. This ensures minimal disruption during the rollout and supports quick recovery.
   • Identify a Roll-Over Plan: Determine how you will transition to the newly orchestrated workflow supported by ReadyWorks. Identify a clean break-point in your operations where the new process can be implemented.
6. Develop and Execute a Communication Plan for End-Users:
   • Communicate with the End-User Community: Prepare end-users for the rollout by outlining the benefits of ReadyWorks, any required actions, and the support resources available. Use TCOMMs (Triggered Communications) within ReadyWorks to automate notifications and updates throughout the rollout.
7. Finalize Go-Live Criteria and Readiness Checks:
   • Set Clear Go-Live Criteria and Obtain Final Sign-Off: Define and document the specific conditions required for go-live, including successful testing, configuration sign-off, and readiness of support resources. This checklist ensures all essential elements are in place before launching ReadyWorks.
   • Conduct Final Readiness Assessments: Schedule a go-live readiness review with stakeholders and project team members to confirm all elements, from workflows to user support, are fully prepared for launch.
   • Select Optimal Launch Timing: Choose a go-live date that minimizes business disruption. For large organizations, consider a phased go-live across different user groups or regions, reducing the initial support load and allowing for a controlled, gradual adoption.
   • Schedule Regular Review and Enhancement Cycles: Plan periodic reviews to assess ReadyWorks’ alignment with evolving organizational requirements. These reviews help the implementation team make necessary adjustments, ensuring long-term platform relevance and performance.
8. Create a Configuration Report to Marry with the Configuration Guide:
   • Generate a Configuration Report: This ReadyWorks generated report is a readout of the configured settings in your environment. This serves as a contrast to the design. Analyzing both is a good lessons learned to review and understand why changes were made from the design and how that will be rectified in the future.
   • Maintain Detailed Change Logs: In regular operations, record all changes to ReadyWorks configurations, data mappings, workflows, and other customizations in a change log. This supports troubleshooting, ensures continuity, and helps future team members understand the project’s history.
   • Conduct Knowledge Transfer to Operations Teams: Following rollout, formally hand over ReadyWorks management to operational teams. Knowledge transfer sessions should cover platform maintenance, monitoring practices, and protocols for handling future enhancements.

By incorporating workshops, formal documentation, and structured sign-off processes, the Project Manager can ensure a well-coordinated, efficient deployment of ReadyWorks. This approach establishes clear requirements, aligns with organizational goals, and supports a seamless transition to ReadyWorks, empowering teams with the tools and knowledge needed for ongoing success.