the systems behind the work
When handling complex initiatives, my workflow is rooted in bringing structure to big ideas, ruthlessly prioritizing milestones, and driving cross-functional momentum so projects land seamlessly.
Case Study 1
Overview
Role: Dual Enrollment Liaison / Campus Rep — Washington High School
Tools: In-person outreach, email, workshops, tracking spreadsheets
The Problem
When I took over as campus rep, there was almost no institutional presence at this high school — prior years had generated only 10 total contacts. There was no established process for reaching students, tracking where they were in the enrollment funnel, or following up before they dropped off.
What I Built
-
On-campus presence 3x/week to build consistent visibility and trust with students and staff
-
Bimonthly tabling to catch walk-up interest
-
Weekly classroom presentations across 5–10 classrooms
-
4–5 workshops per month, each with ~30 students, to move students from "curious" to "enrolled"
-
A tracking system to manage each student's individual progress through the enrollment process, since everyone entered at a different stage
The Result
123 new enrollments in one year
Up from a baseline of 10 contacts total in the years prior. Enrollments roughly doubled month over month as the outreach cadence took hold, building toward that year-end total. I'm on track to roughly double that number again in the next fiscal year as the program matures. This wasn't optimization of an existing system; it was building the system, and the presence behind it, from nothing.
Case Study 2
Overview
Role: Marketing Lead (Volunteer Staff)
Tools: Google Sheets/Excel, Asana, Mailchimp
The Problem
Resonate's Young Adult Program, PRIME, attended two annual retreats each required coordinating venue and vendor logistics, budget tracking, a full schedule/itinerary, on-site staffing, and attendee registration and communication. Five concurrent workstreams, each retreat held annually, with real budget and vendor stakes and no margin for dropped details.
I worked as part of a four-person team where ownership stayed fluid. Everyone regularly stepped outside their formal title to cover what the event needed, so while my role was Marketing Lead, the actual work spanned full-scope event coordination.
The Result
Delivered two annual retreats end to end, each running five concurrent workstreams against a single shared timeline and tracking system I built and maintained. That system turned what had previously been managed ad hoc into a repeatable operating model — one the team could run again each year without rebuilding the process from scratch. No dropped details or last-minute scrambles across either retreat, despite the volume and complexity.
What I Built
-
Built a master timeline and tracking system in Asana that sequenced venue booking, budget approval, itinerary finalization, and staffing assignments across both annual retreats, giving the four-person team one shared source of truth instead of scattered updates across texts and emails
-
Used that system to source and manage venue and vendor logistics end to end, from initial booking through final confirmation
-
Tracked budget and costs against the timeline inside the same system, so any workstream running behind or over budget surfaced early instead of at crunch time
-
Built the full schedule and itinerary for each retreat within the tracker, sequencing sessions, activities, and logistics across the entire agenda
-
Assigned and managed volunteer and staff roles through the system, keeping execution on track on-site
-
Owned attendee registration and communication, from initial signup through pre-retreat logistics information
Case Study 3
Overview
Role: Dual Enrollment Liaison (Ohlone College) & Marketing Project Manager, Volunteer (Resonate) — concurrent
Tools: Asana, Calendar, Microsoft Workspace/SharePoint
The Problem
While running Ohlone College's outreach program and coordinating Resonate's programs and retreats simultaneously, dozens of recurring and one-off commitments were competing for attention across both organizations at once: social media posts, newsletters, meetings, prep for workshops, tabling, and 1:1 meetings, coordination with high school counselors, admin, and college tech, plus graphics for Resonate's different programs. With two organizations, multiple audiences, and no single shared view of what was due when, the risk wasn't any one task falling through. It was losing track of the full picture across roles entirely.
The Result
Ohlone's outreach program and Resonate's programs and retreats were both sustained at full scope without either one getting dropped to cover the other. Every recurring and one-off commitment across both organizations had a visible place in the system, so staying on track didn't depend on memory alone.
What I Built
-
Built a unified system in Asana and calendar tools to track every recurring and one-off commitment across both organizations in one place, instead of relying on memory or separate lists per role
-
Color-coded and categorized tasks by organization and type — Ohlone outreach vs. Resonate programs, content/graphics vs. meetings vs. event prep — so I could see at a glance where attention needed to go each day
-
Time-blocked recurring commitments — workshop and tabling prep, 1:1 meetings, coordination check-ins with high school counselors, admin, and college tech — so competing priorities had dedicated space instead of getting squeezed in reactively
-
Used the same system to plan social content, newsletter sends, and graphic requests for Resonate's programs alongside Ohlone's outreach calendar, keeping both workstreams visible side by side rather than siloed
