Fall 2022- October 18, 2022

Responsive & Local w/ LGBTQ+ center

Designing with people in LGBTQ+ center at Purdue for a responsive app that locates gender neutral bathrooms on campus

Scope Framing

The project’s description was to create a web-based solution for a local community: we decided to work with Purdue LGBTQ+ center. 

Areas that we could focus on were pulled from team members’ interviews with people who worked there about what problems they faced and what improvements could be made. Based on the interview, there were many opportunities for us to design web solutions.  To organize the potential areas, we collaboratively worked on an affinity diagram.

Venn-diagram of different potential design areas with the LGBTQ+ center

We eventually narrowed it down to one solution: creating a comprehensive web-based map of gender neutral bathrooms as that led to a clear, straightforward solution with a narrow and important user group. 

Current Solution for Locating Gender-Neutral Bathrooms

The current solution at Purdue for locating gender neutral bathrooms is: Refuge Restrooms which is a fully realized app with most of the functionality we were looking for: map with pinned locations on it, comments on each bathroom from the users, general locations of all the gender neutral bathrooms in a list format. 

However, there is much room for improvement and isn’t too helpful for actually using it to find bathrooms. 

Screenshots of Refuge Restrooms and a picture of a Purdue sign of where a gender-neutral bathroom is

There were little to no users and very few of the restrooms actually pinned on the map. As a result:

  • only 10 out of the 200+ gender neutral bathrooms could be found on the map section
  • All GN bathrooms were in a long list that wasn’t sorted by distance
  • The bathrooms had very all or nothing reviews because it seemed like only a few users were actually rating them

Moreover, while the list format did have symbols/tags for each restroom indicating accessibility, there were no filters for these tags and missing tags for menstrual products that other universities’ solutions included. 

Designing with People Who Prefer GN Bathrooms

Preparing a Codesign Workshop

Although we were researching the importance of GN bathrooms and comparing the current solutions on our own, none of our team was part of the community we wanted to design with: people who prefer using GN bathrooms over gendered ones. For this project to succeed, we needed to talk with and get ideas from that community via a codesign workshop. 

We wanted any design decisions to be based on the community members’ stories and design suggestions.

To encourage participants in telling their stories and have good conversations, we came up with more open-ended questions along with a task of them sketching their own design.  

While we wanted and encouraged all designs, we recognized that some participants may not feel comfortable sketching ideas, so we also allowed for them to just write down features they would want on the post-it notes.

Screenshot of codesign protocol

Codesign Workshop

Due to time limitations of the project and our own team’s schedules(we all wanted to be there in person to conduct the workshop and take notes), it was conducted on one day for 90 minutes. 

To make people joining us feel more comfortable with the codesign experience, especially people who may be unfamiliar with UXD or design in general, we let people come in and go anytime. In total, we had 9 community members show up, but only a few people were there for the whole workshop, others leaving earlier or coming in late.

Results 

All post-it notes we got from the codesign workshop

Problems related to difficulty locating GN bathrooms at Purdue

The first part of the codesign workshop in identifying problems from a community lens was very enlightening in showing the importance of developing a system for locating gender neutral bathrooms. 

Some notable quotes that were:

  • “I’m in the biochemistry building a lot [and it says] ‘to find the gender neutral bathrooms go down the double doors [...]’ I’m just gonna misgender myself because I don’t have the time” 
  • “I kinda just use any bathroom that has a toilet in it”

Participants from our codesign workshop gave us more reasons it was difficult for them to find gender neutral bathrooms, such as:

  • “I don’t want to pull up a map every time I have to pee”
  • Restrooms being located on opposite sides of buildings
  • Subpar quality of some gender neutral bathrooms

Physical Design Opportunities 

Photo of post-it notes on design opportunities around gender neutral bathrooms

The workshop was especially insightful as our participants gave us many design suggestions and areas of improvement we could design around in GN bathrooms, both on post-its and during the conversation. 

Suggestions that we included when developing our website were:

  • Indicating accessible stalls & menstrual product accessibility
  • Prioritize local bathrooms, map by building
  • Details of building the GN bathrooms are located in
  • Showing floor plans 

Developing a solution

Taking the areas of improvement from both our codesign workshop and competitive analysis we found in Purdue and other universities, we created mid-fidelity prototypes on Figma to come up with possible UIs that would be the best solution. This was done quickly in order to get group critique by other teams during this project. 

We started out with a web prototype that was easier to ideate for before also creating a phone/mobile prototype as that’s what students would most likely be using to find restrooms. We also kept a checklist of the features we wanted to include that we got from the codesign in order to make sure it could really cater to our user group.

Screenshot of our Figma file for our initial mid-fidelity prototypes
Annotated screenshot of our initial web prototype
Annotated Screenshot of our initial mobile prototype

Improving our solution

After getting feedback on our prototypes by other teams of student UX Designers and members of our user group, we came back as a team to make changes. 

Screenshot of iteration process on Figma

One major insight we got from user testing was that some of the features in the sidebar were unnecessary and cluttered, such as the star rating in the user reviews section, so we removed them. 

We also added directions to the bathroom detail sections to make location even clearer.

Web Iteration

Annotated screenshot of iterated web prototype

On the web version, we moved the filters to the top of the screen so the map and restroom icons would be the main focus. 

Mobile Iteration

Annotated screenshot of iterated mobile prototype

We also added interactivity to the mobile screens by making the bar with additional information swipeable. We did this because the main focus should be on the restroom icons and wayfinding rather than additional (helpful, but not necessary) building information.

After our redesigns, we handed them over to another team member for coding the final website. 

Final Presentation

reflection

Challenges and Next Steps

Codesign Workshop

  • Conducting it all on one day limited number of participants and therefore the amount of insights we got 
  • As one of our professors put it,” is it really worth it to conduct a codesign to just find out that a map would be helpful?” We needed to be more intentional with codesign goals to get valuable information and insights, things that we couldn’t figure out already on our own. 

Responsive & Local

  • We tunnel visioned on creating an entirely new web/mobile experience for locating bathrooms, when we already noted how there was a solution in place, albeit limited. Our design process could have been a lot more streamlined/time crunched if our solution was focusing on building outreach and a user base for that app so that it is more functional
  • Besides the codesign workshop from the previous project and some user testing on our Figma mid-fidelity designs, our user group wasn’t as included in the end as much as I would have liked
  • Some of the designs or design suggestions,  from the community, even if they were ideal, were difficult to include in the first place due to our coding limitations such as location tracking. At this point in the semester, we were still beginners at HTML/CSS/Javascript!

If we had more time...