Mockup SQSHBook Notion.png

Overview

Type

Responsive cross-platform website hosting a community-facing SaaS database of over 1,200 LGBTQIA+-affirming local resources

Scope

Entire design strategy and UX process including research, UI, prototyping, usability testing, and final deliverables

Timeline

June 2023 - May 2025

Role

Sole UX Designer

Team

Product Owner (1) Software Developers (2) SQSHBook Data Team (6) Internal stakeholders (15+)

Tools

Figma Contentful GitHub Loom

Challenge: level up an MVP

After its initial start as a spreadsheet that compiled local queer-affirming resources, an MVP version of SQSHBook was built as a cross-platform responsive web app.

I was brought on as the sole UX Designer for Version 2 of SQSHBook. My objective was to improve usability but “Improve SQSHBook” was way too broad.

Because there was no previous designer or any UX processes in place, I had to lead the way from end-to-end, starting with research, strategy, and feature prioritization.

Step 1: How I discovered & set priorities for V2

My approach: research with internal stakeholders

To identify the existing pain points, I conducted research with SQSH helpline volunteers who used SQSHBook to find resources for callers.

I gathered both qualitative and quantitative data from over 15 stakeholders.

  1. First, I facilitated two virtual focus groups to gather open-ended feedback about how they used SQSHBook and their biggest challenges with it.
  2. Then I asked users to answer specific survey questions and use rating scales to gather quantitative data.

<aside>

💡 Why I chose this approach:

Conducting research with internal stakeholders allowed me to get acquainted with the product and gain insights quickly.

It was easy (and free) to access helpline volunteers, who were already connected to SQSH.

</aside>

Insights

Using this research, I identified two problem statements.

Key Findings