Product Designer
User Research
Planning user research: recruiting users from askable, designing facilitation guides
Moderated & unmoderated user testing
Conducting user interviews
Insights shareback
Detailed dev-ready UI design work
Product strategy
Hi-fi prototype testing & iteration
Lo-fi prototypes
QA and testing
Financial stress is the top stressor for Australians and 50% of the population feel they lack financial wellbeing. Financial wellbeing isn’t just about how much money one makes, but also how they feel about their financial situation.
Many people are unaware of the impact that their everyday spending habits have on their money. Our brains often operate on autopilot and in this state we often buy things without thinking about the future ramifications.
Wisr saw this as an opportunity to use the power of behaviour change to help people improve their financial health.
The beta version showed early signs of product market fit with positive feedback from users. But the product lacked excitement and a strong IA. I redesigned the app and launched it to market within 6 months of joining the team.
During that timeframe there were many challenges. Here are some of our achievements.
Even though the beta version of Wisr Today tested well, we needed to further understand our primary users.
Through countless interviews and surveys, we built out our superfan profile.
They weren’t:
Someone who had their finances in control
Someone who knew and recognised their money behaviour
Someone who was struggling to make ends meet
They were:
Users who had adequate income but were overspending due to bad money habits, leading to debt or not being able to pay off their debt
Women between 24 - 34
“Self-improvers” who had tried budgeting tools before
These guided how the product was designed from visuals to tone of voice.
We mapped out the beta 3 user journey and iterated on it to build the ideal user journey and user flow.
Breaking free of the UI and looking at the app experience holistically helped us achieve two important thing:
Not get stuck on minor details & see the gaps between beta experience vs ideal experience.
Make decisions on app IA.
After gaps were identified solutions were designed with our target market in mind. This led to the introduction of a more fun app experience compared to beta versions.
Working with the product manager and growth lead to design experiments on the onboarding funnel as we were getting a lot of downloads but our trial start rates were very low.
One experiment we ran that led to a big change in the number of trial starts was on the paywall.
We launched with a paywall design that was minimal showed the pricing and a value proposition.
Once we saw there was a big drop off on the paywall, we started to look deeper at the paywall from a user’s perspective.
How would someone feel when they see the paywall & price tag?
What questions will they have?
Based on a few user interviews and our assumptions these were the concerns we highlighted on the launch paywall.
Doesnt address users main concern/pain point:
When will I be charged?
Am I being charged the full amount right now?
I’ll forget to cancel my subscription
Users are anxious when they see the paywall
We addressed these concerns on the paywall by:
Iteration is inevitable so after the launch we were conducting user interviews and running maze surveys with users who were engaged but more importantly who churned at different point in the journey. Based on the feedbacks we received we ran different experiments & implemented changes to the product.
Working closely with the product manager we designed A/B tests for different points at the onboarding funnels (eg: entry screens, paywall) to make product decisions.