Go live readiness for RISE.

The RISE with SAP go live event is the most operationally consequential moment in the conversion programme. The conversion either lands on the planned cutover weekend with the business operating cleanly inside the new environment, or it lands with a list of issues that the support team and the business operations team work through across the first ninety days. The difference between the clean go live and the messy go live is the readiness framework that the buyer applies in the six weeks before the cutover. This article describes the readiness framework that the firm uses, identifies the five readiness dimensions, and describes the final go no go decision protocol that converts the readiness assessment into a single decision.

Cutover readiness and the dress rehearsal cadence

The cutover readiness dimension covers the technical sequence that moves the business from the legacy environment to the RISE environment over the cutover weekend. The sequence has typically between forty and one hundred discrete steps, with each step owned by a defined team and dependent on the preceding steps. The readiness assessment for the cutover dimension is based on the dress rehearsal cadence, with the rehearsal repeated until the sequence completes within the planned window with no critical issues.

The dress rehearsal cadence has a defined minimum. Three rehearsals at full scope are the minimum that the firm requires before any go live is approved. The first rehearsal typically identifies issues that the planning did not surface. The second rehearsal validates the fixes against the issues from the first. The third rehearsal demonstrates that the sequence completes cleanly inside the planned window. Programmes that go live with fewer than three full scope rehearsals consistently encounter cutover issues at the event, with the issues compounding because the team has not built the muscle memory for the sequence.

The cutover window itself has to be sized against the realistic rehearsal data, not against the optimistic plan. A cutover sequence that runs for thirty six hours in rehearsal will likely run for forty eight hours in production, because the production environment introduces variables that the rehearsal environment does not replicate. The contingency margin against the rehearsal time has to be at least twenty five percent, with the margin documented and reserved at the cutover plan.

Data readiness and the reconciliation protocol

The data readiness dimension covers the migration of the legacy data into the RISE environment and the validation that the migrated data matches the source. The migration is technically straightforward in most cases. The validation is the property that determines whether the go live is data ready. The reconciliation protocol is the buyer side discipline that runs the validation, and the protocol has to be in place before the cutover weekend, not invented during it.

The reconciliation protocol has three layers. The first layer is the volumetric reconciliation, which confirms that the record count in the source matches the record count in the destination, with the variance reported by entity. The second layer is the financial reconciliation, which confirms that the financial totals in the source match the financial totals in the destination, with the variance reported by account. The third layer is the operational reconciliation, which confirms that the key operational records in the source match the operational records in the destination, with the variance reported by record type.

Across the firm engagement base, the data readiness dimension is the most frequent cause of go live delay. The delays arise when the reconciliation protocol surfaces variances that the cutover team cannot resolve inside the cutover window. The variances typically result from data quality issues in the source that the migration did not anticipate. The mitigation is to run the reconciliation protocol against a full data extract at least four weeks before the cutover weekend, with the variances resolved in the source environment before the cutover.

Integration readiness and the end to end test

The integration readiness dimension covers the inbound and outbound interfaces between the RISE environment and the surrounding application landscape. The interfaces are typically the most underestimated component of the conversion, because they cross organisational boundaries and depend on third party systems that the conversion team does not control. The readiness assessment for the integration dimension is based on the end to end test, with the test exercising each interface against a defined transaction profile.

The end to end test has to cover every interface, every transaction type, every error path, and every reconciliation point. The test has to run at production volume, with the volume sustained for a defined duration to surface the performance issues that lower volume tests miss. The test has to be repeated until the failure rate falls below the agreed threshold, typically zero critical failures and less than five percent non critical failures.

The integration readiness is the dimension that the buyer side team has to own most directly. The SAP delivery team owns the SAP side of each interface. The buyer side team owns the surrounding landscape and the third party systems that connect to the interfaces. The coordination between the two sides is the property that determines whether the integration testing surfaces the issues early or late, and the coordination has to be operationalised through the programme steering committee well before the cutover window.

Business change readiness and the user adoption signal

The business change readiness dimension covers the user training, the process documentation, the operational handover, and the user adoption signal. The dimension is often the dimension that the technical team treats as secondary, and it is the dimension that the business operations team treats as primary. The readiness assessment has to bridge the two perspectives by measuring the user adoption signal against a defined threshold.

The user adoption signal is measured through three indicators. The first is the training completion rate, with the target set at ninety five percent of the affected user base completing the training before the cutover. The second is the sandbox usage rate, with the target set at the users completing a defined number of sandbox transactions in the four weeks before the cutover. The third is the user confidence survey, with the target set at the user base reporting a confidence level above an agreed threshold. The three indicators together provide the adoption signal that the go live is business ready.

Support readiness and the hypercare posture

The support readiness dimension covers the operational support posture during the first ninety days after the go live. The posture is typically referred to as hypercare, with the support team staffed at elevated levels and the response times accelerated against the steady state SLAs. The readiness assessment for the support dimension is based on the hypercare staffing plan, the escalation protocols, the incident tracking, and the war room readiness.

The hypercare staffing plan has to include the buyer side support team, the SAP delivery team, the SI partner team, and the hyperscaler team. The plan has to define the shift pattern across the relevant geographies, the escalation thresholds at each level, and the handover protocol between shifts. The plan has to be tested in dress rehearsal alongside the cutover sequence, with the rehearsal exercising the incident response protocols rather than just the technical steps.

The final go no go decision protocol

The final go no go decision is taken at the executive steering committee meeting that is held one week before the planned cutover. The decision is binary. Go and proceed to cutover. No go and defer to the next planned window. The decision is taken against the five readiness dimensions, with each dimension assessed against the defined threshold and the combined assessment producing the recommendation.

The decision protocol requires that all five dimensions are at green or amber, with no dimension at red. A red dimension triggers an automatic no go, regardless of the assessment on the other four. An amber dimension triggers a documented risk acceptance, with the mitigation plan documented and the residual risk acknowledged at the executive steering committee. A combination of more than two amber dimensions triggers an extended discussion, with the no go option taken seriously rather than rationalised away. The discipline of the protocol is the property that prevents the optimistic go live decisions that consistently lead to messy go live events.

Closing position. Readiness is the discipline that lands the cutover

The RISE go live event is the moment at which the months of preparation either pay off in a clean cutover or surface in a list of issues that the support team works through across the first ninety days. The five readiness dimensions and the go no go decision protocol convert the readiness assessment from a subjective judgement into a structured discipline. The discipline is the property that distinguishes the conversions that land clean from the conversions that land messy. The clean landings are not a function of fortune. They are a function of the readiness framework applied with operational rigour in the six weeks before the cutover. The discipline is the property that the firm consistently installs on every conversion engagement, and it is the property that the senior CIOs increasingly require before any go live is approved.