01
What implementation readiness means
Readiness does not mean every setting is finished or every question has a perfect answer. It means the team has enough ownership, operational clarity, validated information, and delivery capacity to make configuration decisions without repeatedly reopening the same assumptions.
A low or incomplete answer is not a failure. It is an early warning that lets the team resolve a dependency before it becomes rework during migration, training, or go-live.
- Decision readiness: the people with authority can resolve scope and workflow questions.
- Operational readiness: current and future workflows are understood by the roles doing the work.
- Data readiness: source records are clean enough to map, sample, and validate.
- Adoption readiness: role-based practice, support, and post-live ownership are planned.

