Strategy
Risk & Dependencies
Integration hotspots, dependency chains, and the risk heatmap. Identifies where transformation risk is concentrated and what mitigations are in place.
Why this matters
Risk visibility determines whether the programme mobilises with appropriate safeguards. Unidentified dependencies are the primary cause of programme delay in transformation initiatives.
What this informs
Migration sequencing, contingency planning, and Phase 1 scope constraints. Every critical risk maps to a decision or deliverable dependency.
What remains unresolved
Cost estimation risk cannot be fully assessed until future-state scenario is selected. China regulatory timeline carries external dependency.
Total Risks
8
Critical
2
High
3
Domains Affected
6
Mitigations Defined
8
Legacy integration brittleness during migration
Facade layer isolates new components. Incremental migration with rollback capability at each stage. Integration test suite before each cutover.
Dealer network adoption lag for new service interfaces
Progressive rollout by region. Dealer feedback loop built into Phase 1. Training programme. Dual-interface period during transition.
Data sovereignty non-compliance in China operations
Parallel China architecture track. Independent data storage. Legal review of all cross-border data flows. ICP licensing ahead of deployment.
Cost estimation accuracy for future-state scenarios
Order-of-magnitude ranges, not point estimates. Scenario-based costing. Vendor pricing validated against reference implementations. Contingency buffer defined.
Vendor lock-in through monolithic platform selection
Composable architecture preference. API-first contracts. Avoid proprietary data formats. Exit cost analysis in vendor evaluation.
Organisational resistance to domain-driven boundaries
Stakeholder alignment workshops. Domain ownership mapped to existing reporting lines where possible. Executive sponsorship for boundary changes.
SAP upgrade cycle misalignment with migration timeline
Early alignment with SAP team on upgrade roadmap. Integration layer absorbs API version changes. Feature-flag migration phases around SAP releases.
Insufficient observability in transitional architecture
Observability as day-one requirement. OpenTelemetry standard. Monitoring dashboard for all integration touchpoints. Alert thresholds defined before go-live.
Legacy integration cutover sequence undefined
blockingCannot begin migration without validated system interaction map and rollback procedures.
China CAC assessment timeline
at-risk45–60 working day lead time. Must be initiated before Phase 1 planning is finalised.
Cost estimation blocked by scenario selection
blockingOrder-of-magnitude estimates require scenario lock. Steering committee decision prerequisite.
Integration Dependency Chain
Shows cascading dependencies between systems and the impact of failure at each integration point.
DraftArchitecture Lead
Data Flow Reliability Map
Data freshness, sync frequency, and reliability indicators across all integration paths.
DraftSolution Architect
Decision Layer
Decisions Supported
ADR-001 (strangler-fig), ADR-005 (observability). Risk profile supports incremental migration over big-bang.
Dependencies
Depends on DEL-001 (Current-State). Feeds into DEL-006 (Deprecation) and Phase 1 contingency planning.
Next Actions
Complete dependency chain diagram. Validate mitigation owners. Quantify cost-of-delay for top 3 risks.
Confidence
Medium — all risks identified and scored. Mitigation activation depends on decisions not yet resolved.