Walk a Duplicate Incident to Control
Resolve a duplicate-record incident by moving from containment to root cause to recurrence control.
Incident Northstar Medical appears twice in the forecast, inflating pipeline by $310K. Two account teams are acting on different customer records for the same organization. DMAIC lens Contain, analyze, control Do not call a duplicate incident resolved after the merge. Resolution means the creation path is changed and recurrence is measured. Merge and move on Contain -> Five Whys -> Control Lower duplicate creation rate Cleanup is repair; control is improvement. 1 Contain 2 Analyze 3 Control First move The duplicate is affecting forecast and account ownership today.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in