Thoughtful digital experiences built for people
Hey there, I’m Praduman, a product designer building products people rely on with 4+ years at Tala and earlier experience at Designit and BigBasket, I design thoughtful experiences for complex financial systems. I believe the best products come from curiosity, collaboration, and enjoying the process.
Revamped the entire cash-in and cash-out flow, which improved channel discoverability and usability and resulted in a scalable experience across markets
Redesigned onboarding and authentication into a faster, safer and more engaging flow that moves users to their first meaningful action with minimal friction
Design system for
A design system that serves everyone, not just designers: easy to use for product and engineering, backed by regular education with every team, and built to work beyond Figma
An interactive way to scroll through facts about me, code-ready with the help of Rive
A footer with a parallax effect that follows mouse movement, code-ready with the help of Rive
A working web prototype with real forms, validation and calculations, for insights a Figma prototype can’t give
Exploring how viable AI is for designers to make real changes to app code
Hey there
Hope you’re
having a
good day
Welcome and feel free to drag around, Don’t be shy
01
Revamped the entire cash-in and cash-out flow, which improved channel discoverability and usability and resulted in a scalable experience across markets
02
Redesigned onboarding and authentication into a faster, safer and more engaging flow that moves users to their first meaningful action with minimal friction
03
A design system that serves everyone — easy for product and engineering to use, backed by regular education across teams, and built to work beyond Figma
01The problem
Our repayment and disbursement flow leaned on one partner because the UI made the alternatives hard to find. Several payment modes existed, but customers rarely explored them — so every outage with the main partner caused spikes in support tickets and eroded trust. Research showed customers were open to other modes when they were presented clearly.
02Research insights
Over-reliance on one partner hurt conversions whenever it had issues, while the other methods stayed hidden and friction-heavy in the existing UX.
03Why improve the design
Problem
The Cash In/Out interface felt dated and inconsistent with Tala’s evolving brand, reducing visual appeal and confidence.
Solution
Modernised the UI to align with Tala’s new design system — a cohesive, contemporary experience that reinforces trust and gives users the clarity needed.
Problem
The previous design lacked a flexible structure, making new features, markets or payment methods hard to add.
Solution
Established a scalable, robust foundation that can grow with new markets and evolving user needs, and also adapt to push new modes of payment.
Problem
Overloaded repayment and disbursement flows created friction, so users stuck with familiar modes.
Solution
Streamlined the experience to reduce cognitive load — nudging users toward alternatives without forcing behavioural change.
ConstraintsReusable screens for cash-in and cash-out · No backend changes · Minimal tech investment
04User testing
Six moderated, in-office sessions gathered qualitative insight, while an unmoderated Maze study sent to 32 users surfaced usability issues with quantitative data.
05The solution
Grouping channels gives every mode an equal chance, with a lower click cost than scrolling a long list.
QR payments sit at the top with reassuring labels like “Instant & easy”, guiding users to the best option.
New ways to show how and where to pay, surfacing the details that matter and removing the clutter.
A reusable error template lets other teams handle common errors without design support.
Migrating to a new market only needs new icons and copy — faster rollouts, lower cost.
06From the design sprint
QRPh is the Philippines’ national QR standard, set by the central bank. One QR can be paid from any participating bank or e-wallet — a single payment method that addressed the biggest issues users faced. As it was new, the design guides users on where their QR is accepted, and gives them a downloadable QR showing the amount and expiry.
07Impact
08What went wrong — and what we did
After reviewing 100+ UX Cam sessions and Amplitude data, three trade-offs stood out: more screens, fees that were now visible, and GCash moved into a category. We accepted the short-term friction — fee visibility builds trust over time, and moving GCash was deliberate, to reduce dependency on one partner.
A follow-up design sprint brought the whole team together around the cash-in / cash-out funnel. We cut the steps to repay — removing a fee sheet that raised anxiety without helping, and merging a step into channel selection.
01Objective
Redesign onboarding and authentication so new users reach their first meaningful action with minimal effort: streamline long screens, tailor the path for returning users, and secure sensitive inputs with an isolated PIN keypad and modern, structured fields — reinforced with clear progress, subtle motion and haptic feedback.
02Re-looking at the flow
A static logo didn’t show whether the app was loading or stuck — a missed first moment of delight.
New and returning users got the same journey, with no focus for either, and also fewer options for recovery.
Forgotten PINs, lockouts from fraud rules, and permissions asked before earning trust.
Too many questions on one screen created heavy cognitive load for the user, leading to incorrect data entry hurting the funnel ahead.
03Why improve the design
Problem
Both followed the same flow, causing confusion and extra steps for existing users.
Solution
Detect returning users and offer a streamlined sign-in, while new users get full, tailored onboarding.
Problem
Fields lacked clear structure and boundaries, hurting clarity and accessibility.
Solution
Clear boundaries, labels and modern styling for users less familiar with digital interfaces.
Problem
PIN entry relied on the system keyboard, which felt less secure and less consistent.
Solution
A custom in-app keypad isolated from system input keeps PIN entry secure and clearly trustworthy.
Problem
Users couldn’t tell how far along they were, raising perceived effort and abandonment.
Solution
A visible step indicator shows completed and remaining stages, motivating users to finish.
Problem
Long scrolling screens with heavy manual entry caused fatigue and drop-off.
Solution
Short, focused steps with progressive disclosure lower the effort on each screen.
Problem
The flow felt rigid and transactional, missing chances to build trust.
Solution
Subtle animations, transitions and haptics at key moments signal progress and build connection.
04New additions
Different paths for returning and first-time users, who need different things from the app.
Motion throughout the journey makes it feel less transactional.
Most users typed details from memory and later failed KYC — scanning the ID first is good friction that saves pain later.
The same scan pre-fills the form, preventing data-entry errors.
A new visual language from the design system, with fields built for accessibility.
Searchable dropdowns for address entry instead of free typing.
One action per screen — choosing an answer also moves you forward.
High-friction KYC steps spread across the journey instead of all at once.
01The question
How can we build a design system that empowers every team — not just design — to stay consistent and make changes independently, so the design team can focus on innovation instead of routine BAU work?
02Catering for ease of use
Who it’s for
Product teams and designers handling small BAU work with tight constraints.
How it works
Ease over flexibility, so small changes stay quick and consistent — like updating text for localization.
Who it’s for
Screens that share a structure but differ in content.
How it works
10+ main screen types — single input, forms and more — share templates, with custom components dropped into predefined slots.
Who it’s for
Designers building new experiences.
How it works
The standard way: pick pre-built components and foundations, and build on top — where designers can also create from scratch.
A streamlined-to-advanced right panel helps product and engineering find the source of truth in any file, and make micro adjustments — like copy or spacing — through variables and text properties.
03Education for all teams
Reviews that keep components, foundations and docs moving together.
Regular check-ins on implementation issues and new opportunities.
Training product teams to find and use components confidently.
One place to raise issues and request the upgrades teams need.
04Beyond Figma
A design system is only as valuable as its impact on development time. After thorough discussions with the tech team, we chose Jetpack Compose, so Android engineers can implement Level 1–3 work with the same efficiency and consistency designers have in Figma — with fewer rounds of rework and realignment.
05Claude skill to ease documentation
A design system is only as valuable as its ease of use and how much easier it makes the work for designers and developers — so the idea for the documentation skill was to increase adoption by all team members, and build consistency among documentation too.
