Parent Career Coach Platform
Discovery Sprint for the Tech Fleet Community
UX Collaboration Showcase
Discovery Sprint for Open Source App
UX Full Cycle TechFleet Team
As a UX Full Stack Design Apprentice on this diverse and talented twelve-person team, we prepared a foundation for an open-source app that would help stay-at-home parents re-enter the workforce.

Tech Fleet is a pending 501(c)(3) that  provides skill-building opportunities and a supportive community to those typically excluded from our industry. Tech Fleet partners with businesses who support their mission and align with their values.
Project
  • Open Source App
  • 4 weeks
  • Volunteer
  • TechFleet.org
Role
  • UX Design Apprentice
  • 12 Member Team UX and Strategy
Tools
  • Userbit Research Tool
  • Figjam
  • Figma
Problem Discovery
Client Baseline Assumptions
  • Parents have outdated skills or gaps in a resume that can make work re-entry challenging
  • After an employment gap, stay-at-home parents lack confidence
  • Building professional networks and relationships while staying at home or after a break can be challenging.
  • Stay-at-home parents cheap and accessible solutions in today’s market.
A Woman working with child
Scholarly Research

With my Family Studies background, I researched scholarly articles for insights and findings prior to starting the survey and interviews to understand the complexity of the issues facing parents.

Insights and Findings
  • Low-Income women are hit the hardest with the job gap rate of 24.9%
  • Top reasons for women are 1) family responsibilities and 2) work-life balance that limit their availability for work
  • Top reasons for gaps are family-related usually to raise a family (48%)
  • Top reason for return to the workforce is need for financial security
  • Other reasons for return include environment (cultural), self-image, skills and abilities, and interests
  • Job search discouragement is also higher for women than men, according to the brief
Creating the Valuable Research Question

It was important to our team to ask the right questions to our interviewees to gain the most valuable findings and insights to drive the product. Our team leads created criteria for collaboration.

Collaboration Process
  • Team collaborated on FigJam
  • Criteria Given: identifying user needs, motivations, assumptions, pain-points, goals and opportunities
  • Top questions voted by team
  • Discussion for any other suggestions
  • Mapped questions in respective categories
  • Questions transferred to Notion to be refined by specific team members
Figjam file representation
How to Get to Know the User
Qualitative Research User Interviews
  • Seven parents interviewed
  • Demographics: college-educated married moms, USA, 30-50 yrs.
  • 2 moms currently had a job, 4 were looking.
qUANTITATIVE rESEARCH - sURVEYS
  • 37 parents from the US took our survey.
  • 54/43 moms and dads.
  • Mostly married, with a variety of educations, careers, and income levels
cOMPETITIVE aNALYSIS
  • 13 potential competitors studied.
  • Job boards, career support, online networking, mentorship sites, & more.
Survey results Image
Research Synthesis

Our team used Userbit to code the interview transcripts and then affinity mapped the vital information. I learned that Userbit is a valuable tool to make the research analysis easier.

Synthesis Method

Userbit Software made coding and collaboration on interviews streamlined. Two team members coded together to keep information less subjective and keep bias low. Tags were moved to FigJam and affinity mapping insights into categories.

Affinity mapping image
JTBD Framework

An effective process for insighs was the Jobs to be done framework. We used the JTBD framework which gave us a rich overall point-of-view of the user needs and struggles.

JTBD framework
JTBD image
JTBD Cards
Insights

After gaining valuable insights, we presented them to the client in slides about the user motivations, needs, and painpoints.

Techfleet Slide 1techfleet slide 2
Ideation to Expand Solutions
Expanding Solutions

Brainstorming the possible key features for future sprints.

Workshop Images
  • Team met for Ideation Workshop to brainstorm solutions that may be used in future phases
  • How Might We statements to solve the user needs and pain points moving forward
  • Used insights from research to keep inline with user needs and goals
Prioritizing Features
Matrix for prioritization
Voting and Discussion
  • Our team used the prioritization matrix for prioritizing “How Might We” statements
  • Each member had to advocate for his/her reasoning and why creating this feature would help the user the most
  • Team discussed placement and voted on most viable options
Next Steps and Hand-off Recommendations
Project Roadmap
Early Steps
  • Create MVP Including career coaching and upskiling resources
  • Get in depth insights through further research
  • Ideate conceptual designs and test them
  • Refine and iterate designs for optimal functionality
  • Finalize the development platform and start laying down initial framework
Later Steps
  • Addition of next prioritised features like Community and Mentorship
  • Identifying additional features based on further research
Up Arrow Button