Role
Visual, UI/UX, and
Interaction Designer
Team
2 Designers
3 Mentors
Tools
Figma
FigJam
Timeframe
12 Weeks
Overview
Goose aims to make events seamless by creating a centralized platform for event discovery and management for college campuses.
Houston, we've got a problem:
For students, events are an essential way of meeting people and engaging with their campus. However, many barriers make discovering and keeping track of events can be challenging and tedious, especially when students have to balance their social lives and academic coursework. Additionally, many students find that existing solutions are cumbersome, unintuitive, and ineffective.
Asking the important questions:
How do students discover events?
How do students keep track of events they plan to attend?
What issues do students have with existing solutions?
User Research
38
Survey responses
4
Semi-structured interviews
35
Affinity map notes

We found that…
80%
of students reported pain points related to campus events.
The most common complaint (42%) was the lack of a centralized system to discover and track events across campus.
Key Takeaways:
1
Most students rely on their memory to keep track of events and find themselves forgetting about them
3
Event organizers had trouble keeping track of expected attendance
2
Students typically discover events through the organization's social media channels, which can be limiting
4
Students were sometimes disappointed by events that didn't meet their expectations
5
Students noted timing and promotion methods prevented their attendance
Design Goals
Create a cohesive environment for seamless discovery and management of local events
Create a system that for event RSVPs and post-event feedback
Create a system that generates recommendations for prospective attendees
Create a system to help attendees keep track of their upcoming events
User Flow
Building off of our design goals, we created a framework for organizing our user's needs.

Wireframing
💡Idea: The user receives a feed of events like a dating app.
Our first idea was to create an app similar to a dating app, where users swipe through events they are interested in. The app's algorithm would use the user's responses to curate more and more relevant events.
Our first idea was to create an app similar to a dating app, where users swipe through events they are interested in. The app's algorithm would use the user's responses to curate more and more relevant events.
User Feedback
Problem: The "dating app" style feed is unintuitive.
During user testing, we found that delivering the events in a dating app style led to a subpar user experience. Users reported that the format made them feel rushed to make a decision
As a result, we redesigned the discovery system, creating a new interface that allows for more time to explore each event.
We also created two discovery pages for different needs: a curated "For You" page which contains recommended events based on the user's preferences, and an explorative "All Events" page which contains all of the upcoming events on campus.
Solution: Rethinking the feed

->

Experimenting and iterating…
Another challenge we faced was the organization of information on the event pages. This required several iterations to achieve a visual and functional balance.
Tying things together
In our final app prototype, users can…
1
Create an Account
New users can create an account with their university credentials and elect interests to curate a feed of recommended events.
2
Discover New Events
The "Discover" page has two tabs: one for a curated feed, and one for all the events happening on campus. These events are arranged in chronological order, and users can explore and sign up for events they are interested in.
3
Manage Upcoming Events
Users can receive push reminders before their events occur, and they can access the "My Events" page to view and manage events they have registered for.
4
Provide Event Feedback
Finally, users are prompted to give feedback on events they have attended. This feedback is provided to the event organizers, and is used to generate recommendations for recurring events.
Conclusion
Next Steps
If this project were to continue, there are several things that I would address:
1. Add functionality to the "Profile" and "Search" pages - While we created wireframes for those pages, developing the functionality for those pages were beyond the scope at the time. However, adding functionality to those pages would make the prototype feel even more cohesive.
2. Design a suite of organizer-facing solutions - While it was beyond the scope of our project, creating a system for event organizers to create and manage their events and organizations would also explore the other end of the student-event relationship.
3. Continue user testing to further refine usability - If there's anything I learned from this project, it's that you can never user test enough! User testing can reveal insights and pain points that go unnoticed while designing.
Reflection
When I started this project, I wasn't quite sure what to expect: I had never done a full case study before, and I wasn't really familiar with UXR and design. Over the course of the semester, I learned from three talented and experienced instructors who eagerly showed us the ropes of UI/UX design and provided constructive and helpful feedback. Tanvi and I also found a really great dynamic working together, and we were super proud of the project we had created. Ultimately, this project is what solidified my interest in UI/UX, and I'm super excited to continue to practice what I learned through this experience!
MADE BY STEVEN IN 2025 :D