BA ACADEMY / CASE STUDY
Policy payment failure: finding the real constraint
A fictional insurance analysis demonstrating root-cause thinking across systems.
This is a fictional learning case. It demonstrates an analysis method, not a claimed client project or measured delivery result.
01
Business problem
Customers report payment failure even when their card is valid; operations has been manually reopening policies.
02
Context
An insurer's portal, payment gateway and policy administration system exchange status changes asynchronously.
03
Stakeholders
Policyholders, payments operations, finance, product, gateway provider, developers and QA.
04
Discovery
Review incident samples, event timestamps, gateway responses and policy-state transitions. Interview operations about workarounds.
05
Analysis
Map the payment state machine and correlate failures with a stale eligibility flag. Distinguish gateway declines from internal policy blocks.
06
Requirements
Define valid state transitions, retry rules, idempotency, reconciliation alerts and customer-facing error language.
07
Solution
Change the eligibility check and add a monitored reconciliation path rather than adding a generic retry button.
08
Testing
Test duplicate callbacks, timeout, delayed success, declined payment and policy reopening in UAT.
09
KPIs
Unsuccessful policy payments, manual interventions, duplicate charges and resolution time.
10
Outcome
Reference outcome, not a real delivery claim: a remediation proposal with explicit tests and measurable success criteria.
11
Lessons learned
A visible customer symptom may originate in a downstream rule. Map the full journey before changing the interface.