Find My Rep is a complementary website to accompany the Find My Rep app that I designed in my first project. The site helps users find and contact their local and federal representatives, and is broader in focus than the dedicated app. It empowers people to feel politically engaged, and enables them to make their voices heard.
This was a individual project that challenged me to plan and direct each step of the design process for a fictional responsive website. I conducted research and empathized with users, defined the problems to be solved, ideated solutions, created wireframes and mockups, built low- and high-fidelity prototypes, and tested my designs via usability studies.
Since this was a solo project for my UX certification class, I relied on friends and family for research and testing purposes, which is not a true representative sample of users. It does, however, give a good idea of the process that I would use if I were designing for a real product.
October – December 2023
I interviewed a small group of friends and family members to gain insights into the needs of my potential users. These are the common pain points that emerged during interviews.
I grouped together common themes and created personas from my research. Here is one example.
Eric is a musician who needs a quick way to contact his representatives because he doesn't have much spare time.
Goal: Find a website that will help him contact his congressperson.
I conducted a competitive audit to investigate products available on the market, and examined their strengths and weaknesses.
Two direct competitors are the websites QuestionPolitics.org and Congress.gov. Indirect competitors are individual city websites.
To set ourselves apart from competitors and solve our users' pain points, we can present a list of personalized reps, including local officials, with multiple methods of contact information, that is neatly organized and pleasant to look at, with registration features that offer bonus content without restricting free information.
Eric is a musician who needs a quick way to contact his representatives because he doesn't have much spare time.
Our app will let users quickly find their representatives’ names and contact information, which will affect busy individuals by giving them the ability to make their voices heard with minimal time and effort.
Reliable, up-to-date database
Election reminders
Multiple methods of contact information
Tailored information about local, state, and federal representatives
Location services or zip code entry for instant info retrieval
Statistics on contact and response rates
After empathizing with my users, and defining the problems to solve, I sketched out what the design solution would look like.
Since a website can have a broader scope than an app, I built a sitemap to organize information that would need to be included. My goal was to create a site where all information was organized logically, so the user could easily and quickly find what they needed.
Focusing on creating a simple and easy experience, I sketched rough wireframes on paper.
After several iterations, I built digital wireframes in Figma, adding a large search feature.
I connected the wireframe screens to create low-fidelity prototypes so I could make sure the primary user flow was clear.
Interact with the desktop version of the prototype here, or watch the video below.
Interact with the mobile version of the prototype here, or watch the video below.
I conducted moderated usability studies with 5 participants. I created a study plan, and carefully drafted my prompts and follow-up questions to avoid influencing my participants.
Open the website and see if you can find your representatives. Do your best to talk me through your thought process.
Select a representative and contact them.
Make your way back to the main screen.
How do you feel about the steps you took to find and contact your rep? What was easy and what was challenging?
Did you find anything confusing?
How do you feel about the website overall? What did you like and dislike about it?
I recorded each session, and re-watched them as needed, jotting down each statement and idea from every participant. I then grouped these into common themes in an affinity map.
I translated each theme from my affinity map into an actionable insight.
It was observed that 3 out of 5 participants felt that the they wouldn't use the scripts feature. This means that most users don't need this feature to be included on every rep's contact page.
It was observed that 4 out of 5 participants found the search and results pages confusing. This means that the two pages need to be differentiated better.
It was observed that 3 out of 5 participants did not realize the contact options were links. This means that the links need to be clearly indicated.
It was observed that 3 out of 5 participants weren't sure which contact method would be best. This means that most participants would like an indicator of best contact method.
Based on insights from the usability study, I de-emphasized the scripts feature of the site, and instead added stat charts for each representative. Broad-use scripts were too generic to be of use, whereas stats are useful information on what contact methods work best, and encourage people to contribute their own data.
I created a "sticker sheet" in Figma detailing my colors, fonts, buttons, and icons, so I could quickly and easily reuse assets, while ensuring all elements stayed consistent. I used the same fonts and colors as I used in the Find My Rep app, so that the two would complement each other.
I made sure my colors were high-contract and met WCAG AA compliance.
Icons include text, which is important for screen readers.
I included multiple options for communication, which is useful to people with speech limitations, and also helpful for people who simply do not like to talk on the phone.
I used headings with different sizes, for clear visual hierarchy, and used only two typefaces, both sans-serif, for each of reading.
I created high-fidelity mockups of the site, where the screens would appear as close as possible to the finished product. Based on user feedback, I clarified the search process, and ended with a CTA button to log contact data, rather than a call script.
I connected the mockup screens to create a high-fidelity prototype.
Interact with the desktop version of the prototype here, or watch the video below. The user's prompt was to find and contact representative Casey Weinstein.
Interact with the mobile prototype here, or watch the video below.
“This is super useful” – study participant A
“It's simple and clean” – study participant C
“It’s really simple and straightforward” – study participant D
People are frustrated by a lack of easily-available information. If they cannot easily get the information they need to contact their reps, it either becomes a chore, or they skip it entirely.
Focusing on the needs of the users will always result in a better design. Also, placing a main focus on accessibility ultimately creates a product that is better for everyone.
I did not have time to do an additional round of user testing once I had built the high-fidelity prototypes. Also, since I was relying on friends and family to be my testers, I felt bad asking them to test both the desktop and mobile versions. In a real-world situation, I'd want to do additional testing, and test on both desktop and mobile. This would surely identify weak areas that could be further improved.