Fincyclopaedia
Fincyclopaedia is a product that makes the process of finding resources about financial literacy easier by providing the user a variety of financial literacy resources from verified sources and simplifying the more complex components of financial literacy media. Fincyclopaedia will focus on providing the user with verified and trusted information sources specific to their region to make the process of becoming financially literate easier.
Problem Space
Problem Statement
How might we make the process of becoming financially literate easier for young adults so that they can learn easily without spending too much time searching for credible and easy to use resources?
Problem Background
This product is for individuals who are seeking financial literacy but either do not know where to begin the search for resources or are wary of the credibility of resources found online. With the vast amount of information available both on the internet and on social media platforms, determining what information is true and what is not can be a bit challenging. The difficulty that comes with sorting through various resources to separate the reliable sources from unreliable sources was cited by 53.8% of surveyed users as one of the main challenges impacting their motivation to keep searching for financial literacy resources.
Based on user research, motivation to become financially literate stemmed from a variety of places. For the majority of users surveyed and interviewed (67%), 3 major sources of motivation were: being able to afford anything at any time, being able to provide for family and being able to make balanced decisions about money.
Lowering (and eventually removing) barriers such as those mentioned above will make the process of learning about financial literacy easier, more accessible and a lot less stressful for people.
Research Insights
User Pain Points
User research was performed using surveys and interviews. Information gathered from user surveys and interviews shows that the major main points experienced by target users were: difficulty finding resources that matched their learning style, difficulty understanding the meaning of certain words/phrases, and lack of verified information sources.
Supporting Data
Based on the survey responses of 65 users and 3 user interviews, we discovered that 58.5% of users seeking financial literacy information faced challenges in finding resources that catered to their learning style. Additionally, 52.3% of users found financial literacy jargon difficult to comprehend, while 53.8% expressed concerns about the reliability of online information.
Feedback
User feedback suggests that users are most interested in having access to information and resources that have been reviewed and verified by reliable sources like banks and financial experts, especially if it is information from a source they are not familiar with.
Landing on the Solution
Based on our target users’ pain points, we know we want to build a product that:
- Provides users with direct access to simplified lessons on financial topics.
- Provides users with access to external resources covering financial topics.
- Provides users with access to resources in various formats( text, video and audio) to cater to different learning styles.
- Provides users full transparency on credentials of internal and external resources recommended.
Future steps
I plan to continue building this product into an MVP at COLAB 21. I would like to gain more in depth knowledge on how to be a good PM by working with a cross-functional team to flesh out the features for Fincyclopaedia.
Learnings
Product Manager Learnings:
Nmesoma Akwajah
Co.Lab was a very valuable experience for me. My main takeaways from this Sprint were:
- Prioritising target users is very important when building a product. Ensure that the product and its features are things the users actually want to see and use.
- Part of prioritising target users is focusing more on the problem space while building a product. Asking more “why” and less “how” to fully understand what pain points users experience rather than jumping straight into trying to find a solution.
- Data is extremely valuable in the world of product development, and good data is even more valuable. During my time at Co.Lab, I gained insights on how to effectively ask users questions during the research phase of building a product.
Designer Learnings:
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
&
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.