Wealth Wizard - An App to Increase Financial Literacy

Summary

In our Digital Prototyping we, as a selected group, created a high-fidelity digital prototype on our assigned prompt. Our solution was a phone application that seeks to improve a user's financial literacy.

Course: ITD 150: Digital Protoyping at The University of Texas at Austin

Project Timeline: 5 Weeks

My Role

Position: Team Member

Responsibilities: Team member that worked with others to create a solution to the problem provided. Helped with conceptualization, ideation, and implementation.

Teamwork: Collaborated with 4 team members [Parth Ghawghawe, Hui Feng, Truc Tran, Grace Sajjarotjana, guided by Professor Joe Meersman.

The Prompt

There are people who are in need of public services but do not know where and how to access them. Many people in need have cell phones and access to technology at libraries and other public facilities. What can keep them aware of services, gather information, and make informed decisions about obtaining assistance? How will they understand how many service providers there are and what associated information is required to gain assistance? Your task is to design an experience that makes it easier for people needing services to obtain them. Your solution could be a service, website, mobile application, chatbot, etc. Don’t worry about the underlying technology, focus on the experience that a user has.

End Goal

Design an accessible application that offers financial advising, thus improving one's financial literacy.

Process

Refining the Concept

In the early stages of the project, our team generated a wide range of ideas in response to the challenge. We carefully evaluated each concept against the prompt, prioritizing solutions that would be accessible, practical, and empathetic to users navigating complex public services.

One idea stood out in particular—addressing financial literacy. As college students living on tight budgets, we resonated with the struggle of understanding how to manage money, especially when access to resources isn’t always clear or centralized. We recognized that this gap in financial knowledge mirrors the broader issue faced by individuals seeking public services: a lack of accessible, digestible, and actionable information.

With that insight, we chose to pursue a solution that empowers users to better understand their finances, identify helpful resources, and ultimately make informed decisions. This direction not only aligned with our personal experiences but also fulfilled the core goals of the design brief.

Prioritized Pain Points
  • Feeling inconclusive or unfulfilled after reading financial information
  • Too many options creating decision fatigue and uncertainty
  • Uncertainty about what to search for or where to begin
How the App Responds
  • Asks questions about financial status and goals to build user confidence
  • Provides tailored suggestions to reduce decision overwhelm
  • Offers additional information on demand to satisfy curiosity and depth-seeking
Planned App Pages
  • Welcome Page: Introductory experience and app overview for new users
  • Profile Page: User enters financial info and preferences
  • Home Page: Main dashboard for navigation and content overview
  • Chat Page: Users can ask personalized financial questions
  • Learning Page: Curated educational content tailored to user needs
  • Learning Journey Overview: See progress and what's next to explore
  • Action Page: Suggestions for what users can do with their budget/savings

Journey Map

Our team began by outlining what a user might experience when attempting to find financial information—especially when under pressure to make responsible decisions with their income.

In this scenario, the user has just received their paycheck and wants to make a smart, informed decision about how to handle it. This journey allowed us to empathize with the confusion, uncertainty, and overload of options that can arise during this process.

By mapping out this experience, we gained insight into user pain points and emotional states, helping us better identify opportunities for intervention and support in the financial literacy space.

Workflow Diagram

Building on the journey map, we created a workflow diagram to illustrate the user’s decision-making process. This allowed us to visualize their steps, needs, and moments of friction when managing finances.

The diagram highlights user actions and surfaces pain points that could hinder confidence or clarity—such as uncertainty in choosing tools or knowing where to begin. It also helped us pinpoint opportunities where our solution could step in and provide support at the right time.

This step was essential in shaping a thoughtful, user-informed experience structure for our application.

Information Architecture

To support a smooth and intuitive user experience, we developed an information architecture that outlines how content and functionality are structured within the app. This helped us establish a clear, easily digestible hierarchy that guides users through their journey.

By organizing content in a way that reflects user needs and behaviors, we aimed to minimize confusion, reduce cognitive load, and promote confident navigation throughout the platform.

This foundation also served as a blueprint for designing consistent interfaces and seamless interactions across the app.

Low-fidelity Wireframe

In response to the key pain points identified during the research phase, we created a low-fidelity wireframe designed to address the primary user concerns:

  • Feeling inconclusive and unfulfilled about information read – We aimed to provide clear, actionable insights.
  • Too many options creating uncertainty in choices – Our wireframe simplifies the decision-making process with fewer, more focused options.
  • Unsure what to search – The design includes intuitive navigation and suggestions to guide users effectively.

This wireframe serves as the foundation for a solution that aims to reduce confusion and provide clarity for users in need of financial assistance.

User Stories

We identified key personas and scenarios that represent the types of users who would benefit from an app like this. The user stories help us understand their needs, motivations, and the pain points they experience when managing their finances.

By creating detailed user stories, we were able to ensure that the app design would cater to the real-world situations users face, providing them with relevant and actionable financial guidance.

User Stories Examples

Alex

Demographic: Female, 21, Texas, College Student, $10k a year

Story: "As a student, I want to have a budgeting app in order to track my spending on textbooks, tuition, and housing while also providing tips for saving money."

Emily

Demographic: Female, 42, Washington, Unemployed, Retired, $0 a year

Story: "As a person who inherited money from my mom, I want to see how I can reinvest this money or budget it wisely. It was enough money for me to retire, but I want it to last and spend wisely for my future kids."

Ava

Demographic: Female, 21, Florida, College Student, $5k a year

Story: "As a college student who wants to have a summer vacation, I need to know how to use credit card credits to buy a flight ticket. In order to know the credit information, I need to learn how to improve my credit."

William

Demographic: Male, 35, Michigan, Doctor, $200k a year

Story: "As a person who wants to buy a new house, I need a tool that allows me to create a comprehensive estate plan, including wills, trusts, and beneficiary designations."

Prototype Completion

This is a layout of our final prototype, wireframed in Figma. It represents the finished design, incorporating feedback from earlier testing phases and is ready for further iterations and user testing.

Interview and Testing

In this phase of the design process, we conducted interviews with potential users from a range of financial backgrounds. Each team member recruited one participant to evaluate our application and provide feedback. We started by asking introductory questions to understand each person's financial background and perspective on financial literacy.*

We then guided participants through the application prototype and asked them to complete specific tasks to simulate real use cases. Afterward, we gathered qualitative insights on their experience, visual preferences, learning methods, and suggestions for future improvements.

What We Wanted to Learn
  • How do users respond to the Resources page vs the Lessons page? Which is more helpful?
  • Which learning methods are most effective? (Text, Gamification, Models, Pictures)
  • How would users use the Chat feature? (Learning, Q&A, support with specific situations?)
  • Would users want automatic chat recommendations or follow-up suggestions?
  • Are there any additional features users wish the app had?
Interview Script (15 minutes per person)
  • Introduction: Briefly explain the purpose – to reduce pain points for people seeking beginner-level financial guidance.
  • Pre-interview questions:
    • Name & Age (and major, if applicable)
    • How important is financial literacy to you?
    • How confident are you in your financial knowledge?
    • If you had financial questions, where would you typically go for answers?
  • Walkthrough: Guide the participant through the mockup while noting reactions, comments, or questions.
  • Task-Based Prompts:
    • Set up your profile page.
    • Explore a budgeting model and share what lessons you learned.
    • Use the chat feature – “What would you ask the chat?” or “What do you wish it could help you with?”
  • Reflection Questions:
    • How do you feel about the look and feel of the app?
    • Do you prefer the Resources page or the Lessons page? Why?
    • Which learning methods work best for you when it comes to finances?
      (Options: reading content, interactive models, visual examples, picture-based content)
    • Do you have any features or suggestions you wish this app included?
  • Observation: Note down any activities or pages the user revisited during testing.

Interview Notes

Interview - Parth

Participant: Isaiah

Major: RTF

Graduation: Spring 2024

Financial Literacy: Understands its importance, not confident, relies on Google and websites

Primary Notes

  • Suggested chat feature should be more prominent and initiate with conversational prompts
  • Visual learner; prefers models and images over text-heavy content
  • Liked the look and feel, Duolingo-style learning, and wizard persona
  • Felt budgeting page had too much text, profile page was “boring but understandable”
  • Thinks AI is useful but most users just want a simplified “wizard” experience

Secondary Notes

  • Found navigation intuitive during profile walkthrough
  • Suggested simplifying access to the budgeting page

Interview - Peter Ahloy

Participant: Julia

Age: 19

Major: General Studies

Financial Literacy: Not confident, relies on father for financial help

  • Overwhelmed by text on intro page; clicked “re-run model” as the only interactive feature
  • Found chat feature fun, didn’t like lessons page until she saw gamification element
  • Loved the wizard character; requested more color but warned against clutter
  • Wanted more topic suggestions from the chat
  • Praised the budgeting model as clear and educational

Interview - Hui Feng

Participant: Mie

Age: 23

Major: Philosophy

Financial Literacy: Low confidence and low importance, prefers advice from banks

  • Suggested light/dark mode and color customization
  • Felt the profile page is too hidden at the bottom
  • Prefers resource page over lessons, felt she’d never use the lessons
  • Wants ability to bookmark or receive a “receipt” of AI chats
  • Visual learner, prefers example- and picture-based content

Interview - Truc Tran

Participant: Truong

Age: 38

Major: Computer Science

Financial Literacy: Confident in some areas, learns from Google Finance

  • Profile page should be accessible via dropdown, not fixed at bottom
  • Wants income input options (hourly, monthly, yearly)
  • Suggested removing pagination and filters from resource cards
  • Wants categories on lesson page (Budgeting, Saving, Debt, etc.)
  • Sliders on budget model felt imprecise; suggested text input alternative
  • Recommended login page and subtle reminders to update profile later

Interview - Grace

Participant: John

Age: 20

Major: Biology

Financial Literacy: 7/10 confidence, 10/10 importance

Where They Seek Help: Google

Task Feedback

  • Profile Setup: Completed easily, navigation was clear
  • Budgeting Model: Found navigation slightly confusing, but model was intuitive
  • Chat Feature: Easy to use, wants topic suggestions within chat

Additional Insights

  • Loved the app’s design and minimal clutter
  • Believes different users benefit from either lessons or resources depending on their background
  • Enjoys learning by playing with models

Interview Summaries

Interview - Isaiah

Demographic: Male, RTF Major

Financial Literacy: Understands its importance, but not confident

Learning Approach: Relies on Google and websites/emails for answers

AI Knowledge: Very interested and knowledgeable about AI usage

Interview - Julia

Demographic: Female, 19, General Studies

Financial Literacy: Thinks it's important but lacks confidence

Support System: Relies on parents, especially her father, for financial advice

Goals: Wants to improve budgeting and avoid overspending

Interview - Mie

Demographic: Female, 23, Philosophy

Financial Literacy: Doesn’t think it's important, lacks confidence

Support System: Relies on parents and banks for advice

Goals: Wants to learn how to be financially responsible when independent

Interview - Truong

Demographic: Male, 38, Computer Science

Financial Literacy: Confident and considers it important

Focus Areas: Budgeting for bills, saving, and investing

Learning Approach: Uses Google Finance for financial questions

Interview - John

Demographic: Male, 20, Biology

Importance of Financial Literacy: 10/10 – believes it’s key to success

Confidence Level: 7/10

Knowledge Level: 6/10 – knows about credit, stocks, and investing

Learning Approach: Searches on Google for answers

Revisiting What We Wanted To Learn

Resources vs Lesson Page

How do people respond to the resources page vs. the lesson page? Which page is more useful?

  • The model was the highest success with two ways of getting there.
  • Users gravitate towards the lesson page, but having a reference is still important.
Effective Learning Methods

Which learning methods are most effective? (Text, Gamify, Model, Picture)

  • Emphasizing the model is our top priority.
  • The “Duolingo” aspect helped in mapping out a journey from start to finish and made learning less intimidating.
Chat Feature Usage

How would users use the chat feature? (and why?)

  • Most users stated they would use it for questions specific to their scenarios.

Testing Feedback

What We Learned About Users

Users found the app and AI approach interesting and potentially helpful.

They are willing to learn if the information is presented well, as confirmed by their curiosity and follow-up questions.

Feedback

Pros
  • The budgeting model was interactive and fun to use.
  • The UI was clean and uncluttered—users liked the branding and iconography (Wizard).
  • The name and character were unique and stood out.
  • Users found it simple to understand and navigate.
Improvements
  • General: The app should have fewer boxes to avoid overwhelming new users. Removing pagination from the resources page can help.
  • Resources Page: Should be moved under the Lessons page for better navigation. 4-6 resource items are sufficient—pagination, sorting, and filtering may not be necessary.
  • Chat Feature: Users wanted predefined options to choose from within the chatbox.
  • Budgeting Feature: Sliders were imprecise; users requested an additional text field for entering exact amounts. Income estimation should include options like $/hour, $/month, and $/year.
  • Navigation: The order of pages should be adjusted—Profile should not be at the bottom but included in a user dropdown menu.
  • Lessons Page: Needs a clear indication or prompt explaining its purpose and content.
  • Chatbot: Should provide visible options and resources for users, as some interviewees didn’t fully experience its potential in the wireframe.
  • Home Page: A login page with email/password should be included. Users suggested an icon reminding them to update their profile later since some just want information without setting up a profile.

Continuation

Things We Would Want to Change & Refine
  • ChatBox: Implement a receipt or bookmark feature for messages.
  • Theme Color: Introduce both Dark and Light mode options, as well as additional color customization.
  • Bookmark Feature: Allow users to bookmark conversations (potential AI enhancements).
  • More Examples: Expand the mockup with additional use cases and examples.
  • Content Refinement: Reduce wordiness and present information in a more concise, effective manner.
  • Learning Support: Provide more real-world examples to aid user understanding.
Things We Would Continue to Research
  • Resources Page: Determine if users prefer more examples or image-based content.
  • Lesson Page: Identify which lesson types are most useful and which six key topics should be emphasized.
  • User Overload: Ensure lessons are informative but not overwhelming for users.

Looking Back & Launch

What Are Our Priorities?
  1. AI Integration: The main improvement is personalization through AI, making the learning experience more tailored to each user.
  2. Optimized Lesson Delivery: Present the first six topics in the best way possible, seamlessly integrated with the chat feature.
  3. Expanded Learning: Develop a second page with more advanced lessons to support continued learning.

Key Takeaways from Working with a Group on Figma Prototype

Collaboration & Communication

  • Clear Role Definition: Assigning specific responsibilities (e.g., UI design, research, content) helps streamline workflow.
  • Version Control & Feedback Loops: Using comments and Figma’s version history prevents overwriting work and helps track design iterations.
  • Efficient Communication: Regular check-ins via Slack, meetings, or Figma comments help align team goals.

User-Centered Design

  • Iterative Testing is Essential: User feedback drives refinements, and small adjustments can greatly improve usability.
  • Balancing Aesthetics & Functionality: A clean UI must still guide users effectively—avoiding clutter while ensuring clarity.
  • Personalization Through AI: Users appreciate when AI features enhance, rather than replace, human decision-making.

Technical & Design Considerations

  • Consistency Matters: Maintaining a cohesive design system (buttons, fonts, spacing) ensures a professional look.
  • Interactive Prototypes Aid Understanding: Clickable elements help stakeholders and users better visualize functionality.

Project Management & Flexibility

  • Scope Management is Crucial: Prioritizing core features prevents unnecessary complexity, especially in early versions.
  • Adapting to Feedback: Some ideas may not work as expected—being open to change leads to better outcomes.
  • Time Management is Everything: Balancing quality with deadlines ensures steady progress.

Outcomes from Prototyping & User Testing

User-Centered Design Validation

  • Lesson Page Preference: Testing revealed user preference for the Lesson Page, guiding content hierarchy and layout choices.
  • Content Accessibility: Feedback highlighted the need to balance structured lessons with on-demand resource materials to support different learning styles.

Optimizing Learning Experience

  • Gamified & Visual Learning: Interactive models and “Duolingo-style” flows emerged as highly engaging, reducing user intimidation and supporting gradual learning.
  • Digestible Content: Simplifying complex topics into smaller steps increased engagement and lowered the barrier to entry for users with low financial literacy.

Feature Iteration through Testing

  • Scenario-Based Chat: Participants expressed a desire to use the chat feature for personalized, situation-specific help, informing a more contextual chatbot experience.
  • Conversational Design Refinement: Insights from testing led to adjustments in chatbot tone and flow to better mirror user expectations and needs.

Refinement of Information Architecture

  • Streamlined Visual Hierarchy: User feedback prompted reorganization of content and clearer labeling to improve readability and reduce friction.
  • Less Cognitive Load: Emphasizing clarity and spacing helped users better navigate the prototype without feeling overwhelmed.

Strategic Feature Prioritization

  • Focus on MVP Elements: Based on user feedback, core features like the interactive model and lessons were prioritized for refinement.
  • Scalability Planning: User suggestions helped identify future features, such as personalized learning paths and proactive chat prompts.

Foundations for Future Design Iterations

  • Data-Informed Design: Testing insights shaped our product roadmap, grounding design decisions in real user behavior and expectations.
  • Validation of Concept: Positive reception to key features provided confidence in the product’s potential and alignment with user needs.

Designed and Developed by Peter Ahloy, 2025