00 Context
Problem Statement
Donors of St. Nersess Armenian Seminary need an easier way to donate. They are limited to single PayPal donations and must mail in or call in for all other donation types. 

Additionally, the accountant needs a more efficient way to collect user information associated with PayPal payments, as the current system entails a laborious manual process of data entry. 
Role: UX Researcher, Information Architect, Developer
Tools Used: WordPress, WPForms, Sketching 
Constraints: Must integrate with PayPal and WordPress 
01 Content Analysis
Identifying Information Architecture
This was the condition of the donation system webpage and my process of mapping the page contents by type.
I identified that the majority of the donation methods were not actionable. As such, it was appropriate to first break down the contents of each page:
Actionable Donation: The user can conceivably make a donation. 
Informational: The user is provided with information, instructions, and data.
Subscription: The user can set up a recurring payment.
Impact story: The user is shown the history and background of the use of funds.
Non-relevant: One page was simply not relevant to donations.
Dead Pages (PDFs)
Additionally, many pages contained donation instructions only through PDFs that the user had to print and mail in. These PDFs were evaluated for function and later reimplemented into interactive payment systems.
Accessibility Issues
As a whole, the labeling of the sections made it very unclear what was to be expected on each page, which was why it was necessary to conduct this information architecture review. The equal-sized boxes give the impression that all of these are donation methods which proved to be highly inaccurate. Additionally, the buttons are not interactive buttons, they are baked into the image file.
02 User & Client Interviews
I conducted two client interviews, one user interview, and user usage data analysis to determine the needs of the project. Here are the key takeaways: 
1. Users (Donors)
By analyzing the previous year's PayPal report, it was determined that the vast majority (roughly 70%) of donations made to organizations are general one-time donations. The other 30% comprised seasonal appeals and the donors who set up yearly recurring payments. This last grouping of donors, though not many, made up much of the total revenue. 
2. Accountant
The accountant was experiencing major frustrations with donations made via the PayPal button not being collecting any information about the user beyond their first and last name, and billing address. She voiced that she often would have to contact the donors by phone or email to retrieve more information about them and manually input them into a database.
3. Communications Director
The communications director voiced the need for a streamlined way to connect marketing campaigns (ie. seasonal donation appeals) to specific form of donations. Currently, when they send out mail or e-mail campaigns, the donor would either need to call in with the donation, mail in a check, or use the generic PayPal button. 
03 Iterative Design Process: Iteration #1
First iteration
With limited time before a campaign launch, I developed a first iteration that contained all of the possible donation types in one interactive conditional widget. This solved the initial problem of making the donations more accessible. However, it didn't quite solve the information architecture issue because the users are prompted with too many choices. As noted previously, the majority of donations fall under a "general donation," and the remaining donation types are much less common.
04 Iterative Design Process: Iteration #2
Second Iteration: Creating an Experience
In order to solve this problem effectively, the user must be given fewer choices in order to guide their decision-making. 
1) First, the "general donations" must be the most accessible choice.
2) Secondly, we have a grouping of three donation types (In Lieu of Flowers, The Path Forward, and Seasonal Appeals) that broadly fall under a special donations category.
3) "Leadership Giving Circle," which is akin to a subscription system, is separated out as its own experience.
4) All other donation information is relocated to an informational section within an accordion menu.
5) Lastly, one of the original pages was an impact story, which is included at the bottom to add a social component in the landing page.
05 Final Design
Landing Page
The final landing page displays choices in the order best supported by the research. Users are first prompted to make a general donation, secondarily the more specific donation types, followed by recurring donations, and other relevant information that does not involve direct action.
Interactive Form Pages
Each of the four donation types that were identified as "actionable" were placed on individual pages to facilitate easy sharing in marketing campaigns. Each page form additionally has a unique decision architecture experience based on the type of donation. 
For example, the "The Path Forward" brick donation system adapted PDF donation form to a much more simplified and user-friendly experience on the form with conditional character limits and visual identifiers.
Back to Top