Financial planning can be ambiguous and intimidating for students and young professionals. We wanted to design a platform to make financial planning more approachable and relevant, seamlessly integrated into each Millennial’s busy lifestyle.
- We conducted user research through 10+ ethnographic interviews in person and over the phone. Through these interviews, we created three personas: a university student, a young professional, and a pair of newlyweds. We eventually cut the newlyweds persona to have a tighter focus on our user.
- We researched other apps currently on the market to better understand what offerings are already out there and how we would differentiate ourselves. We organized the current financial planning apps into 3 categories: spending, saving, and investing.
- We positioned ourselves as a potentially highly social app, utilizing users’ spending data to help them better plan for their savings. Users could sync up their financial information and make wishes, or financial goals, and use our app as a progress tracker.
- I drew some wireframes and went to test out our ideas with the users we had originally interviewed. They gave us great feedback and told us what features they liked, didn’t really need, and wanted. One example was the name of our app – our original name “WingIT” appeared to give off a careless vibe, which took away from the integrity of our financial planning app.
- I eventually converted these sketches into hi-fi wireframes and continued to collect feedback and make design changes. Using the wireframes, I built a deck and eventually presented it to my team.
Design Challenges & Takeaways
- I learned to not jump to hi-fi wireframes right away – users will tend to provide feedback that is focused more on aesthetics as opposed to functionality. It’s also way easier to make quick changes on a lo-fi wireframe.
- Financial planning is quite broad, and it’s important to have a tight definition on what it means with your app and for your users.
- Sometimes, you might fit into the user personas, but you should not assume that you are the user you’re designing for!