Product Experience

Introduction

Core Connect gives tech professionals the sustainable and dynamic resource of mentorship with core values. Core values guide employees on how to prioritize when making challenging decisions, navigating various relationships with less conflict and more collaboration, while giving greater meaning and results in their work. Core values also serve as a map for companies on how employees and leadership can better solve problems and differentiate themselves from competitors. By knowing each other’s core values a mentee can match with an experienced professional mentor for more meaningful and resonant answers based on their real life experiences.  

Companies prioritizing core values had a 175% increase in value over a 12-year period

63% of consumers say they want to buy products and services from companies that have a purpose that resonates with their values and belief systems

Problem Background 

In the rapidly changing tech industry, users have specific and personalized problems that often can’t be solved in community boards, courses, and even the most up to date resources. Aspirants are moving away from a variety of industries and backgrounds and into tech creating unique and diverse needs for learning and development. Both professionals and aspirants need refined resources to advance in their careers because the current offerings lack meaningful results and reliability.

Research Insights

User Pain Points

After several interviews and surveys completed, we learned the following:

  • 66% of users experience hindrance in personal growth when working in a team with unaligned core values.
  • Majority of users have trouble efficiently finding a mentor online. First priority in finding a mentor is their professional background and second is their personality.
  • If there is no indicator, most users question if mentors are still active on the platform. Many users experienced booking a session and never hearing from the mentor and/or the mentor not showing up to their scheduled meeting.
  • Mentors leave mentorship platforms because they feel the connection with the mentee is lacking fulfillment and meaning. Mentors also feel mentees are solely looking for FAANG employees with the most years of experience and dehumanizes the experience. Decreased mentor engagement leads to a cyclical effect of both mentors and mentees dropping from the platform.

Why Now?

The greater problem is employee dissatisfaction and high turnover rates:

  • The 2023 tech employee turnover rate is 18.3% - the highest turnover rate of any sector
  • Resignation rates are higher for senior-level employees compared to mid-level
  • Mentorship is the #1 focus area for L&D programs in 2023
  • Of those with a mentor, 97% say they are valuable, yet only 37% of professionals have a mentor meaning there is a large untapped market. 

Solution Explanation

Through a more symbiotic mentor and mentee relationship, employees can find meaningful, empathetic, and truly personalized actionable answers from real life successes to their questions improving work performance, retention, and satisfaction.

  • More efficiency and enjoyment searching and matching experience
  • Able to meet clearer expectations
  • More meaningful and productive sessions
  • Build a network of like-minded professionals
  • Practice soft-skills for communicating with a challenging coworker by matching based on their core values

Core Connect’s key features:

  1. Core value test: a quick test that users can take before starting the mentor search. Although 77% of users noted that they know their top professional core values, we wanted to encourage the remaining 23% to engage with the core values filter. Additionally, Values Institute states that there is a chance of one’s core values changing depending on their life stage and age. 
  2. Core values as a filter, along with others: with 66% of users having experienced hindrance in their personal growth when working in a team with unaligned core values, we found it significant to allow users to search mentors using aligned core values. Users also expressed their need for more specific filters to make the ‘mentor-searching’ process more efficient. Other specific filters include availability, industry, discipline, experience level, and company size. 
  3. Specific information on mentor profiles: with users’ priority when choosing a mentor being professional background and what mentor is like, it made sense to add mentors’ past work experiences, core values, and what led them to mentoring. Category tags of what mentors can help with were also added to assist users in choosing a mentor. 
  4. Mentor’s last active time indicator: given that most users want some kind of indicator that shows the mentor is indeed active on the website, we added a section showing when the mentor was last active on the platform. This feature provides some reassurance and guidance to who the user wants to book a session with.

Lofi & Hifi Mockups

Iterative Design Learnings

After usability testing, we learned:

  • Users find our 3 main tasks’ flows (below) to be intuitive & straightforward
  1. Taking the core value test
  2. Filtering to find a mentor 
  3. Selecting a date and submitting a mentorship request form
  • Users like the clean design overall
  • Other feedback: 
  1. It would be helpful to see mentor’s portfolio/website
  2. It’s not very clear that the filter options are like checkboxes, where multiple things can be selected at once
  3. It would be easier to select if Core value filter dropdown is bigger

Implementation Details 

Technical implementation

Where is it hosted? 

  • Netlify - a free hosting website which allows for custom subdomain and uncustomized second-level domain. In addition, it integrates into github easily and auto updates when files are changed on github.

What is your tech stack?

  • React - front end
  • JSX -  files
  • Tailwind CSS - inline styling
  • MUI - specific styling for calendar
  • Vite - frontend tooling
  • Figma - design

High level journey of a request?

  • The request is usually made by our project manager, designed by our designer on Figma. The idea is added to our Trello where it is moved from the backlog to the in progress by the developers, until one or both developers are able to complete it then it is updated on our github by moving it to the main branch, which updates our website. Our Trello is then updated to show completion. Our designer reviews the updated work and gives feedback. The feedback usually requires changes and updates. The cycle repeats until the designer and product manager sign off on it.

Technical challenges

What was the hardest part of development?

  • Managing states in the core value test was challenging. But filtering mentors on the homepage is proving more of a challenge since we are using 5 different elements to filter one data set.

Does your app have any scaling issues?

  • Not necessarily, we tried to code with keeping in mind features we would like to add on and leaving the option open for them. One of the biggest things we would like to add is a backend for storing user/mentor data

What are some key takeaways?

  • Taking the time to map out the basic logic for a given page/component before writing it all out can save a lot of time later on in going back and debugging
  • Understanding proper source control is very valuable for working on team
  • Consistent and detailed communication between developers is very important to make sure they work together and not overwrite each other in programming
  • Variable naming and proper documentation is really important to making readable/debugable code

Future Steps

Beyond the time restrictions of this MVP features we would like to add include:

Go-To-Market Strategy

Focusing on building a strong mentor network we would:

  • Convert existing successful tech mentors and create solutions to their problems
  • Approach mentors who left existing platforms since their contact info is commonly on their profiles 
  • Design messaging that empathizes with the reasons they joined/left
  • A/B test cold/warm emails based on industry, role, and experience
  • Create networking spaces for mentors to find community and advance their mentoring skills

Competitors

In anticipation of competitors adding a core value feature, we would ongoingly establish relationships and interviews of top users in order to prioritize features that further improve their experience by focusing on:

  • Growth on NPS
  • New Users
  • New net MMR
  • Scheduled Meetings
  • 5 Star Mentor Reviews

Target Personas

Based on competitor data we would tailor content, advertising, and services to align with the demographic and age distribution of this target audience, critically emphasizing cultural understanding and resonance including:

  • More males than females
  • Predominantly aged 25-34
  • Mobile-friendly
  • Incentivize users to create content and promote on LinkedIn and YouTube

Monetization

Competitors utilize a variety of fee-based models:

  • Subscription
  • Subscription with Optional Pay-Per-Service (as specified by the mentor)
  • Pay-Per-Service 
  • Donation-Based
  • Free
  • Funded by partnered software subscriptions
  • Funded by investors

Freemium

We would implement a freemium model where users pay for a subscription after a free trial. To increase our experienced mentor base and engagement we would give the option for mentors to set an additional fee. 

80/20 Rule

To establish regular streams of revenue we would sign contracts with companies that have existing L&D budgets and find them by:

  • Exhibiting and/or presenting at tech conferences
  • Approach HR Managers and other decision makers
  • Design messaging the solves their key pain points based on Glassdoor reviews and recent articles
  • A/B test cold/warm emails based on company size and competitors
  • Prioritizing companies that have defined their core values

Images

Other high resolution images

Learnings

Product Manager Learnings:

Anisa Charucksiri

I discovered that it is much more fulfilling to solve the pain points of key stakeholders, experienced mentors, versus duplicating what’s already in the market.

I learned that mentorship really does provide direction and answers both through my research as well as my direct experience with mentors.

I gained value in CoLab’s communities including my team, fellow PMs in the cohort, and through the community at large.

Designer Learnings:

Katie Kim

I learned how to communicate user-centric design decisions throughout a product cycle, and that this allows the team to be on the same page with project priorities 

I learned how to utilize visual narratives including user persona, user flows, and sitemap to share research findings and project’s goals with the team

I learned that collaboration is entering conversations with willingness to learn from the other person while sharing my own expertise.

Designer Learnings:

Jo Sturdivant

  1. 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.
  2. 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.
  3. 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:

Jayden Evens

Learning how to collaborate with your code so that when you are merging to the main branch there is not too much conflict to correct

Making sure everything is connected inside the code so that it is scalable and that it makes the UX seamless.

One thing I think as a hindsight is declaring objects as a group rather than winging it and having to add more as we move on.

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:

Lukas Reeves

&

Working on a team requires consistent, specific and thorough communication

Filtering in is much more challenging than I anticipated

Many problems in programming on a team can be prevented or reduced by delegation and proper planning ahead

Use good variable names and document code well for debugging other developer

Developer Learnings:

Maurquise Williams

&

  1. 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.
  2. 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.
  3. 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.

Full Team Learning

We learned the benefits of working in a team and leaning on each other’s expertise in order to optimize the outcome of our MVP. We each had differing working schedules and personal inhibitors come up during the 8-weeks but were able to still meet each week’s submissions because of open dialogue, finding solutions for the few small communication gaps that came up, and came up with new collaboration tools that weren’t provided for working asynchronously.

We learned that we could navigate unknowns and road bumps, like not knowing our midpoint demo date and the many unexpected bugs in our site, by being mentally prepared for longer hours and adapting quickly for fast-approaching deadlines and by finding camaraderie in one another.

Because we each come from different backgrounds, we learned new ways to communicate effectively and efficiently and found that aligning on key requirements and goals to be incredibly helpful.