Rochester Area Community Foundation: Ticketing Experience
Skills
UX/UI, Leadership and Communication
Type of Project
Class + Client Project
Teams + Role
Team of Six : 3 Designers / 1 Front-End + project manager / 2 Back Ends; I, design lead + designer
What is the Rochester Area Community Foundation?
RACF, in partnership with generous philanthropists and community partners, works to improve the quality of life for people who live and work in the eight-county region through its leadership and strategic grant-making.
** Disclaimer ** Will only be showing the work I have worked on.
The Problem
RACF were going through a website reconstruction. They needed to create a system where the users can do these various actions:
Customers can apply for discounts
Website Administrators have a method of approving applications
Administrators and, as well as, community associates have the ability to view their progress and effectiveness of an event.
The Solution
As the designer, I was not too involved in the development of the reconstruction. However, we intended to build the website straight from code.
From the design perspective, we concluded to implement the following:
Different views for the following: administrators, customers and community-associates. Thus, we went with these three systems.
Administrators / Community Associates:
Adding events, venues
Data Analytics
Place where applications are approved.
Customers:
A ticketing system
A place to send in their application for discounts
Venues / Events Sections
Final Designs
Customer View: About a Venue
This is an example of a venue, how things are laid out. This contains important information and as well as events that will be present at the venue.
Customer View: Event Navigation
This is an example of a venue, how things are laid out. This contains important information and as well as events that will be present at the venue.
Customer View: Planning a Visit
This section is where a customer can select “Plan a Visit” this goes through a process of planning a visit. At the end, this is where they can apply discounts for coupons and SNAP Codes and such.
Key Take Aways / Learnings
Main Learning: Better understand the objective…..
While patience is obvious. However, I did not understand the notion of it and learned how to accept certain circumstances and results, especially with multiple people. I really had to learn how to work with them on various things such as: not knowledgable of Figma, unpolished designs, and allocating tasks fairly.
Another thing I learned: is situational management. For me, the team is more important than the project. If there is a conflict or lack of response, it’s better to resolve and try to ease the situation than directly keeping it professional. For example, related to task allocation, one of them is in a completely different time-zone, didn’t know how to use Figma and is juggling many classes. It wouldn’t be fair to give tasks that are strenuous.
The last thing I learned is giving productive feedback. Criticizing, and not acknowledging the efforts made to where they got to isn’t going to make those who aren’t confident about their own abilities want to be productive. This was a weird thing to understand because in a lot of different design communities, the act of tearing down a design is common practice.