🧑🏻🎤 My Role
Product Designer, Researcher
📑 Project Type
Redesign, Interaction Design, Payment Dashboard
👯♀️ Collaborators
Engineers, Product Manager, Operational , Account Payable, Finance
🗓 Date & Place
🔥 Challenge
Snapshots of current system(s) to run our operational in payment team.
How might we create a robust payment system that is accurate, fast, reliable, integrated, and scalable?
💻 Final Output
✨ Outcomes
Disbursement time is now 60%~ faster
Remove 75%~ of payments rejected/month (due to wrong disbursement amount)
100% of our disbursement now can be done in our platform (Previously only about 70%)
Improve payment request Accuracy by 80%~
Reduce complain from transporter by 90% (About Payment Amount & Transfer Details)
Scroll down to see design process overview or contact me to see the details of the project ilhampamn@gmail.com
'It's a literal embodiment of quick fixes'
This is one, concise sentence to describe the current condition of our payment dashboard. We decided to create a new platform where every module is also going to be reworked. I was in charge to build the payment module under the payment platform squad specifically for the disbursement system as the foundational module of our system. These are the initial impression that we get when we see the system at a glance.
It's a replication of Excel Sheets
Decentralized Document Management
Unstandardized Input & Flows
Prone to error disbursement due to free text-input for amount to be disbursed
I partly contributed to this mess (I'm aware of the risk of a quick fix, saw all of the sign but didn't act upon it for the first 3 months in the payment squad) so the offensive tone is necessary ✌🏻 (we learned it the hard way, it's a hard pill to swallow but it is what it is)
We move on, and right after we identify the surface problem, I started to plan the discovery side of this project. This is how the story went.
Discovery Process of the project
After the discovery process we started to synthesize and discuss it together. If we only look at the problem piece by piece, it's pretty straightforward that we can just fix it right away. But we have learned, that another quick fix won't fix anything. So we tried to knot the pieces into one story and came up with some ideas/approach which are:
Create a whole new module for payment schedule so that our payment will scale
Streamline all of the process, not just improving the User Interface for the sake of it.
We also refined our goal of the project so that we can start working backwards:
I also came up with a design principles to make sure that we can achieve our goal, which everyone agreed on prior to delivery kick-off project.
It’s time for us to make it into realization. The approach of my solution-validation is mostly using The Funnel Technique in Qualitative Usability Tests with operational staff + Design review with the upper management. Breaking Down & Prioritizing Macro/Micro JTBD for each role
The importance of Design Principles
Conceptual Thinking is very important in the type of project
Hypothesis-Driven Design
Contextual Design Framework x Information Architecture Management
Stakeholder Management & Facilitation Skills
System Thinking (How things affect each other)
Testing Method Exploration + Rapid Feedback
