TEAM
6 Project Strategists, 6 UX Researchers, 1 Tech Consultant
MY ROLE
Product Strategist
TIMELINE
July 2023 - August 2023
BACKGROUND
The Melanin Village (TMV) was founded by a Black mother to address the lack of Black History education in American schools. It serves as a supportive hub for Black and Brown homeschooling families, offering community, meetups, and resources while promoting comprehensive Black history education.
WHAT THIS PROJECT MEANS TO ME
As a person of color, I deeply resonate with Melanin Village's mission to empower Black and Brown communities through education, resources, and engagement. Contributing to a project that uplifts underrepresented communities was truly fulfilling, and I am honored to support a cause I wholeheartedly believe in.
THE CHALLENGE
• The use of multiple platforms lead to inefficiencies in the admin workflow
• Customers struggle to navigate the website, hindering access to key information like sign-up, waitlist, and eligibility
• Paying customers face usability issues with the education platform due to its complex tech stack
THE SOLUTION
Consolidate admin tools, enhance website navigation for easier access to key information, and simplify the education platform’s tech stack to improve usability for paying customers.
Product Strategy for a Homeschooling Business
Product Strategy for a Homeschooling Business
Product Strategy for a Homeschooling Business
In Phase 0 of this project, my team and I developed a research-driven product strategy that consolidated the back-end platform for admins and optimized the front-end for a user-centered experience. While we don’t have access to numerical impact data, our work set the foundation for reducing business costs and enhancing user engagement.
In Phase 0 of this project, my team and I developed a research-driven product strategy that consolidated the back-end platform for admins and optimized the front-end for a user-centered experience. While we don’t have access to numerical impact data, our work set the foundation for reducing business costs and enhancing user engagement.
TEAM
6 Project Strategists, 6 UX Researchers, 1 Tech Consultant
MY ROLE
Product Strategist
TIMELINE
July 2023 - August 2023
BACKGROUND
The Melanin Village (TMV) was founded by a Black mother to address the lack of Black History education in American schools. It serves as a supportive hub for Black and Brown homeschooling families, offering community, meetups, and resources while promoting comprehensive Black history education.
WHAT THIS PROJECT MEANS TO ME
As a person of color, I deeply resonate with Melanin Village's mission to empower Black and Brown communities through education, resources, and engagement. Contributing to a project that uplifts underrepresented communities was truly fulfilling, and I am honored to support a cause I wholeheartedly believe in.
THE CHALLENGE
• The use of multiple platforms lead to inefficiencies in the admin workflow
• Customers struggle to navigate the website, hindering access to key information like sign-up, waitlist, and eligibility
• Paying customers face usability issues with the education platform due to its complex tech stack
THE SOLUTION
Consolidate admin tools, enhance website navigation for easier access to key information, and simplify the education platform’s tech stack to improve usability for paying customers.
TEAM
6 Project Strategists, 6 UX Researchers, 1 Tech Consultant
MY ROLE
Product Strategist
TIMELINE
July 2023 - August 2023
BACKGROUND
The Melanin Village (TMV) was founded by a Black mother to address the lack of Black History education in American schools. It serves as a supportive hub for Black and Brown homeschooling families, offering community, meetups, and resources while promoting comprehensive Black history education.
WHAT THIS PROJECT MEANS TO ME
As a person of color, I deeply resonate with Melanin Village's mission to empower Black and Brown communities through education, resources, and engagement. Contributing to a project that uplifts underrepresented communities has been incredibly fulfilling, and I’m honored to support a cause I deeply believe in.
THE CHALLENGE
• The use of multiple platforms lead to inefficiencies in the admin workflow
• Customers struggle to navigate the website, hindering access to key information like sign-up, waitlist, and eligibility
• Paying customers face usability issues with the education platform due to its complex tech stack
THE SOLUTION
Consolidate admin tools, enhance website navigation for easier access to key information, and simplify the education platform’s tech stack to improve usability for paying customers.
The Approach
The Approach
The Approach
FINDING COMMON PATTERNS
FINDING COMMON PATTERNS
Upon starting this project, we received a detailed document from the business owner outlining platform pain points affecting her workflow and customer experience. We categorized these issues into common themes and developed a comprehensive tech stack to address them.
Upon starting this project, we received a detailed document from the business owner outlining platform pain points affecting her workflow and customer experience. We categorized these issues into common themes and developed a comprehensive tech stack to address them.
ADMIN PAIN POINTS
ADMIN PAIN POINTS
USER PAIN POINTS
USER PAIN POINTS
IDENTIFYING STRENGTHS AND OPPORTUNITIES
IDENTIFYING STRENGTHS AND OPPORTUNITIES
To understand TMV's tech stack, we first mapped out the platforms and integrations in use (image below), providing a clear view of their purpose and significance.
I then conducted a SWOT analysis to assess each platform’s value proposition, strengths, weaknesses, opportunities, and risks. We also created user flows for admins and both potential and current customers to evaluate their navigation through the website and internal platforms (not shared due to privacy concerns).
This process helped uncover additional issues within each integration, allowing us to refine and categorize them more effectively.
To understand TMV's tech stack, we first mapped out the platforms and integrations in use (image below), providing a clear view of their purpose and significance.
I then conducted a SWOT analysis to assess each platform’s value proposition, strengths, weaknesses, opportunities, and risks. We also created user flows for admins and both potential and current customers to evaluate their navigation through the website and internal platforms (not shared due to privacy concerns).
This process helped uncover additional issues within each integration, allowing us to refine and categorize them more effectively.
To understand TMV's tech stack, we first mapped out the platforms and integrations in use (image below), providing a clear view of their purpose and significance.
I then conducted a SWOT analysis to assess each platform’s value proposition, strengths, weaknesses, opportunities, and risks. We also created user flows for admins and both potential and current customers to evaluate their navigation through the website and internal platforms (not shared due to privacy concerns).
This process helped uncover additional issues within each integration, allowing us to refine and categorize them more effectively.
TMV's platforms and integrations shown above
TMV's platforms and integrations shown above
What Surveys Reveal About our Users
What Surveys Reveal About our Users
While my team focused mainly on understanding and identifying the user problems in order to define the MVP, the UX team assisted us in gathering user insights.
Some useful insights we found were that paying members:
• Do not take advantage of the resources provided due to technical difficulties.
• Have a ton of questions that are left unanswered.
• Would love to see more social features on the platform to stay connected with others (i.e. video chat feature, group messaging, friend suggestions).
While my team focused mainly on understanding and identifying the user problems in order to define and prioritize the MVP, the UX team assisted us in gathering user insights.
Some useful insights we found were that paying members:
• Do not take advantage of the resources provided due to technical difficulties.
• Have a ton of questions that are left unanswered.
• Would love to see more social features on the platform to stay connected with others (i.e. video chat feature, group messaging, friend suggestions).
While my team focused mainly on understanding and identifying the user problems in order to define and prioritize the MVP, the UX team assisted us in gathering user insights.
Some useful insights we found were that paying members:
• Do not take advantage of the resources provided due to technical difficulties.
• Have a ton of questions that are left unanswered.
• Would love to see more social features on the platform to stay connected with others (i.e. video chat feature, group messaging, friend suggestions).
Users reported a strong correlation between the frequency of platform use and the level of difficulty they encounter in navigating these platforms.
Users reported a strong correlation between the frequency of platform use and the level of difficulty they encounter in navigating these platforms.
Uncovering Root Issues Through Problem Statements
Uncovering Root Issues Through Problem Statements
Using insights from the survey, we conducted another round of user problem categorization, which gave us the opportunity to develop problem statements. These statements helped us understand the root issues from the user’s perspective, guiding us in brainstorming potential solutions.
Using insights from the survey, we conducted another round of user problem categorization, which gave us the opportunity to develop problem statements. These statements helped us understand the root issues from the user’s perspective, guiding us in brainstorming potential solutions.
This image shows the problem statements we created, highlighting user problems, motivations, expectations, and emotions.
This image shows the problem statements we created, highlighting user problems, motivations, expectations, and emotions.
Do We Have an
MVP Yet?
Do We Have an MVP Yet?
Do We Have an MVP Yet?
Well.. we're getting there!
In Phase 0, our goal was to define the blueprint for the Minimum Viable Product (MVP) before passing our research and strategies to the Phase 1 team. We started by developing multiple MVP options and outlining their corresponding features (see image below), then prioritized these features into low, medium, and high categories.
The MVP options focus on key areas, divided into user and admin functionalities:
(1) building a community-driven platform
(2) designing a curriculum for both parents and children
(3) managing user data migration
Segmenting the project this way helped create a clear roadmap and prioritize each phase effectively.
The features were selected based on the following considerations:
• Incremental value: Which features contribute most to the product’s success metrics?
• Cost: What are the costs of platform subscriptions and maintaining custom solutions?
• Risk: What challenges might arise during feature creation and after implementation, such as timeline delays, skill gaps, and future operational issues?
Additional considerations for the MVP included business values, user needs, and technical specifications. By following these criteria, we aimed to select features that would drive the MVP’s success while keeping costs in check and minimizing potential risks.
Well.. we're getting there!
In Phase 0, our goal was to define the blueprint for the Minimum Viable Product (MVP) before passing our research and strategies to the Phase 1 team. We started by developing multiple MVP options and outlining their features (see image below), then prioritized these features into low, medium, and high categories.
The MVP options focus on key areas, divided into user and admin functionalities:
(1) building a community-driven platform
(2) designing a curriculum for both parents and children
(3) managing user data migration
Segmenting the project this way helped create a clear roadmap and prioritize each phase effectively.
The features were selected based on the following considerations:
• Incremental value: Which features contribute most to the product’s success metrics?
• Cost: What are the costs of platform subscriptions and maintaining custom solutions?
• Risk: What challenges might arise during feature creation and after implementation, such as timeline delays, skill gaps, and future operational issues?
Additional considerations for the MVP included business values, user needs, and technical specifications. By following these criteria, we aimed to select features that would drive the MVP’s success while keeping costs in check and minimizing potential risks.
Additional considerations for the MVP were business values, user values, and technical specifications.
Additional considerations for the MVP were business values, user values, and technical specifications.
Where Do We Start?
Where Do We Start?
To better prioritize features, we constructed an effort-impact matrix. This allowed us to visually assess which features could be implemented within the limited timeframe. Our analysis revealed that prioritizing user flows, UI enhancements, and customer-centric step-by-step processes were more feasible than integrating multiple platforms.
To better prioritize features, we constructed an effort-impact matrix. This allowed us to visually assess which features could be implemented within the limited timeframe. Our analysis revealed that prioritizing user flows, UI enhancements, and customer-centric step-by-step processes were more feasible than integrating multiple platforms.
The value is determined by considering the following factors:
• The number of users impacted (262 members, with around 130 active users).
• The potential value, benefit, and revenue the feature could generate, as well as the speed of its value increase.
• The level of effort needed to develop the feature.
The value is determined by considering the following factors:
• The number of users impacted (262 members, with around 130 active users).
• The potential value, benefit, and revenue the feature could generate, as well as the speed of its value increase.
• The level of effort needed to develop the feature.
Prepping for the Next Phase
Prepping for the Next Phase
Prepping for the Next Phase
what's next???
what's next???
To guide our goal setting and evaluate the impact of our work, we've outlined potential Key Performance Indicators (KPIs) and defined SMART goals for different timeframes: short-term and long-term (5 and 10+ years).
For the next phase (Phase 1), our plan is to hold a product vision workshop with the business owner, revisit the problem statements from Phase 0, review the feature list, and prioritize features together.
To guide our goal setting and evaluate the impact of our work, we've outlined potential Key Performance Indicators (KPIs) and defined SMART goals for different timeframes: short-term and long-term (5 and 10+ years).
For the next phase (Phase 1), our plan is to hold a product vision workshop with the business owner, revisit the problem statements from Phase 0, review the feature list, and prioritize features together.
To guide our goal setting and evaluate the impact of our work, we've outlined potential Key Performance Indicators (KPIs) and defined SMART goals for different timeframes: short-term and long-term (5 and 10+ years).
For the next phase (Phase 1), our plan is to hold a product vision workshop with the business owner, revisit the problem statements from Phase 0, review the feature list, and prioritize features together.
HANDOFF
HANDOFF
To help Phase 1 start their product strategy journey, we gathered all Phase 0 documents and deliverables in a Notion page. We also listed the following recommendations:
• Review the deliverables and understand the tech stack along with the pain points that the business owner highlighted.
• Organize a workshop with the UX Research team to integrate survey and interview insights into the features list.
• Involve a developer in an MVP workshop to assess the technical effort required for feature selection.
To help Phase 1 start their product strategy journey, we gathered all Phase 0 documents and deliverables in a Notion page. We also listed the following recommendations:
• Review the deliverables and understand the tech stack along with the pain points that the business owner highlighted.
• Organize a workshop with the UX Research team to integrate survey and interview insights into the features list.
• Involve a developer in an MVP workshop to assess the technical effort required for feature selection.
To help Phase 1 start their product strategy journey, we gathered all Phase 0 documents and deliverables in a Notion page. We also listed the following recommendations:
• Review the deliverables and understand the tech stack along with the pain points that the business owner highlighted.
• Organize a workshop with the UX Research team to integrate survey and interview insights into the features list.
• Involve a developer in an MVP workshop to assess the technical effort required for feature selection.
What We Learned
What We Learned
What We Learned
CHALLENGES WE FACED
CHALLENGES WE FACED
• Lack of developer guidance made it difficult to assess the feasibility of each feature idea or solution.
• The complexity of the tech stack made it challenging to account for all technical interactions.
• Insufficient survey responses prevented a timely comparison with the features and requirements list.
• Lack of developer guidance made it difficult to assess the feasibility of each feature idea or solution.
• The complexity of the tech stack made it challenging to account for all technical interactions.
• Insufficient survey responses prevented a timely comparison with the features and requirements list.
WHAT WE WOULD'VE DONE DIFFERENTLY
WHAT WE WOULD'VE DONE DIFFERENTLY
• Involve developers early to assess the project’s technical feasibility.
• Send user surveys early to understand user needs before brainstorming solutions.
• Include the business owner in workshops to align with her vision and goals.
• Involve developers early to assess the project’s technical feasibility.
• Send user surveys early to understand user needs before brainstorming solutions.
• Include the business owner in workshops to align with her vision and goals.
WHAT I LEARNED FROM THIS
WHAT I LEARNED FROM THIS
• User research is the foundation — understanding user problems early ensures a strong product strategy.
• A well-defined product strategy is essential — it sets the scope and priorities for development.
• Collaboration strengthens outcomes — workshops facilitate idea generation, and working closely with stakeholders leads to better decisions.
• User research is the foundation — understanding user problems early ensures a strong product strategy.
• A well-defined product strategy is essential — it sets the scope and priorities for development.
• Collaboration strengthens outcomes — workshops facilitate idea generation, and working closely with stakeholders leads to better decisions.
Applying What I’ve Learned in My Job
Applying What I’ve Learned in My Job
Applying What I’ve Learned in My Job
Overall, I’m really happy with how this project turned out. Before working with TMV, I often rushed into solutions without fully understanding the problems. Since then, I’ve applied what I’ve learned to my role as a Product Designer/UX Researcher at Spartan Solar. By making changes to my design process—like doing more research early on, improving collaboration with stakeholders, and holding workshops—I’ve noticed a significant amount of time saved on projects. I’ve also received better feedback from both stakeholders and users.
Overall, I’m really happy with how this project turned out. Before working with TMV, I often rushed into solutions without fully understanding the problems. Since then, I’ve applied what I’ve learned to my role as a Product Designer/UX Researcher at Spartan Solar. By making changes to my design process—like doing more research early on, improving collaboration with stakeholders, and holding workshops—I’ve noticed a significant amount of time saved on projects. I’ve also received better feedback from both stakeholders and users.