PROBLEM
Prospective volunteers interested in joining Hack for LA find it difficult to get the information they need to confidently get involved. This is unfortunate because it means the organization loses out on the skills and resources that people would like to share with HFLA's weekly hack nights.
GOAL
Provide website visitors with the information they need regarding hack nights and current available projects so they can get involved at their best capacity.
Prospective volunteers interested in joining Hack for LA find it difficult to get the information they need to confidently get involved. This is unfortunate because it means the organization loses out on the skills and resources that people would like to share with HFLA's weekly hack nights.
GOAL
Provide website visitors with the information they need regarding hack nights and current available projects so they can get involved at their best capacity.
|
ROLE: UX/UI Designer
PROJECT SCALE: July 2019 – ongoing PRIMARY STAKEHOLDER: Hack for LA community and Meetup organizers |
TOOLS USED
|
CONTEXT
Though Hack for LA had a loyal group of volunteers and new people dropping in weekly, there was still a disconnect between the hack nights and potential volunteers. Based off the organization name, many were not aware that the hack nights wasn't about "hacking," per se. The meetups welcomed those who are new to tech, and that they also had room for designers.
One of the main difficulties was how do we communicate all the information that website visitors may need or want without burdening the volunteers with the extra responsibility of maintaining the project information on the website?
One of the main difficulties was how do we communicate all the information that website visitors may need or want without burdening the volunteers with the extra responsibility of maintaining the project information on the website?
RESEARCH & INSIGHTS
To better understand the expectations of website visitors, Hack for LA organizers collected results for a feedback survey from 46 volunteers.
First, we wanted to know "What information did you come to the site to find?"
First, we wanted to know "What information did you come to the site to find?"
We pulled out quotes so that we could keep track of specific comments and feedback that volunteers shared via the survey.
Out of 46 responses:
We were able to categorize the feedback into four different themes:
- 8 mentioned wanting more information on projects and hack nights.
- 12 people gave feedback and suggestions on the website UI. (This made sense as the volunteers we polled are already involved or looking to get involved in the tech industry.)
We were able to categorize the feedback into four different themes:
- Transparency - one volunteer was curious about Hack for LA's relationship with city government
- User Interface - comments ranged from color theme to concrete feedback on our CTA
- Project - volunteers wanted more information on current projects at Hack Night; and lastly,
- Expertise Level - information regarding the skills required for each of the projects.
DEFINING THE PROBLEM
From the common themes of the survey results, we came up with a couple key questions we wanted to address in the redesign.
We took our goal one step further and set our sights on "In one year's time, people are able to join projects in a few clicks."
WIREFRAMES
In our first iteration, we considered filtering projects by location and skills needed, but quickly realized that this would not be sustainable as event organizers can't expect volunteer leads to provide weekly updates.
We also considered providing a form for volunteers to submit and a CTA for each project. Though the projects use a card design, they are misleadingly static. |
|
