Run FMEA On A Billing Change

A pricing-table migration affects 1,200 customers. The sample invoice test passed, but RA needs to know which failure modes need controls before launch. FMEA scoring: severity x occurrence x detectability -> control priority Not quite: relying on a passed sample invoice test can miss segment-specific defects. A sample proves those customers worked, not that the riskiest failure modes are controlled. Name failure modes List grandfathered discount loss, wrong tax treatment, inactive product code, and duplicate minimum fee. Failure modes are concrete ways the change can fail, not broad worries. Score severity Grandfathered discount loss scores 5 because it creates customer…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in