FullyBeyond: CSUF's First Design-a-thon

Goal

To create a virtual design-a-thon event that fosters creativity, collaboration, and community while addressing real-world problems through UX/UI design.

We wanted to empower students to develop their confidence and enhance their design skills through a beginner-friendly environment.

Research & Planning Process

To address these challenges, we conducted extensive research and sought guidance from experienced design-a-thon organizers. Our team efforts included:

Attending Other Design-a-thons

Participated in events hosted by other universities to learn best practices, identify participant pain points, and observe event structures.

Connecting with Organizers

Consulted with experienced organizers from other universities to gain insights on securing sponsorships, structuring events, and navigating logistical challenges.

Drawing Inspiration

Incorporated key features such as workshops, mentorship sessions, and streamlined submission processes inspired by successful designathons.

Collaborative Planning

Formulated a tailored plan to create a beginner-friendly virtual designathon addressing CSUF's unique needs.

My Role & Contributions

As the Marketing Lead and a core organizer, I took on multiple roles, ensuring the event's success from planning to execution. My contributions included:

Marketing Strategy & Execution

Brand Identity

Developed and implemented FullyBeyond's brand identity, mission, and a compelling social media voice.

Engagement

Devised creative outreach strategies, such as interactive Instagram posts and an official Spotify playlist, to personalize the event atmosphere and foster excitement.

Content Creation

Designed newsletters, promotional materials, and beginner-friendly templates to encourage hesitant participants and make the event more approachable.

Community Building & Inclusivity

Participant Guide

Helped create a comprehensive, user-focused guide to ease participant anxiety, explaining the event timeline, team formation process, and submission requirements.

Team Matching

Personally ensured that every participant who wanted a team was successfully matched, fostering a collaborative and inclusive environment.

Onboarding in Discord

Facilitated community engagement by actively encouraging collaboration and extending the server's purpose to build a lasting UX community.

Workshop Contribution

Conducted a UX research workshop during the event, empowering participants to incorporate research-based methodologies into their projects.

Sama's birthday celebration.

Last meeting of the 2024 FullyBeyond Organizing Team.

Building Team Dynamics

Team Morale

Strengthened trust and camaraderie among organizers through shared meals and initiatives like team-building Spotify playlists, encouraging personal connection and collaboration.

Encouraging a Welcoming Team Atmosphere

Actively fostered a supportive environment by verbally affirming ideas, validating contributions, and encouraging quieter team members to participate.

1-on-1 Support

Provided personalized support to team members who couldn't attend meetings, ensuring they felt included and were able to contribute effectively.

Challenges Faced

Meeting Initial Deadlines

Early in the process, our team struggled to meet deadlines. I implemented a reward system that motivated accountability and encouraged teamwork, ultimately improving task completion.

Sponsorship Withdrawals

The week of the event, all sponsors pulled out. I instinctually decided to cover the prize funding myself to maintain team morale. However, my team rallied together to share financial responsibility, demonstrating resilience and commitment to our vision.

Logistics Complexities

We initially underestimated the challenges of onboarding participants across platforms (Devpost and Discord). I addressed this by consolidating processes, simplifying instructions, and providing updates to participants.

Participant Tracking

When acceptances were released, I noticed an issue that the RSVP Forms and Discord onboarding did not originally require participants to provide a consistent first and last names, which would create confusion with participant verification. I immediately notified my team and they addressed it in the Discord server, asking participants to adjust server names to first names, ensuring a smoother participation process.

Outcomes & Impact

Participant Success

We successfully created an engaging and educational experience tailored for beginners.

100+

Participants

Universities

75%

Beginners

Feedback indicated that participants had a positive experience and found the event valuable in developing new skills.

Community Legacy

Established CSUF's first designathon and created a foundation for future organizers to build upon.

Team Growth

Organizers gained invaluable skills in event logistics, marketing, and UX design. The bonds formed created a lasting sense of camaraderie and dedication within the team.

Lessons Learned

Marketing Overlook

A date discrepancy in participant submission deadlines caused confusion, resolved through clear communication and updates.

Team Communication Gaps

Transparency, timely communication is vital for smooth collaboration.

Sponsorship Challenges

Early outreach didn't secure enough support; a contingency plan is essential for future events.

Reflection

FullyBeyond wasn't just an event... it was a labor of love aimed at creating something our younger selves would have appreciated. From beginner-friendly workshops to ensuring participants found teams, every decision was meticulously made to empower others to grow and succeed.

This experience taught me the importance of trust, resilience, and adaptability. FullyBeyond wasn't just about building a platform; it was about creating opportunities for students to believe in themselves and their potential. The challenges we faced and overcame are a testament to the heart and dedication poured into this event.

Post-meeting activities.

BTS of marketing content.

The 2024 FullyBeyond
Organizing Team.

FullyBeyond

CSUF's inaugural UX/UI design competition.

Problem Statement