Sharing Volunteer Experiences Study
One aspect of Unself’s mission is to connect volunteers with nonprofits – both in our app and on-the-ground in the community.
The community formed between volunteers, nonprofit admins, and program participants has been proven to be one of the single greatest drivers to give back.
After our hour tracker platform foundation was complete, I began to research how we could facilitate those connections inside our app.
Through our analytics and user research, Unself identified that our core user segment is Self-Motivated Volunteers: millennials who have intrinsic motivation to further a personal cause. (Check out the persona here)
While this group tracks hours frequently, these users are not the vast majority of the volunteering community nor the population at large. Our next challenge is to expand our user base and product offering for the next segment of volunteers: those who are externally and socially motivated.
One major risk we identified is potentially alienating our core – Self-Motivated volunteers aren’t inclined to “humble-brag” about their volunteerism. I interviewed a handful of these users to figure out the pitfalls we could avoid while adding more social features to our hour tracker.
As we began to start working on new features for sharing your tracked hours with other volunteers, we quickly realized there were a mix of strong ideas around new navigation, flows and copy.
So, unsure of the exact next design step, we opted to test our two most promising concepts with an even mix of Self-Motivated (core user base) and Community-Motivated (new user target) volunteers.
Beyond excited to run our first real research study, I put together a Notion repo of all our test documentation and began recruiting users who fit into our personas from our opt-in test pool via Calendly.
Once we had the goal and structure of the test set, the design team moved into production. We began with text-based wireframes to indicate content modules the flows we would need to design. This also became the foundation of my test script.
Our team uses Figma, which allowed us to all collaborate on the same prototypes via browser. This made dividing up high fidelity visual design and linking screens a snap!
Once we completed Proto A and Proto B, I put together documentation for our team to visually list the new enhancements we added to both prototypes (test controls) versus the variable navigations pathways we were testing.
After our week-long study with nine users was complete, I began to sift through commonalities in the raw data, capturing different lenses in a Notion board.
The most interesting finding out of this data set was not whether a majority of users preferred prototype A to B. Rather, it was that Unself was not meeting their core driver to use the app (regardless of persona).
While our prototypes successfully conveyed to an even number of users that we were on the right track with a social hour tracker, the number one reason people were using our app was to find vetted volunteer opportunities.
By this time we had the ability to host volunteer events on our app (see my Volunteer Events project). But this data told us we needed to invest in a scaleable events system in order to also scale our users.
In order to dig into how and why people move through Unself, I re-listened to screencap video and scribed soundbites (check out one test user’s raw notes).
As trends emerged, I began to capture them as digital insight cards. The color coding related to whether I felt the insight was a strength, weakness, or a totally unexpected new learning for us.
The cards were grouped so that from any edge entry point, you could follow related chains of insights, which was very helpful when leading a team exercise to ensure everyone empathized with our users.
Our insights ranged from actionable copy changes to larger features sets, like a Community homepage where users could see shared tracked experiences and promoted volunteering events.
The design team took this essentially new backlog and compared it with our upcoming stories, writing out a UX flow script that contained the improvements we decided to make throughout the app.
Right after our study we got a meeting to discuss a partnership with the National Parks Foundation – the most exciting opportunity I’ve probably ever had!
I had a ton of fun being able to incorporate the necessary design changes from our insights so soon – all of which can be seen in our National Parks Foundation pitch prototype.
Through this process, the Community landing page began to crystalize as a true jumping off point to other volunteers’ profiles (without humble bragging), organizations volunteers help, as well as opportunities vetted by Unself.
The volunteer profile and tracking experiences also became enriched as we understood more about how people think about their impact on Unself.
We learned that volunteers think about their tracked experiences by time, by nonprofit organization, and by cause. This led to us redesigning the Track and Profile to have split views according to what volunteers wanted to see personally (in Track) vs. what they wanted others to see (on their Profile).
We gained incredible insights into peoples’ thought processes while they are tracking hours too. One of the most valuable insights was that volunteers consider writing their descriptions as an act of journaling and want to track how they feel at the same time, so we added emotion tracking specific to volunteering. The controls for sharing experiences needed to be on the same page so that volunteers could confirm/revise what they wrote if need be.
This study taught us more than we could possibly imagine about our core users and our next target group. We didn’t walk away with a clear answer which prototype was “better” than another. Instead, we walked away with a new iteration of our app that answers our users’ most important drivers – which is all I could hope for, and then some!
(Want to know more about how our tracker got to this point? Check out the full story of our hour tracker.)