Signed in as:
filler@godaddy.com
Signed in as:
filler@godaddy.com
AutismWish grants wishes to autistic children for Christmas who have submitted a cumbersome web-based referral form. Most users were accessing the website via mobile devices and often sent support emails for assistance. My re-imagined mobile version created an intuitive experience and greatly reduced support requests.
Create a more positive experience for users who were currently expressing frustration with the referral process
Reduce the overwhelming amount of emails that were being sent to the support team
Increase the number of referrals that are successfully completed by the deadline
Upon reviewing the support tickets, it became very apparent that users found the referral process confusing. The image to the left is a snapshot of the Support team's inbox. Each email labeled [ACTION NEEDED] indicates an open support ticket. This was just one page out of dozens. After reviewing all the information and synthesizing the qualitative data, the following key insights became apparent:
I conducted a competitive analysis of five similar programs and thoroughly evaluated our competitors' strengths, weaknesses, strategies, and offerings. This allowed me to identify the gaps in our own product in order to inform the re-design.
The following is an example of information gathered from the competitor The Make-A-Wish Foundation:
Competitor Analysis: Make-A-Wish Foundation
Referral Process:
Benefits of the Referral Process:
Continuous Improvement:
By focusing on a robust and inclusive referral process, Make-A-Wish Foundation can effectively identify and support children with critical illnesses, ensuring that the wishes granted are meaningful and aligned with their unique circumstances. The streamlined referral process enables efficient coordination and communication among medical professionals, families, and the foundation, ultimately contributing to the positive impact of wish experiences for eligible children.
Baseline data indicated there were approximately 25 emails a day received by email support regarding the applicaton/referral process. After launch of the MVP, emails received dropped to about 2-3 daily.
I used Balsamiq to virtually draw out and externalize ideas, which could then be shared with the team. Once sketches were discussed and reworked, we touched base with the stakeholders. The sketches allowed us to ask follow-up questions during these meetings that would help clarify in more details. Whether it was allowing the primary stakeholder to express a vision or seeking clarification from the developer - we used sketching to help get us on the same page.
I designed several iterations of approximately 38 wireframes, which were frequently reviewed with my team and the primary stakeholder. Once we came to a consensus in the overall structure, information architecture and flow — we were able to focus on really developing the UI components and copy/content.
An initial draft of the redesign included social media login as an option. The problem here was that we currently did not have the technical capacity to execute such a login due to limitations within our database systems. For the same reasons, we were unable to implement login with SMS. However, I was able to be more flexible and expressive with the error messaging design. I was responsible for overseeing this project and ensuring the final illustrations were in line with our overall vision. It was important that these were clear, concise, and easy. The final illustrations represent a more holistic image with a fresh, clean tone.
Significantly fewer users called the call center for login and password retrieval assistance.
In a post-launch survey, users reported high satisfaction ratings and positive comments of the redesign.
The primary stakeholder personally congratulated our team on a successful launch. The project's success earned us a new client for future projects.