Creating a better user experience with a focus on onboarding and account management.
idonate provides tools for both charities and fundraisers to help them raise vital funds. idonate operates primarily as an online fundraising platform, where users can create their own page to promote their fundraising event, allowing family and friends to donate directly to their chosen charities.
idonate also provides a number of SaaS products and hosted fundraising solutions, such as their Virtual Fundraising Events that became so important during the COVID-19 lockdown and an Online Raffle Creator. Idonate allows charities to collect fundraising revenue through the idonate platform or directly through their own websites also.
I was approached by the founders of idonate to help them to reduce the large volume of support calls they were receiving from users, create a simplified navigation and site architecture to encapsulate the various additional products that they now offer under the idonate brand and create a fresh, new visual identity for idonate (including a logo design and new brand identity).
idonate needed help in reducing the large number of support calls they were receiving by creating a simplified navigation and site architecture.
The part I played
Logo Design & Brand Identity
I served as the sole UX and UI designer on the project, with full management of the project from the very beginning.
I undertook all of the UX research with input from sample users and stakeholders and worked as the sole UI designer from conception to completion before handing over annotated high-fidelity wireframes and video walkthroughs to the development team.
View related work for this project:
Design to Development
Data from integrated site analytics were studied and analysed to gain an understanding of the user demographics, behaviours and flows through the existing website.
Using the tool Hotjar, I took a snapshot of screen recordings of user interactions and collected data from click and scroll heatmaps.
This data highlighted some initial potential pain points around site navigation, inconsistencies in labelling and jargon. It also showed how users tended to interact with different elements on the site.
This data highlighted some initial potential pain points around site navigation and inconsistencies in labelling and jargon.
A full competitive benchmarking exercise was undertaken to gather a better understanding of the industry standard, potential user pain points, defined user mental models and opportunities to create a better user experience and use design as a competitive advantage over other fundraising platforms in use in Ireland.
I looked at the overall user experience in detail for each competitor, but focused extensively on the positives, neutrals and pain points involved in:
- =Homepage Layout and Content
- =Navigation & Information Architecture
- =User Account & Dashboard - Editing a Fundraising Page
- =Checkout - Donating to Somebody's Cause
The main findings from this exercise were that most competitors focused on a very simple, step-by-step onboarding setup, asking only for the absolutely essential information from their users. Account management varied from app to app, but provided great insight into opportunities for improvement and to gain a competitive advantage.
Account management varied from app to app, but provided great insight into opportunities for improvement and to use an improved user experience as a competitive advantage.
Usability Testing Sessions
& Depth Interviews
A series of usability tests were conducted on sample users with the goals of:
- =Determining the main source of user pain points
- =Identifying areas that cause confusion with users, especially around site architecture
- =Where any negative experience may cause user drop-off during onboarding
- =Evaluating the user experience of the donation process to spot any potential improvements or sources of user frustration
Based on these goals, I developed a series of tasks for the users to complete, including setting up a fundraising page for a sample charity, making some basic edits and updates to their fundraising page, promoting their page on social media and making a donation to another fundraiser using the search function.
The users were carefully chosen to give a range of computer literacy, age and device-preference. The testing sessions themselves were a mixture of in-person sessions and remote sessions. All sessions involved a depth interview afterwards to probe further into the pain points and mental models of the users.
The findings were invaluable. Serious pain points became evident around basic site navigation, onboarding and especially around the user dashboard and edit page functionality. User frustration was very high around these areas and depth interviews with the users brought about clear issues that needed addressing.
Serious pain points became evident around basic site navigation, onboarding and especially around the user dashboard and edit page functionality.
Pain Points & Opportunities
Click each post-it below for more information:
The user is expected to search for the event they are fundraising through by date, but this is not made fully clear, and because of this the user cannot find the event they are searching for and end up entering it manually. It takes the user a substanial amount of time and frustration before getting to their desired result.
Opportunity: Simplify the Event selection process
Remove the date-picker option and instead present the user with a simple search bar where they have control to search by event name, location or date.
Give clear feedback on what to do next if the desired event does not appear in search results: manually enter event details, but only visible after searching.
The user is asked during onboarding to select a short URL for their fundraising page. This is not a required step, but is configured to look like it is.
Error messages appear on the form before text entry and don’t clear until after the form has been submitted, which causes the user to think that they have incorrectly entered something and they get frustrated trying to figure out what a suitable entry should be without adequate feedback.
Opportunity: Use visual guidance
By presenting the text input field where the user is asked to select a short URL as it would look in a browser’s address bar, the user will understand at a glance what they are being asked to change here (using the SSL lock symbol and visuals matching common browser address bars). Clear help text advising the user and reminding them that this step is not mandatory also.
Having error validation not occur until after the form has been submitted will help reduce user confusion and frustration also.
When it comes to editing their page, the array of options overwhelms and confounds the user. The Edit Page section assumes the user will go through each step sequentially, rather than jump straight to the section they wish to edit. Presenting options “Next” and “Save and Exit” cause confusion with the users, and because each step needs to be saved before moving to the next often ends with them not saving their changes. The users are unsure of what options they are changing and where these changes or updates will appear on their page.
Opportunity: Simplified Dashboard Options and a Visual Page Editor
Nesting options under headings has caused much of the problem, so by giving each option it’s own defined section, the user should find what they want easily. User guides beside each option to help any user who gets stuck, reducing support calls.
Remove the Edit Page section and replace it with a visual page editor (using the Facebook mental model), where the user can edit sections visually on their page, seeing exactly what they are changing and updating without any confusion.
If the user wants to change the template of their fundraising page, they select from a number of drop-down select options, which are just non-descriptive text options. The user’s feedback was that they’d like to see a preview of what each template looks like before clicking on the option.
Opportunity: Pick a Page Template during onboarding
Based on the user feedback, it makes more sense for the user to pick a page template during their original signup (creating their fundraising page), rather than afterwards.
Include the page template selection in the Create a Fundraiser form process, showing thumbnails of the templates.
The FAQ page is a separate platform powered by ZenDesk. The landing page is configured to look very similar to the idonate homepage and the navigation options offer a “Home” button that leads to the landing page of the FAQ platform. All users had tremendous issues with getting back to the idonate website after going to the FAQ page, not realising that they were on a different platform/browser tab.
Opportunity: Change the Visuals of the FAQ page and provide a clear return route
The user was confused by the fact that the ZenDesk FAQ platform was styled to look very similar to the idonate homepage. By distinguishing the visuals of the FAQ page, it will help the user differentiate where they are. A clear “Return to idonate” navigation button that is always present at the top of the page will solve the “getting lost” problem.
The user is asked at the beginning of the donation checkout form to select a payment type (Credit Card, Apple Pay or Google Pay). Credit Card is selected by default, but users are still clicking on it and when nothing changes, they are thinking that it isn’t working and contacting support for help.
A lot of users are also wary of adding their contact phone number and address, which is a requirement of the credit card transaction provider, thinking that it is being shared with the charity that they are donating to. They are losing confidence in the security of their personal details and not finishing their transactions.
Opportunity: Split the process into three steps
By splitting the donation process into three separate steps, all of the pain points can be addressed.
1. The user selects a payment type and moves on to the next step.
2. The user fills in their donation amount and a message to the fundraiser and charity.
3. The user fills in their payment details. By keeping the payment details contained and separate to Step 2, the user doesn’t feel like their details are being shared with the charity, but for verification needs, using their mental models from other sites’ checkout process.
Many users commented on the lack of encouragement and joy throughout the site. Being a charity fundraising platform where users are essentially doing good deeds to help good causes, they expect to see more success stories and more joy, celebration and enthusiasm throughout the site.
Opportunity: Show Success Stories and Celebration
Showing success stories on the homepage front-and-center will remind users of the reason behind what they are signing up for.
Giving users a celebratory “well done” and using joyful, colourful animations throughout the onboarding and donation process will help to bring joy and enthusiasm to the site.
User Flow Maps
One of the biggest pain points that arose from the initial stakeholder interviews, user testing and depth interviews was that of the problematic and unintuitive site architecture of the existing site. User flow maps were created for a number of scenarios and personnas flowing through the idonate site. This was conducted as an exercise to visualise the existing user flow on both idonate and their sister-site ifundraise (which was now being incorporated into idonate with this redesign), and to improve the flow based on the data collected and by analysing the flow maps and user journey maps side-by-side.
One of the biggest pain points that arose during research was that of the problematic and unintuitive site architecture of the existing site.
Sketching & Low-Fidelity Wireframes
I always like to sketch a design out on paper first. Low-fidelity wireframes and concepts can be fleshed out very quickly and tested before moving on to more high-fidelity prototyping and development.
User Validation Testing
User validation testing brought about some tweaking that was needed, particularly around the Edit Page designs. Users weren’t immediately understanding the visual page editor and needed to be given a visual prompt. The solution came with a simple banner at the top of the page, that informed the user that they were editing their page, which in turn prompted them to look for the changes they wanted to make. Testing with clickable prototypes allowed for a quick iteration through the design process before moving on to higher quality wireframe devilerables.
High-fidelity, fully annotated wireframes for each page were designed using Adobe Xd. Design deliverables included a full design system, interactive annotated wireframes with downloadable assets and style guides, and for each flow I also delivered an instructional video demonstrating and showcasing each element on each page. I find that the video demos can help greatly in communicating a design to large teams of developers, like we were dealing with here, and can help to reduce confusion or misinterpretations of design elements (especially dynamic and interactive elements).
Thoughts & Learnings
idonate highlighted the importance of simplication in user flow – simplifying the jargon, breaking onboarding tasks into smaller steps helped to create a more user-friendly experience.
Drawing on established user mental models and moving from a set of overly-complicated forms to a visual page editor helped users understand the changes they were making to their fundraising pages, increasing the likelihood of more user engagement.
The scale of the project was much vaster than originally conceived. Upon reflection, I think a more Agile approach towards the project would have made the project more manageable and would have allowed for faster development, with more user testing. However, user test validation from clickable prototypes and iterating back through the design process was still a speedy and effective process.