Background
CICIL is one of the biggest education funding companies in Indonesia. Our goal is to facilitate students' needs to ensure they have everything necessary to excel in their education. While student loans are popular in the US, they are a new concept for Indonesian citizens.

How Cicil works

Chapter 0. Synopsis
Problems
The existing checkout page was plagued by difficult loan terms and a cluttered design. The inability to switch links when students wanted to try another simulation also contributed to a ridiculously high drop rate. Confusing installment and limit information disturbed the price simulations and checkout experience.
Objectives
- Improve the visuals of the new checkout page with a new design system and fix all the UX and content structure problems.
- Make the informational structure better for existing and new users.
- Decrease bounce rates and user complaints about unclear loan structure information.
Challenges and constraints
This was my first major redesign project and also one of the most important parts of CICIL's product journey. I had to manage this project while I was only five months into product design, and all the research was done during early COVID-19. The research process was difficult because we needed to conduct all interviews and usability testing using online tools.
Old checkout page with a lot of unclear structure of number calculations
Chapter 1. Understand
Research, interviews and data
This project started with limited resources for research because CICIL only had one researcher with an unstructured research method. Therefore, I started the project without in-depth user research. I looked for several sources of information such as research results from PMs, interviews with stakeholders, and expected targets from the designer's side. I initiated concept testing to users to get immediate results in the form of data.
To understand the product deeply, I initiated talks with the product manager. These conversations generated a lot of information about how our margin counts.
Conducting online usability testing was new due to early COVID-19. We tried concept testing with Maze and generated significant data.
After concept testing, the design direction was clearer. We understood the design objectives.
Research: Maze usability testing
Concept testing the first iterations yielded:
I initiated this concept testing together with the product researcher, using Maze as the main tool due to the limited situation (pandemic). We also followed up with some users through online usability testing along with simple interviews. This research produced quite satisfactory results because we got enough insight to continue the design process.
What we learned so far?
- Some loan/financial terms were difficult to understand, and users just wanted to know the installment amount.
- Users liked to try different links from different price sellers, contributing to a high drop rate.
- The drop rate was reduced from 70% to 20% during concept testing.
- Understanding the loan limit concept was difficult.
Research: Interview
Online usability testing the second iterations
This time around we were pretty much in the final stage of designing. We conducted another round of testing after getting a lot of feedback about structural details. We tried to improve the IA and show information that matters to the users. These were the goals of the next iterations:
- Better information hierarchy and minimized distractions.
- Make switching links more accessible.
- Provide concise installment breakdowns and limit usage information.
Problem statement
- Unfamiliar terms for students.
- Unclear fee breakdown.
- Inability to switch between links to simulate other prices.
- Confusing credit limit information.
- Cluttered information overshadowing main information.

Chapter 2. Craft
Deliverables
Based on our research and testing, we made several design changes:

Design deliverables
Visually fresher design
Simplified UI to make the experience easier for users.
Every section crafted with a user-centered mindset
As we found out that our users like to try different links to simulate the price, we understood that it is one of the reasons our drop rate is high. Adding a shortcut link crawler form is the key to make the experience seamless and reduce drops.

Deliverables 1
We understand that users came to our app with clear intention to buy a specific product, not browsing
We're not a marketplace. We're a 3rd party payment app. Users came to our app with a specific mental model. They already knew the stuff they wanted to buy after browsing in the marketplace. Instead of making the product card take up half of the space, we decided to cut a lot of unimportant information and make it more compact.
Deliverables 2
Switch link whenever you want
Users can switch links to simulate different prices seamlessly.
Deliverables 3
Decluttered loan breakdown
Combined variables into "Cost Accumulations" with a detailed view available on click.
Deliverables 4
New and improved limit card
Visual cues replaced confusing numbers, indicating available limit usage clearly.
How it used to be
Full of numbers that don't make sense if we really count them. It looks like a multiplication but it's not. The numbers are all over the place, while all the student cares about is whether they can still purchase this product with the current limit.
Now it's easier to scan quickly
Green indicates how much limit will be used from your current available limit. Adding a checklist indicator makes it clearer.
If students run out of limit, they cannot continue with the checkout. Increase the down payment or buy cheaper stuff.
Available limit vs. overlimit state
Bonus explorations
Adding loading animations to make it more fun
Some students who live in rural areas might face a longer load while crawling the product from other marketplaces. I tried to empathize with their waiting time and added a loading animation to make them feel that the loading is happening.
Chapter 3. Learning
Learning and take aways
This project, my biggest solo project so far at CICIL, taught me a lot about communication with PMs, engineers, internal stakeholders, and users. Starting just 4-5 months after joining CICIL (my first full-time job as a Product Designer), I learned to craft good visuals, communicate my design, take criticism, and understand user needs.
