Attended: Bo, Jaime, Dana, Hannah, Lillian, Adityo

Discussion with UXD1 on the collaboration areas — Content will leave stickies on UXD1’s figjam, but we can brainstorm separately on our own figma files.

• Onboarding flow - We agree with UXD1 on separating the profile from the matching flow, so that mentees can see mentors even without quiz but don’t need to get matches, or can update the matches. Also on the same page about having users fill in only basic information during sign-up so that it’s not so tedious.
  • Making things more personalized to help users navigate the process, e.g. tooltips, coaching, prompts (e.g. via email) if users sign up but don’t fill out a profile or abandon the process halfway.
• Mentor matching quiz / questionnaire
• Figuring out what “whisper technology” is — and more broadly, how to make content clearer and not sus
• Landing page — users were confused that it’s a remote platform + free to use [E.g. where can we highlight this info, and streamline the signups, and should we show them some mentor profiles before they sign-up?]
  • Question: Has there been any testing done with mentors if they would be comfortable showing their profiles publicly? Maybe we could have a toggle to turn public view on/off on mentor profiles.
• Users were confused about the main purpose of the mentorship programme, which is separate from the mission of SL.
• [for sprint 2 or 3] filter options and copy and how to make it more intuitive [lets think more about the taxonomy / levels, how to prioritise the filters] [—> not all the dropdown were clickable in the prototype] [now we know it’s going to be a handful of careers]
• Mentor cards — can give feedback from a content perspective. Becca said that location is not a priority, so UXD is thinking if should remove the location. [Would the pills be pre-defined, or can people type their own?]

We also went over our goals for Mon and Tues

• Questions / clarifications for the meeting with the SL content team
  • Clarify content audit with the SL team, if it’s needed, and if so what the goals are
  • Style guide / voice and tone — we’re focusing on content strategy from the UX angle now, but would it be helpful to add in elements from a marketing angle, e.g. SEO [tbh the team doesn’t know that much about this beyond that it’s about keywords]
• Content flow —> commenting on UXD figjam
• Style guide and voice/tone — Jaime will work on populating the content style guide template and Dana will add on later. —> We’ll try to present this as an MVP during the SL content meeting to try to get some initial feedback on our direction, product voice, and tone examples.