Goal savings
Making savings simple for Africans who just want to set money aside without confusion.


Context
When I joined Ejara, one of the first challenges was around savings. Research had shown us that a large number of users didn’t quite understand our savings product. To them, it looked and felt like an investment product, not savings. And for something as sensitive as money, that confusion was dangerous
But here’s the thing: people actually wanted to save. In fact, an earlier experiment that was ran “Locked Savings” showed that users loved putting money aside until a specific date. Many even locked their funds without hesitation. People wanted to save with purpose, they just needed a product that made sense.
So my job was clear: Design a savings experience that felt familiar, intuitive, and easy to trust.
Role
Product Designer
Company
Ejara (fintech)
Duration
5 month (launched🚀)
Year
2024
Getting started
I didn’t want to reinvent the wheel. Instead, I looked around at apps people already trusted for saving, Piggyvest, Risevest, Aucred. I compared flows, and asked myself: what are the patterns everyone uses, and where can Ejara do better?. I paid attention to what was common across all of them (goal name, target date, target amount, frequency) and also where they fell short.
From there, I sketched the first user flow. Creating a goal would start with the essentials: a name, a target date, a target amount, and the saving frequency: weekly, monthly, or flexible. I designed the experience of add money into that goal, tracking progress, breaking a goal early, and even earning a cash bonus from your savings. Each of these flows needed to feel intuitive, like a tool people already knew how to use.
Key flows
The first visual shows the ‘Create a Goal’ flow, highlighting key details such as the goal name, category, description, target amount, and target date.
The second visual shows the ‘Add Money’ flow, where users top up their goal by adding funds.

Key flows
The first visual is the ‘Edit Goal’ flow, where users have the option to change the details of their goal.
The second visual is the ‘Break Goal’ flow, where users can end their goal before the target date, though this comes with a break fee.

Edit goal details
Goal title
For school

Rent
Change
Goal description (Optional)
One is that, as a large language model, it may have simply been predicting...
Continue
14:45

How much do you need for this goal?
XAF
0
0 XAF, monthly
When should it be done?
September 17, 2025
Change
Are you giving up now?
You’ll lose 2500 XAF if you break your goal.
No, cancel
Yes, proceed
Beta testing with users
I wanted to test what we designed as quickly as possible so i requested for a beta testing, which was done with some of our active users in the previous app version. We watched them use the app, listen to their complain and watched their body language.
About 80% of them misunderstood the label “Goal Amount.” They thought it meant how much they wanted to save right now, not the total they needed to reach the goal.
The homepage also caused friction. The testers weren’t sure where to go to create a new goal, which meant the experience wasn’t as obvious as it should have been.
These insights guided a round of refinements clearer labels, friendlier copy, and a redesigned homepage that made creating a goal feel effortless.
After iteration
The first screen highlights the label change for the target field, updated based on feedback from beta testing. It was revised from ‘Goal Amount’ to the clearer label: How much do you need for this goal?
The second screen highlights the previous savings homepage and the updated version, with emphasis on the goal savings section. The goal savings section was restructured into a compound section, directing users to a dedicated screen where they can either view existing goals or create a new one.


What the data showed after launch
Three months in, the data told an interesting story:
70% of users chose goal durations of three months or less. And about 80% of them either reached their target amount, their target date, rarely both.
But patterns always reveal new opportunities. Some users were hitting their savings target early, with time still left before their goal date. Others got to their goal date but hadn’t yet saved enough. In both cases, the product didn’t give them flexibility, so I had proposed something new.
Iterating for flexibility
So, I pitched a new idea: let users increase their target amount if they finished early, or extend their date if they weren’t there yet.
This feature will allow users to increase their target amount if they had saved faster than expected, or extend their target date if they needed more time as it adapt to real-life ups and downs.
The result? Goal Savings quickly became the most-used product out of all our releases. It gave users clarity, control, and confidence in their money and that’s exactly what savings should do.

Goal details

Rent a new home
250,000 XAF
Dec 27, 2024
Withdraw
Increase amount
100%
Amount saved
250,000 XAF
Cash bonus
Your savings earn bonuses!
View
14:45
Last transaction
See all

Deposit
Completed
30,000 XAF
09:23 AM
Woohoo! 🎉 You’ve hit the target amount!
Increase the amount to continue saving.
Goal details

Rent a new home
250,000 XAF
Dec 27, 2024
Withdraw
Extend date
100%
Amount saved
250,000 XAF
Cash bonus
Your savings earn bonuses!
View
14:45
Last transaction
See all

Deposit
Completed
30,000 XAF
09:23 AM
Woohoo! 🎉 You’ve hit the target amount!
Increase the amount to continue saving.

Impacts and Results
Goal Savings became the most-used product across all releases following iterative improvements
Eliminated 80% user confusion through terminology refinement and UX improvements
Reflection
For me, this project reinforced a few key lessons:
Familiarity lowers friction, users don’t want to rethink how savings should work.
Language is design, the right label can be the difference between confusion and clarity.
When people see a product adapting to their reality, they keep coming back.
Thank you for reading
View next project