The top-up that was “successful” too early
We asked File Lighthouse to look at e-wallet top-ups after the contact centre kept taking “where is my money” tickets in the same week our pack showed a healthy success rate. Aida’s matching pass showed the success event firing on acknowledgement, not on completed load. We changed the steering pack before the next month closed.
— Head of operations, licensed e-wallet, Peninsula Malaysia
KYC retries counted as new people
Our onboarding funnel treated every MyKad recapture as a new applicant. Priya wrote that down in language the board could not wave away. The audit did not magically raise conversion; it stopped us celebrating a number that was mostly retries.
— Product lead, digital lending, Klang Valley
Workshop, with a leftover argument
The event naming day was useful for abandon versus fail. I still think “pending at switch” deserved its own label and Wei Liang wanted it under a broader pending bucket. We left that one open on purpose rather than inventing a name nobody in ops would use.
— Payments manager, remittance app
Longer note: first disbursement weekend
A BNPL team in East Malaysia sent a week of origination events and a redacted disbursement file. The readout showed Saturday-night approvals sitting in “drop-off” because the partner bank did not post until Monday. The contact centre already knew this; the weekly chart did not. File Lighthouse did not rebuild their charts. They annotated the ones in use and sat a 45-minute briefing with finance in the room, which was the point.
We later booked the longer product measurement audit for the repayment journey. That second piece took the full five weeks because the settlement extract arrived late — not because the review itself wandered.