Risk and Decision Register
The controls that addressed data quality, adoption, continuity, and the risk of copying the old workflow without understanding it.
Risk principle: The old tables were treated as evidence to interpret, not as a complete description of the operating model.
Risk register
| Risk | Potential effect | Initial response |
|---|---|---|
| Hidden workflow rules | Important logic exists only in people’s habits or private workarounds. | Map the process, use coexistence, and keep a decision log. |
| Data mismatch | Records do not map cleanly to the target model. | Define schema mapping before migration and test representative sample data. |
| Team rejection | A generic admin screen does not fit the roles doing daily work. | Build role-appropriate views and validate them with the team. |
| Incomplete handoff | The CRM depends on the person who originally built it. | Provide SOPs, known-issues notes, and clear ownership. |
| Premature cutover | Missing scenarios or data gaps interrupt daily operations. | Keep systems in parallel until selected scenarios are validated. |
Key decisions
Schema before screens
Model the work and relationships before reproducing old views.
Coexistence before cutover
Use a parallel period to reveal missing states, data gaps, and ownership questions.
Scenario-based validation
Test the work the team actually needs to perform, not only technical setup.
Handoff as deliverable
Documentation and ownership are part of the system’s readiness.