CodeLab
Centralizing event discovery, RSVPs, and attendance for a 350+ member software and design agency.
ROLE
Product Designer
TEAM
4 Designers, 4 Developers
DURATION
1 month (August 2025 - September 2025)
TOOLS
Figma, Figjam
CONTEXT
Company
CodeLab is a UC Davis–based software and design agency that brings together UX designers and engineers to work on large-scale projects for industry and community clients such as Reddit, Snapchat, and Chevron, while offering professional development and social experiences.
Problem
CodeLab members struggle to keep track of the club’s many events, leading to missed attendance check-ins for general meetings and forgotten RSVPs or absences at official professional events.
Impact
Handed off to developers as an intuitive system that simplifies event tracking and attendance management.
HOW MIGHT WE?
How might we centralize event information so members can easily track events, RSVP, and Check-In all in one place?
Goals
Check-into attendance
Have a better way to check-into attendance that isn't manual and dependent on another person
RSVP easier
Provide a centralized and easy-to-find location to RSVP for events
Track Event Information
Easy view all events in one location, rather than varied annoucements/messages from several channels
USER FLOW MAP
Brainstorming how to tackle these problems
LOW-FIS
Solutionizing how to track events, display event details, and RSVP/Check-In
Calendar Page - tracking events
Events Page - event details, RSVPing, and Checking-In
CONSTRAINTS
Removing Calendar Page from our MVP
Why? Three reasons…
With events naturally being organized by date and filtering features, calendar didn't seem like it added much value
User POVs
Many users have their own personal calendar, so CodeLab calendar would have to naturally sync with other calendars to be beneficial
Dev Contraint
This app has a tight deadline, having to launch in less than a month. Calendar integration may not be the best use of time for our dev team.
MID-FI
Tacking user problems without Calendar
Mid-FIs
surfacing important events to increase RSVP rate
events will naturally be shown by whats most upcoming
tags and filters to track different types of events
different CTA for professional/social vs GMs
adding events available for admins
DESIGN SYSTEM
Creating the branding
Final Designs
Fleshing out Admin & Member Views
Member's View (without adding/editing events)
Admin View (can edit/add events & permissions)
REFELCTION
Challenges & Next Steps
Next Steps
Handoff to devs: The developers are currently working on building this app. We also have more teams focusing on other aspects of the app such as the user journey of onboarding, and a photo gallery that are connected to events.
What I would do better next time
User Research: If I had more time, I would have liked to do more user research, whether that be interviews or surveys. I feel like a lot of design decisions I made were a lot of "what ifs" and hypothesizing about the users actions, rather than actually finding data and research to support the decision. Due to the speed of this project, this project became more of a quick UI-heavy project rather than a more thoughtful fleshed out design process.
