Stanford University

Enhancing the university's gift giving experience to solve a problem with conversion rates.

Stanford University

Enhancing the university's gift giving experience to solve a problem with conversion rates.

01. Overview

Giving to Stanford

background
Stanford University has one of the largest financial endowments in the world and brings in millions in gifts from alumni every year. However, this is not enough as these funds are meant to be used in perpetuity and a lot of these funds are restricted or earmarked for specific purposes. As a result, Stanford still needs to fundraise and collect gifts from as many sources as possible.
Problem
Stanford was having issues converting visitors of their Giving landing page and also noticed a 40% abandonment rate in their payment form workflow.
objectives
Redesign the Giving landing page to help the average person empathize with the university's cause.
Optimize the user experience of the online payment form.
results
50% decrease in the time to complete the payment form.
tools
Adobe XD, Excel
project Type
Redesign
role
UX/UI Designer, Web Designer & Data Analyst
duration
3 Weeks

02. Research & Discovery

Heuristic evaluation

We immediately started with performing a heuristic analysis of both the existing Giving landing page and payment form and identified some heuristic issues that may have been preventing visitors from easily being able to accomplish their giving goals. The scope of this project was primarily centered around these two pages.
Original Giving landing page and payment form designs that me and my team were tasked with redesigning.

Connecting with users

"Don't they have millions? Why do they need my little money?"
"What else could they need?"
"I'm still paying my own bills for college."
We had daily calls with our contacts at the university and weekly in-person meetings to review findings and designs. We began by meeting with our client at the university to understand all of the goals that they wanted to achieve throughout this project and to confirm the feasibility of what we could address within the project timeline. It was requested that we focus on “everyday normal people” as our target users. The targeted user was 18-50 years of age, had an average income, and worked a normal 9a-5p job or was a student.
We immediately started by walking around campus and questioned about 25 people total (students, professors and staff). We then questioned family and friends on whether they'd be willing to donate to the university. Immediate feelings of confusion and disbelief stood out.
How can we compel everyday people to give their hard-earned dollars to one of the wealthiest universities in the world?

Surveys

People had donated to causes before. Why not this one?
We sent out a 10-question survey asking these people about their previous giving experiences. We learned that ~50% of respondents were fairly involved with groups or extracurricular activities and would be willing to give back to their school, while almost all respondents were more willing to give to specific clubs or teams in which they were involved.
feeling informed
compassion
strong interest
connection
Feelings that lead to giving.

User interviews

As expected, most interviewees had a mental depiction of Stanford that was privileged or spoiled and prioritized its own needs over the cause. The promise of helping students gain a good education was not enough here.
Our client was able to connect us with 5 existing donors. Since these donors had already given to the university, we wanted to hear about their experience with filling out the online payment form. Common issues that were mentioned:
key takeaways regarding the payment form
The form is too long and tedious.
The unexpected amount of information required makes users feel uncomfortable, like they are committing to more.
It's a confusing process because there is no idea of how long it is.
Lack of a quick pay option (PayPal) seemed slightly inconvenient.

Journey mapping

It was helpful to map out the user journey to confirm that our efforts should be primarily focused on improving the giving form. We were able to see that the giving form offered the greatest risk for user drop-off in the giving journey.
Journey map of a user traversing through the 4 stages of giving.

03. Design

Wireframes

After analyzing all of our research, we felt the best plan was to focus on including those elements that touched the emotions of being well informed about why this so seemingly wealthy university could still tremendously benefit from the help of our target user, as well as imagery on who they'd be helping. We also wanted to showcase the breadth and width of the site to provide a multitude of ways that potential donors could become involved with the university and all of its causes. We began with drawing up some rough drafts for what the landing page could look like. The giving landing page is the first place that most donors arrive, so this is where we wanted to draw out those feelings that we discovered from our surveys and interviews. To do this we focused on:
key takeaways
Showcasing student stories about campaigns that are affected by funding and gifts to the university at the top to grasp readers' attention and emotions at the start.
Increasing opportunities to give throughout the page and improve call-to-action (CTA) placement.
Providing transparency by sprinkling information on how the university allocates its gifts throughout the page.
Adding more images of students so that donors can see who they are helping.

Usability testing

In order to get some feedback from our university contact, I created some mockups of the new designs in Adobe XD to share in our next meeting.
We cleaned up some of the heuristic issues on the giving form as well and pushed all of the extraneous data that the university wanted to collect towards the end of the workflow. We also suggested that the university add the convenience of a quick pay option, as it was mentioned several times in testing sessions.

100%

Of testers preferred our design over the original design.
key takeaways
Users didn’t really understand any of the icons except for Record and struggled to get started when prompted with a task.
Most users expected to be able to “set it and forget it” while Spot captures all planned waypoints on the floor plan.
Most users were initially confused about how to use the two joysticks together but quickly figured it out.
Many people had a false sense of security in the presence of Spot, approaching it like a friendly pet rather than a potentially dangerous piece of machinery.
It was asked multiple times if there was a way to schedule multiple walks at once. Repeating the actions to set up a single walk seemed tedious to some.
Users need to be lead more into the individual actions that they wanted to achieve.
Users need additional context when operating the joystick controls to help maximize safety.
Users need to be able to quickly shut down Spot at any given time that it’s in motion.

04. Final designs

05. Impact

Results

We presented our final designs for the client and they loved them. They were super excited about the changes and eager to implement them on their website.
Regarding the giving form, we were able to cut down the time to complete the form by 50%. Testers cited a simpler, "less daunting" process, cleaner look, and the quick payment option as reasons of preference towards our designs over the current design.

50%

Decrease in the time to complete the payment form.

Lessons I learned

make better use of wireframes
Looking back, I think that I could've made better use of low-fi wireframes to maximize feedback in the few client meetings that we had. With this being my first official client, I think I was a bit eager to create some cool mockups to show but moving forward I want to make sure that I always have mastered the element of "functionality" before investing time on polished visuals.
be able to adjust
Being able to adjust your plans is important. I think we did a pretty decent job of using our time to come up with the best design for our client, but it was a challenge coordinating times to speak with some of the users provided by the client. With the 3-week timeframe on the project, we sort of had to work around the schedules of these users, forcing us to adjust our plans at times.

Next steps

If given the chance, I'd track the performance of the payment form to confirm if our solution remedied the abandonment rate issue. Regarding the landing page, I'd be really interested in tracking the conversion rates and mapping the many different navigation routes that users take to arrive at the payment form, to uncover more insights into what could further interest potential visitors of the page.