Product and business analysis, from Jakarta. Application journeys, payments, and the systems underneath them. I am at my best where the requirement is vague, the deadline is real, and five teams disagree about what done means.
The flow had been assembled one step at a time and nobody owned the whole of it. I mapped what actually happened, found where applications quietly died, and put a name and a clock on every step. 67% faster, end to end.
Every login was spending money nobody had questioned. Replacing paid SMS codes with a flash call took 60% off the bill — and, unusually for a savings project, people preferred the new way.
Started September 2026, and dated on purpose. This is the part of the site that is supposed to grow.
Short pieces on how requirements go wrong, and what I read that changed my mind.
A log, with a line or two each. The cheapest habit to keep, so it starts first.
Small things that work, including this one. Informatics degree, still used.