rweisssieker-xp AX Migration Change Adoption
Purpose
Convert migration scope into business readiness work. Focus on role impact, process change, training, communication, UAT ownership, adoption risk, hypercare, and stabilization.
Default Outputs
- Change impact map.
- Training plan by role.
- Communication plan.
- UAT ownership matrix.
- Business readiness checklist.
- Hypercare adoption plan.
- Process owner decision list.
Workflow
- Identify impacted roles, modules, legal entities, business processes, reports, integrations, and data ownership changes.
- Separate technical migration from business behavior change.
- Define training topics, audiences, timing, and evidence of readiness.
- Create communication by stakeholder group.
- Define hypercare model and adoption exit criteria.
Use Generated Artifacts
Prefer these analyzer outputs when available:
ai-training-change-impact.mdif present in workspace templates.project-onboarding-guide.mdpersona-team-member-task-view.mdweekly-status-report.mdai-workshop-questions.mdai-migration-backlog.mdai-quality-gates.md
Quality Bar
- Treat adoption as a migration workstream, not an afterthought.
- Link every training item to changed process, role, or system behavior.
- Include UAT ownership and business sign-off criteria.
- Call out readiness risks that can block go-live.