Overview

Summary

<aside> 💡 Fazz Financial Group has many products, such as Payfazz Agen (PFA) & Payfazz Master Agen (PMA). The two are similar but Payfazz Master Agen (PMA) is still missing some features. We want to migrate some of the features from PFA to PMA, one of them is Set Selling Price (Atur Harga Jual).

</aside>

<aside> 💰 Atur Harga Jual is a feature that aims to ease agents’ transaction process. Our agents sell many digital products, and their customers need a receipt as proof of transaction. Currently, agents can set the selling price right when they’re about to print the receipt. However, this process has some disadvantages for agents. Hence, we build this feature that enables agents to set the selling price beforehand called Atur Harga Jual.

</aside>

<aside> 🗣 Role

UX Designer

</aside>

<aside> ⌛ Duration

4 weeks

</aside>

Background

The main reason for this project to happen was the migration plan. From the PM’s side, we wanted to complete the feature on the other app so that the migration process could go smoothly.

The Design Process

After receiving the PRD from the Product Manager, I then begin the crafting. First and foremost, I analyzed the PRD to truly understand the requirements. The way I did it was by breaking down the requirement into bullet points.

Every project has a challenge. Some of the challenges that I faced were:

• We don’t have enough data from the current feature, especially the statistics.
• Each digital product has a different flow; such as postpaid, prepaid, and finance. In each category, the flow might differ from one another.
• In financial products, such as bank transfers, the transfer amount is going to be different for every agent. How to make the process of pre-setting the selling price easier?
• Currently, agents can set the selling price before printing the receipt, in the cashier feature, and now in the Atur Harga Jual feature. There are a lot of ways to set the selling price. How do we make it seamless?
• And many more...

Despite the challenges, I went through with the project. The first thing that I did was evaluate the current version of the feature in the PFA app by myself. Some of the findings that I found were:

• There is no response from the system after the user sets the selling price
• Too many terms, such as biaya pembayaran, biaya layanan toko, harga jual, etc.
• Inconsistent CTA, screen-naming, etc.
• It’s kind of hard to see all selling price at once because the detail is hidden in the accordion menu
• And some other things...

After evaluating the current feature, I tried to dig deep into the company’s artifact to find previous research related to Atur Harga Jual. Fortunately, we have some research that gives an insight into our users’ behavior. Also, I asked the senior designers who have worked on this project before for more insights regarding this feature. The main thing that I found was that most agents don’t have a problem completing the task (setting the selling price). This shows that the current flow is already easy to understand.

Competitive Analysis