I was assigned a new feature to design for Sprint 3 and 4: The Match Questionnaire
From concept to questionnaire..
Purpose:
The purpose of the Match Questionnaire is to provide match recommendations that are more alignment with a Mentee's goals and interests.
Priorities:
Easy navigation for a mentee to take/re-take the quiz as goals change
Iterating on matching results by providing “good” or “great” matches instead of matches based on percentages like previously designed
Adding a tag system that allows users to add more options they may not see listed
Side nav progress panel
Results page (Shown after completing)
Tag system answer format
Feature: Match Questionnaire
Feature: Match Questionnaire
Time for a Facelift
Along with designing the Match Questionnaire feature, I was also tasked with iterating on the Search & Filter side panel.
This side panel was first built and handed off in the previous phase. Our team analyzed the handoff design and decided to make a few changes based off new insights gathered from user testing.
Before




The Sort & Filter header was updated with brand coloring to help with visibility when viewed by users
After
Feature: Sort & Filter
Feature: Sort & Filter
Mentor Card


Copy/location information displayed to mentees found to be unnecessary
% match tag created uncertainty on how to measure this metric/feasibility issues with dev team
Before


After
Added a color coded tag system displaying focus areas for that mentor
Final copy displayed to mentee:
- Name
- Job title
Added availability tag
For better viewing, some visual assets are hidden in this view. To see more please view this section via tablet or desktop mode!
Breaking ground on design tasks
After getting properly oriented, each member on UXD Team 1 was assigned flows they would be designing for.
Our team faced unique challenges as a mix of new and veteran designers that would be iterating on designs handed off from the previous phase. We also put our focus on adapting our design tasks to align with our minimum viable product (MVP).
Tasks I worked on specifically are listed below:
- Mentor card re-design
- Sign Up Modal & Email verification flows
- Match Questionnaire flow
- Search and filter flow
Below are the handed off designs from Phase 1. These are the designs we would be iterating on:


Mentor Card
Filter


With a strong foundation for our design process established, it was time to invest in a new design system.
We collaborated closely with the Dev team and decided to go with the Ant Design System after confirming it was compatible with React and Next.js



Logo/Branding
Icon Kit
Icon Set
Logo/Branding
Here's why we chose the Ant Design System!
Old design system wasn't feasible with the framework the dev team was using
Enabled more control over design of the product
Encouraged better collaboration between Dev & Design
Ensured near seamless crossover between the prototype and live product
Ability to customize and tailor to branding
Icon Set
Inputs/Components
Color Palette
Typography
Input
First name
Checkbox
Checkbox filled
Great match
Available now
Input focused
First name
Montserrat
Work Sans


Our Design System
Our Design System
With our HMW questions established, we re-analyzed our mentee user flows to confirm our design direction for features like onboarding, the match questionnaire and finding a mentor.
This set us up for a strong foundation to begin iterating on existing screens that were handed off from the last phase. We then moved into picking a new design system and assigning design tasks.


Re-working Artifacts
Re-working Artifacts
Tap the image above to inspect more closely


After analyzing the research from Phase 1...
We used the key insights to inform our design process and structure our How Might We questions.
Below are the How Might We questions that we chose to focus on in our design process for this phase:
1
How might we establish a mutual connection between mentor and mentee to ensure a good fit?
2
How might we ensure users feel safe and secure?
3
How might we give mentees and mentors the opportunity to develop long term mentorships?
4
How might we provide guidance to users throughout the process and reduce any confusion in our user flows?
5
How might we get users excited to book their first session?
6
How might we provide clarity and transparency for users?
How Might We Questions
How Might We Questions
Moderated & Unmoderated Usability Testing
Key Findings & Themes
Safety, Trust and Transparency
Users want to feel safe
Users want to feel like they have choices and agency
Users want consent by a two-way street
Inclusivity and Belonging
User want to feel like they are making informed decisions
Users care about learning the most they can about the program
Increased Clarity and Guidance
Users need more clarity and guidance through profile due to varied life experiences
Users want an intuitive process
Want to Know More
Support offered and bios - most interesting pieces of information
Expressed nervousness around the mentor having no input in booking the session
Would they be a good fit?
Value of the mentor to me - what has the mentor helped/what have they accomplished?
Filtering Categories
Industry experience categories
Confusion around expertise and industry
Difficulty finding toggle button at the button
Long term vs. short term
Mentorship minutes were unclear
Scheduling
Users want an intuitive process
Booking Monday is the most commonly used
Research was conducted in Phase 1 to understand the needs and pain points from the mentee user perspective.
My team used the research insights from Phase 1 to inform our design process and form the How Might We questions for this phase so that we could hit the ground running.
Background
Phase 1 ResearchOverview
Multiple types of testing:
Unmoderated
Moderated
Consistent Themes
Security, privacy and trust
Inclusivity and belonging
User friendliness
Transparency and guidance
Read the full UXR Report here!


Build on Phase 1’s work and explore new features for mentee users:
Develop core features designed in Phase 1
Address design debt and iterate on handed off Phase 1 designs and user flows
Ideate on and design new features for mentee users
Design Process:
Our team worked via an agile work flow using 2 week sprints to design/iterate on new and existing features from the previous phase.
Each sprint concluded with a round of feedback from the overall team as well as a retrospective.
Deliverables:
Finalized Onboarding Flow
Finished Sort/Filter Panel
Finished Match Questionnaire
High Fidelity Prototype


As always, thank you for scrolling and if you’d like to see the current working prototype developed in collaboration with us and the Development team please feel free to jump to the prototype section above or click the button below to see the current tester!
Next Steps
Next Steps
This project will move into Phase 3 after review on how this phase went.
My next steps look like this:
This project will move into Phase 3 after some review on how this phase went for the overall team.
That being said my next steps look like this:
This project will move into Phase 3 after review on how this phase went.
That being said my next steps look like:
- Preparing for leadership in a Co-Lead role for the UXD Team
- Usability testing with a focus on features designed in this phase
- Onboarding and assisting new designers that join the team
- Preparing for leadership in a Co-Lead role for the UXD Team
- Usability testing with a focus on features designed in this phase
- Onboarding and assisting new designers that join the team
(Update: Phase 3 was completed January 2024, UXD Lead Case Study coming soon!)
- Preparing for leadership in a Co-Lead role for the UXD Team
- Usability testing with a focus on features designed in this phase
- Onboarding and assisting new designers that join the team












UPDATE: Phase 3 was completed January 2024!
Look out for a UXD Design Lead Case Study coming soon!
UPDATE: Phase 3 was completed January 2024!
Look out for a UXD Design Lead Case Study coming soon!
We’ve Arrived at the End of the Case Study
We’ve Arrived at the End of the Case Study
Overall, my team enjoyed experiencing success in wrapping up our final designs and presenting them and the final prototype to our client.
We handed off our annotations and gathered to discuss what happens next...
Overall, my team enjoyed experiencing success in wrapping up our final designs and presenting them and the final prototype to our client.
We handed off our annotations and gathered to discuss what happens next...


Conclusion
Conclusion
Conclusion
What were some of the major takeaways my team and I gained from this project?
What were some of the major takeaways my team and I gained from this project?
Mid-phase we had miscommunications arise between other teams that cost us time in the long run:
- The UX Content team had to repeatedly review copy changes after pivots happened. The copy they already reviewed would get changed again and again. This caused inefficient time loss and frustration for both teams.
- The Development team had extra hands to work on different screens but due to a complex standardized format for submitting designs, the UXD team was too overwhelmed to be able to meet those standards for submitting tickets and the whole system had to be revised mid-phase.
Mid-phase we had miscommunications arise between other teams that cost us time in the long run:
- The UX Content team had to repeatedly review copy changes after pivots happened. The copy they already reviewed would get changed again and again. This caused inefficient time loss and frustration for both teams.
- The Development team had extra hands to work on different screens but due to a complex standardized format for submitting designs, the UXD team was too overwhelmed to be able to meet those standards for submitting tickets and the whole system had to be revised mid-phase.
The Importance of Effective Collaboration
Moral of the story: Effective collaboration takes intentional effort in all areas of a team and although its hard to get perfect, mistakes like these helped me realize just how effective timely and efficient communication between teams is.
Moral of the story: Effective collaboration takes intentional effort in all areas of a team and although its hard to get perfect, mistakes like these helped me realize just how effective timely and efficient communication between teams is.
TLDR/Moral of the story


Usability Testing - The UXR team focused on testing for the mentor’s perspective only for this phase, so we did not have the ability to test for the mentee’s POV. Due to this, we had to rely on user testing done in Phase 1 only.
Usability Testing - The UXR team focused on testing for the mentor’s perspective only for this phase, so we did not have the ability to test for the mentee’s POV. Due to this, we had to rely on user testing done in Phase 1 only.
We structured our designs off of the research insights gathered in Phase 1 and used those to inform our design process.
After finishing this phase our team put together a document that had recommendations for what to test in the next phase
We structured our designs off of the research insights gathered in Phase 1 and used those to inform our design process.
After finishing this phase our team put together a document that had recommendations for what to test in the next phase
Changing scope - The onboarding flow was changed three different times during the phase due to client requests. This unfortunately pushed our timeline back.
Changing scope - The onboarding flow was changed three different times during the phase due to client requests. This unfortunately pushed our timeline back.
We did what designers do best in Agile--we adapted to each change requested and pivoted each time.
Unfortunately this did put our timeline off but we re-aligned our goals to deliver high fidelity designs for the onboarding flow and were successful!
We did what designers do best in Agile--we adapted to each change requested and pivoted each time.
Unfortunately this did put our timeline off but we re-aligned our goals to deliver high fidelity designs for the onboarding flow and were successful!
What were some of the main challenges we faced in this project?
What were some of the main challenges we faced in this project?
How did we adapt and overcome these challenges?
How did we adapt and overcome these challenges?
In the final week of April, we presented our work to the client at our final demo of the phase. Shortly after, my team annotated our designs, prepped for handoff, and wrapped up any final touches.
With all of our T’s crossed and I’s dotted, I took the time to reflect back on our experience and asked myself:
In the final week of April, we presented our work to the client at our final demo of the phase. Shortly after, my team annotated our designs, prepped for handoff, and wrapped up any final touches.
With all of our T’s crossed and I’s dotted, I took the time to reflect back on our experience and asked myself:
Challenges & Takeaways
Challenges & Takeaways
Challenges & Takeaways
Time for a Facelift
Time for a Facelift
Along with designing the Match Questionnaire feature, I was also tasked with iterating on the Sort & Filter side panel.
This side panel was first built and handed off in the previous phase. Our team analyzed the handoff design and decided to make a few changes based off new insights gathered from user testing.
Along with designing the Match Questionnaire feature, I was also tasked with iterating on the Sort & Filter side panel.
This side panel was first built and handed off in the previous phase. Our team analyzed the handoff design and decided to make a few changes based off new insights gathered from user testing.

Certain terms/copy listed were reevaluated by users and the UX Content team and were noted to be outdated in most opinions
Original categories and copy for this section needed to be revised by the UX Content team
These drop downs were found to be confusing to users during testing
Before

Terms in the “Sexual Orientation” section were updated according to user feedback to reflect modern terms
“Gender Identity” was changed to just “Identity” after consulting with the UX Content team
The “Support offered” section was changed to “Focus Areas” with updated category terms
The “Industries” dropdown was replaced with an input field and tags for better screen space conservation and utility
The Sort & Filter header was updated with brand coloring to help with visibility when viewed by users
The panel layout was changed to collapsible sections for a decluttered viewing experience
After


Certain terms/copy listed were reevaluated by users and the UX Content team and were noted to be outdated in most opinions
Original categories and copy for this section needed to be revised by the UX Content team
These drop downs were found to be confusing to users during testing
Before


Terms in the “Sexual Orientation” section were updated according to user feedback to reflect modern terms
The “Support offered” section was changed to “Focus Areas” with updated category terms
The “Industries” dropdown was replaced with an input field and tags for better screen space conservation and utility
The Sort & Filter header was updated with brand coloring to help with visibility when viewed by users
The panel layout was changed to collapsible sections for a decluttered viewing experience
After
New Feature: Sort & Filter
New Feature: Sort & Filter
Tag system answer format
From Concept to Questionnaire..
From Concept to Questionnaire..
I was assigned a new feature to design for Sprint 3 and 4: The Match Questionnaire
I was assigned a new feature to design for Sprint 3 and 4: The Match Questionnaire
Purpose:
Purpose:
The purpose of the Match Questionnaire is to provide match recommendations that are more alignment with a mentee's goals and interests.
The purpose of the Match Questionnaire is to provide match recommendations that are more in alignment with a mentee's goals and interests.
Priorities:
Priorities:
Easy navigation for a mentee to take/re-take the quiz as goals change
Easy navigation for a mentee to take/re-take the quiz as goals change
Iterating on matching results by providing “good” or “great” matches instead of matches based on percentages like previously designed
Iterating on matching results by providing “good” or “great” matches instead of matches based on percentages like previously designed
Adding a tag system that allows users to add more options they may not see listed
Adding a tag system that allows users to add more options they may not see listed
Side nav progress panel

Results page (Shown after completing)



New Feature: Match Questionnaire
New Feature: Match Questionnaire
Mentor Card
Mentor Card


Location information displayed to mentees found to be unnecessary for remote mentoring
Location information displayed to mentees found to be unnecessary for remote mentoring
% match tag created uncertainty on how to measure this metric/feasibility issues with dev team
% match tag created uncertainty on how to measure this metric/feasibility issues with dev team
Before
Before


After
Added a color coded tag system displaying focus areas for that mentor
Added a color coded tag system displaying focus areas for that mentor
Final copy displayed to mentee:
- Name
- Job title
Final copy displayed to mentee:
- Name
- Job title
Added availability tag
Added availability tag




Buttons for saving progress and continuing past this flow
Buttons for saving progress and continuing past this flow
First draft copy/text
First draft copy/text
Friendly tone, gender neutral themed illustration
Friendly tone, gender neutral themed illustration


Updatedassets
Updatedassets


Updated to more neutral illustrations
Updated to more neutral illustrations
Collaborated with Content Strategy to edit previous copy/text to be more concise
Email Verification Flow
Email Verification Flow
The Iteration Process
The Iteration Process
The Iteration Process
Breaking ground on design tasks
After getting oriented, each member on UXD Team 1 was assigned flows they would be designing for.
Our team faced unique challenges as a mix of new and veteran designers that would be iterating on designs handed off from the previous phase. We also put our focus on adapting our design tasks to align with our minimum viable product (MVP).
Tasks I worked on specifically are listed below:
- Mentor card re-design
- Sign Up Modal & Email verification flows
- Match Questionnaire flow
- Search and filter flow
Below are the handed off designs from Phase 1. These are the designs we would be iterating on:

Mentor Card
Mentor Card
Filter
Filter




Sign Up Modal
Sign Up Modal
Mentor Search
Mentor Search



Phase 1 Deliverables
Phase 1 Deliverables
With a strong foundation for our design process established, it was time to invest in a new design system.
With a strong foundation for our design process established, it was time to invest in a new design system.
We collaborated closely with the Dev team and decided to go with the Ant Design System after confirming it was compatible with React and Next.js
We collaborated closely with the Dev team and decided to go with the Ant Design System after confirming it was compatible with React and Next.js
Here's why we chose the Ant Design System:
The old design system wasn't feasible with the framework the dev team was using
Enabled more control over design of the product
Encouraged better collaboration between Dev & Design
Ensured near seamless crossover between the prototype and live product
Ability to customize and tailor to branding
Our Design System
Our Design System
With our HMW questions established, we re-analyzed our mentee user flows to confirm our design direction for features like onboarding, the match questionnaire and finding a mentor.
This set us up for a strong foundation to begin iterating on existing screens that were handed off from the last phase. We then moved into picking a new design system and assigning design tasks.
With our HMW questions established, we re-analyzed our mentee user flows to confirm our design direction for features like onboarding, the match questionnaire and finding a mentor.
This set us up for a strong foundation to begin iterating on existing screens that were handed off from the last phase. We then moved into picking a new design system and assigning design tasks.
Key
Action
Element
Element
Click the image above to inspect more closely
Re-working Artifacts
Re-working Artifacts
1
1
How might we establish a mutual connection between mentor and mentee to ensure a good fit?
How might we establish a mutual connection between mentor and mentee to ensure a good fit?
2
2
How might we ensure users feel safe and secure?
How might we ensure users feel safe and secure?
3
3
How might we give mentees and mentors the opportunity to develop long term mentorships?
How might we give mentees and mentors the opportunity to develop long term mentorships?
4
4
How might we provide guidance to users throughout the process and reduce any confusion in our user flows?
How might we provide guidance to users throughout the process and reduce any confusion in our user flows?
5
5
How might we get users excited to book their first session?
How might we get users excited to book their first session?
6
6
How might we provide clarity and transparency for users?
How might we provide clarity and transparency for users?
After analyzing the research from Phase 1...
We used the key insights to inform our design process and structure our How Might We questions.
Below are the How Might We questions that we chose to focus on in our design process for this phase:
After analyzing the research from Phase 1...
We used the key insights to inform our design process and structure our How Might We questions.
Below are the How Might We questions that we chose to focus on in our design process for this phase:
How Might We Questions
How Might We Questions
Background
Background
Research was conducted in Phase 1 to understand the needs and pain points from the mentee user perspective.
My team used the research insights from Phase 1 to inform our design process and form the How Might We questions for this phase so that we could hit the ground running.
Research was conducted in Phase 1 to understand the needs and pain points from the mentee user perspective.
My team used the research insights from Phase 1 to inform our design process and form the How Might We questions for this phase so that we could hit the ground running.
Phase 1 Research Overview
Phase 1 Research Overview
Multiple types of testing:
Unmoderated
Moderated
Multiple types of testing:
Unmoderated
Moderated
Consistent Themes
Consistent Themes
Security, privacy and trust
Inclusivity and belonging
User friendliness
Transparency and guidance
Security, privacy and trust
Inclusivity and belonging
User friendliness
Transparency and guidance


Moderated & Unmoderated Usability Testing
Key Findings & Themes
Moderated & Unmoderated Usability Testing
Key Findings & Themes
Safety, Trust and Transparency
Safety, Trust and Transparency
Users want to feel safe
Users want to feel like they have choices and agency
Users want consent/"a two-way street" when receiving matches
Users want to feel safe
Users want to feel like they have choices and agency
Users want consent/"a two-way street" when receiving matches
Inclusivity and Belonging
Inclusivity and Belonging
User want to feel like they are making informed decisions
Users care about learning the most they can about the program
User want to feel like they are making informed decisions
Users care about learning the most they can about the program
Increased Clarity and Guidance
Increased Clarity and Guidance
Users need more clarity and guidance through profile due to varied life experiences
Users desire an intuitive process
Users need more clarity and guidance through profile due to varied life experiences
Users desire an intuitive process
Want to Know More
Want to Know More
Support offered and bios - most interesting pieces of information
Expressed nervousness around the mentor having no input in booking the session
"Would they be a good fit?"
Value of the mentor to me - "What has the mentor helped/what have they accomplished?"
Support offered and bios - most interesting pieces of information
Expressed nervousness around the mentor having no input in booking the session
"Would they be a good fit?"
Value of the mentor to me - "What has the mentor helped/what have they accomplished?"
Filtering Categories
Filtering Categories
Industry experience categories
Confusion around expertise and industry
Difficulty finding toggle button at the button
Long term vs. short term
Mentorship minutes were unclear
Industry experience categories
Confusion around expertise and industry
Difficulty finding toggle button at the button
Long term vs. short term
Mentorship minutes were unclear
Scheduling
Scheduling
Users want an intuitive process
Booking Monday is the most commonly used
Users want an intuitive process
Booking Monday is the most commonly used
Research Insights
Research Insights
Build on Phase 1’s work and explore new features for mentee users:
Build on Phase 1’s work and explore new features for mentee users:
Develop core features designed in Phase 1
Address design debt and iterate on handed off Phase 1 designs and user flows
Ideate and design new features for mentee users
Develop core features designed in Phase 1
Address design debt and iterate on handed off Phase 1 designs and user flows
Ideate and design new features for mentee users
Design Process:
Design Process:
Our team worked via an agile work flow, utilizing 2 week sprints to design/iterate on new and existing features from the previous phase.
Each sprint began with sprint planning and concluded with demo and a round of feedback from the overall team as well as a retrospective.
Our team worked via an agile work flow, utilizing 2 week sprints to design/iterate on new and existing features from the previous phase.
Each sprint began with sprint planning and concluded with demo and a round of feedback from the overall team as well as a retrospective.
Deliverables:
Deliverables:
Finalized Onboarding Flow
Finalized Onboarding Flow
Finished Sort/Filter Panel
Finished Sort/Filter Panel
Finished Match Questionnaire
Finished Match Questionnaire
High Fidelity Prototype
High Fidelity Prototype
Project Goals
Project Goals


My Role
UX/UI Designer
My Role
UX/UI Designer
Duration
1/30/2023 - 4/6/2023
~ 3 months
Duration
1/30/2023 - 4/6/2023
~ 3 months
Tools Used




Tools Used




Process
Agile style work environment
2 week sprints
8-10 week long phases
Process
Agile style work environment
2 week sprints
8-10 week long phases
The Tech Fleet team for this project was made up of six teams consisting of 42 team members in total.
Here’s a breakdown of our team structure:
The Tech Fleet team for this project was made up of six teams consisting of 42 team members in total.
Here’s a breakdown of our team structure:
Team & Background
Team & Background




The Tech Fleet team was made up of six teams consisting of 42 team members in total.
Here’s a breakdown of our team structure:
My Role
UX/UI Designer
Duration
1/30/2023 - 4/6/2023
~ 3 months
Tools Used








Process
Agile style work environment
2 week sprints
8-10 week long phases
Team & Background
Team & Background
Below I present one of our deliverables for Phase 2: The interactive Figma prototype and vercel tester of the Sean's Legacy Mentorship platform and its progress from this phase.
Flows that are included in this version of the prototype and vercel site include:
- Onboarding Flow: all "Sign Up" and "Login" buttons are functional
- The "About Us" page is accessible
Below I present one of our deliverables for Phase 2: The interactive Figma prototype and vercel tester of the Sean's Legacy Mentorship platform and its progress from this phase.
Flows that are included in this version of the prototype and vercel site include:
- Onboarding Flow: all "Sign Up" and "Login" buttons are functional
- The "About Us" page is accessible
Prototype
Prototype
Important Update about the Project:
Important Update about the Project:
Important Update about the Project:
This project has recently updated the name of the platform to Thrive Out Loud. Any updated testers and assets in this case study may contain updated branding.
This project has recently updated the name of the platform to Thrive Out Loud. Any updated testers and assets in this case study may contain updated branding.
This project has recently updated the name of the platform to Thrive Out Loud. Any updated testers and assets in this case study may contain updated branding.
About this project:
About this project:
About this project:
Techfleet and Sean’s Legacy have partnered together with UX researchers, designers and product professionals on a project to create:
Techfleet and Sean’s Legacy have partnered together with UX researchers, designers and product professionals on a project to create:
Techfleet and Sean’s Legacy have partnered together with UX researchers, designers and product professionals on a project to create:
A professional mentorship program and platform that will provide LGBTQIA+ young adults a safe space to seek career guidance and form long-lasting professional relationships.
A professional mentorship program and platform that will provide LGBTQIA+ young adults a safe space to seek career guidance and form long-lasting professional relationships.
A professional mentorship program and platform that will provide LGBTQIA+ young adults a safe space to seek career guidance and form long-lasting professional relationships.
The Structure of this Project:
The Structure of this Project:
The Structure of this Project:
This project was set up to run in 2 week sprints covering an 8 week time period for a total phase. This case study covers Phase 2 of this project.
This project was set up to run in 2 week sprints covering an 8 week time period for a total phase. This case study covers Phase 2 of this project.
This project was set up to run in 2 week sprints covering an 8 week time period for a total phase. This case study covers Phase 2 of this project.
Organization overview
Organization overview
Organization overview



TechFleet
TechFleet
TechFleet
An organization aimed at matching opportunities for UXR, UXD, and Product professionals with projects for non-profits
An organization aimed at matching opportunities for UXR, UXD, and Product professionals with projects for non-profits
An organization aimed at matching opportunities for UXR, UXD, and Product professionals with projects for non-profits


Sean’s Legacy
Sean’s Legacy
Sean’s Legacy
A 501c3 non-profit focused on providing resources, opportunities, and support to the LGBTQIA+ community
A 501c3 non-profit focused on providing resources, opportunities, and support to the LGBTQIA+ community
A 501c3 non-profit focused on providing resources, opportunities, and support to the LGBTQIA+ community
Overview
Overview
Overview
Sean’s Legacy
Phase 2
Sean’s Legacy
Phase 2
Sean’s Legacy
Phase 2
Professional Mentorship Program
Professional Mentorship Program
Professional Mentorship Program
Start: 01.30.2023
Start: 01.30.2023
Start: 01.30.2023
End: 04.06.2023
End: 04.06.2023
End: 04.06.2023
A professional mentorship program for LBTQIA+ young adults.
A professional mentorship program for LBTQIA+ young adults.
A professional mentorship program for LBTQIA+ young adults.
A case study by:
Mika Bernal
A case study by:
Mika Bernal
A case study by:
Mika Bernal




<Work Collection - Sean's Legacy Mentorship Platform
<Work Collection - Sean's Legacy Mentorship Platform
<Work Collection - Sean's Legacy Mentorship Platform
Project Goals
Project Goals
Research Insights
Research Insights
Phase 1 Deliverables
Phase 1 Deliverables
The Iteration Process
The Iteration Process
Index
Below is the live Figma prototype and vercel tester of the Sean's Legacy Mentorship platform and its progress from this phase.
Flows that are included in this version of the prototype and vercel site include:
- Onboarding: all "Sign Up" and "Login" buttons are functional
- The "About Us" page is accessible
Prototype
Prototype
What were some of the main challenges we faced in this project?
Changing scope - The onboarding flow was changed three different times during the phase due to client requests. This unfortunately pushed our timeline back.
We did what designers do best in Agile--we adapted to each change requested and pivoted each time.
Unfortunately this did put our timeline off but we re-aligned our goals to deliver high fidelity designs for the onboarding flow and were successful!
Mid-phase we had miscommunications arise between other teams that cost us time in the long run:
- The UX Content team had to repeatedly review copy changes after pivots happened. The copy they already reviewed would get changed again and again. This caused inefficient time loss and frustration for both teams.
- The Development team had extra hands to work on different screens but due to a complex standardized format for submitting designs, the UXD team was too overwhelmed to be able to meet those standards for submitting tickets and the whole system had to be revised mid-phase.
The Importance of Effective Collaboration
Moral of the story: Effective collaboration takes intentional effort in all areas of a team and although its hard to get perfect, mistakes like these helped me realize just how effective timely and efficient communication between teams is.
TLDR/Moral of the story




Usability Testing - The UXR team focused on testing for the mentor’s perspective only for this phase, so we did not have the ability to test for the mentee’s POV. Due to this, we had to rely on user testing done in Phase 1 only.
We structured our designs off of the research insights gathered in Phase 1 and used those to inform our design process.
After finishing this phase our team put together a document that had recommendations for what to test in the next phase
In the final week of April, we presented our work to the client at our final demo of the phase. Shortly after, my team annotated our designs, prepped for handoff, and wrapped up any final touches.
With all of our T’s crossed and I’s dotted, I took the time to reflect back on our experience and asked myself:
Challenges & Takeaways
Challenges & Takeaways


As always, thank you for scrolling and if you’d like to see the current working prototype developed in collaboration with us and the Development team please feel free to jump to the prototype section above or click the button below to see the current tester!
We’ve Arrived at the End of the Case Study
Overall, my team enjoyed experiencing success in wrapping up our final designs and presenting them and the final prototype to our client.
We handed off our annotations and gathered to discuss what happens next...


Conclusion
Conclusion
Next Steps
This project will move into Phase 3 after review on how this phase went.
That being said my next steps look like:
Preparing for leadership in a Co-Lead role for the UXD Team
Usability testing with focus on features we designed in this phase
Onboarding and assisting new designers that join the team
(Update: Phase 3 was completed January 2024, UXD Lead Case Study coming soon!)



















