Strategy
Risk & Dependencies
Integration hotspots, dependency chains, and key blockers across current and proposed architecture. Scored by impact and likelihood to inform sequencing constraints.
Why this matters
Unmitigated risks will delay or derail the transformation. This register quantifies exposure and maps dependencies that constrain sequencing.
What this informs
Deprecation sequencing, Phase 1 scope constraints, and the steering committee risk appetite conversation.
What remains unresolved
Dependency chain mapping incomplete. Dealer adoption risk requires field validation. Cost accuracy risk blocked by scenario selection.
Total Risks
8
Critical
2
High
5
Domains Affected
6
Mitigations Defined
6
Risk Heatmap — Impact × Likelihood
Legacy integration brittleness during migration
Façade layer isolates new components. Incremental migration with rollback capability at each stage. Integration test suite before each cutover.
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.
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.
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.
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.
Integration Dependency Chain
Critical path dependencies between systems. Highlights single points of failure and cascade risks during migration.
DraftArchitecture Lead
Data Flow Reliability Map
Data freshness and reliability across integration touchpoints. Flags where eventual consistency may affect business operations.
DraftSolution Architect
Key Blockers
Cost estimation depends on scenario selection
Blocks: DEL-009 — High-Level Platform Cost Estimate
China data sovereignty assessment not initiated
Blocks: DEL-007 — China Architecture Annex
SAP upgrade roadmap not confirmed
Blocks: ADR-006 — SAP retention decision
Decision Layer
Decisions Supported
ADR-001 (strangler-fig), ADR-004 (China track). Risk profile shapes sequencing and scope constraints.
Dependencies
Risk profile informs deprecation sequencing and Phase 1 scope definition. Blocks DEL-005 completion.
Next Actions
Complete dependency chain mapping. Define risk appetite thresholds with steering committee.
Confidence
Low-Medium — heatmap populated but dependency chain and dealer adoption risk require further validation.