A remediation sprint cleans years of bad address rows in the property system but leaves the capture form free-text and unconstrained. What outcome should the program expect?
Select an answer to reveal the explanation.
Short Explanation
Mopping the floor while the tap still runs just schedules the next flood. Cleaning history without locking down the capture form invites the same defects back. Prevention has to ride with remediation.
Full Explanation
One-time historical remediation improves the current state but does not change the process that generates defects. Unconstrained capture forms continue to admit bad addresses after the cleanup window closes. Effective programs combine correction with prevention controls such as validation, picklists, and stewardship at entry. Without that pairing, defect rates typically rebound.