GPSN × the Snap Foundation × an LAUSD high school, launching a one-year arts expansion. Rather than a standalone agenda, this submission plays the launch forward as it would actually happen: the email choreography that builds the meeting, the strategy notes behind each move, a 90-minute agenda with its sequencing logic, the prep materials, and what I'd do with more time.
This meeting will likely be the first time some of these stakeholders have been in a room together, and the person bringing them together is the newest hire at the table. The temptation is to run it like a funder kick-off: a big deck, grant logistics, a deliverables timeline. But the school is the party whose year gets disrupted, whose teachers have watched outside initiatives come and go, and whose principal will decide early whether this partnership is theirs or something happening to them. And with a one-year grant, the kick-off has to do more than make a good first impression: the year moves quickly, and momentum needs to start here. So everything below is built around three objectives:
We don't want the High School to feel they're being scrutinized, or that they've been handed extra work. We want them to feel they're receiving not just access to funding, but a community of support: one that wants to learn, hear, and become personally invested in the school's mission.
That concern shapes every email below: what gets asked of whom, in what order, and what never gets asked at all.
What follows is the coordination as it would actually run: two parallel email threads, one with the Snap Foundation and one with the school, converging into a single all-hands email with the agenda. Margin notes explain the intention behind each move. Names and dates are placeholders; assumptions are listed in section 8.
The first move is choosing where this meeting lives and how it opens. Both choices are designed around the funder's own culture, and both come from time spent inside it: I ran the Snap Design Academy alongside Snap's philanthropy team for three years and watched it grow to four academies.
Good morning, Snap Foundation team,
My name is Jose Garcia. I recently joined the GPSN team, and I'll be the liaison between the Snap Foundation, GPSN, and the High School. I previously worked with the Snap philanthropy team for three years running the Snap Design Academy, and watched it grow to four academies. I'm excited to work with the Snap family again.
In planning our new-year kick-off, I wanted to ask if it would be possible to meet at the Snap campus in Santa Monica. Additionally, if it's not too much to ask, would it be possible to open our session with Council, led by one of your facilitators?
We had the great opportunity to participate in Council with the students and instructors during the Snap Academies, and it always created a great introduction to the programs.
Best,
Jose
Council is a circle practice Snap's CEO Evan Spiegel grew up with at Crossroads School in Santa Monica: roughly a dozen people in a circle, taking turns "speaking from the heart." Spiegel brought it into Snap before the company was even formally established. Inside Snap it's a real institution: thousands of Councils have been held company-wide, led by trained facilitators at Snap offices around the world, with a talking piece passed around the circle. The practice traces back to the Ojai Foundation, whose Center for Council program has trained facilitators across Los Angeles for decades.
So this isn't a quirky icebreaker request. It invites the funder to open the partnership with their own cultural practice, one their facilitators already run every week, and one I've personally watched work as an introduction with students and instructors.
We don't want this to be another meeting. We want an experience, something that evokes the feeling of starting something new. For school staff, a morning at Snap's Santa Monica campus is an event, not an obligation; for the funder, it positions them as opening their doors rather than inspecting a school. The school's turf gets its moment too: the first next step out of this meeting is a visit to the school (see the agenda's close).
Two emails to the school. The first is a short, warm introduction with the meeting as a gift: a hosted morning, their choice of date. The ask to share comes only in the second email, after the date is theirs, and it's framed so the school controls its own story with zero preparation required.
Good morning Principal Doe and High School team,
It's great to connect with you! My name is Jose Garcia, the newest member of GPSN, and I'll be the liaison between our three teams. I look forward to meeting in person soon.
To launch the new year, we'd love to get everyone together for a morning kick-off meeting to get to know the teams and share what we're most excited about for the year.
The Snap Foundation has graciously offered to host us at their campus in Santa Monica on the following dates and times. Please let me know which works best for you and your team, and we'll send over a calendar invitation.
[Date option 1 · Date option 2 · Date option 3]
Best,
Jose
The school hears about this meeting as something being offered, a hosted morning at Snap with their pick of dates, before anything is asked of them. The funder was approached first precisely so that the school's first email contains a finished invitation, not a scheduling burden.
No grant logistics, no deliverables, no "expectations" language. First contact sets tone; the tone here is we're excited, this is real, and it starts with getting to know each other.
Thank you for confirming the date and time. I'll let the Snap Foundation team know and send over a calendar invite shortly. I'll also make sure to send over location and parking details once I receive them.
In preparation for the kick-off meeting, I'd love to dedicate a portion of our meeting to having your team share more about your school and your vision for this program, as well as for the future of the general student experience. My goal is for all of us to have a better understanding of your vision, so we understand how to best support you in that mission.
The overview can include any school history you'd like to include, the current programs you offer, needs and trends you're noticing with students, parents, and their experiences, and your vision, which can include general academic outcomes, specific programs, or just ideas you have jotted down.
I'll have an introduction slide ready for your team, and we'll present that while you share, but if you'd like to include any visuals, you're welcome to send over photos or slides and I'll make sure to have those prepared.
Time-wise, we'll schedule 20 minutes for your team to share.
Let me know if you have any questions or thoughts. I'm excited to get started.
Best,
Jose
The school gets the longest share of the morning, 20 minutes, but every mechanic removes burden: the prompt is a menu ("anything you'd like to include… or just ideas you have jotted down"), the slide is made for them rather than requested from them, visuals are optional, and the time box is stated so they can calibrate without guessing.
The framing sentence does the real work: "so we understand how to best support you in that mission." The school isn't reporting to the partnership; the partnership is orienting itself around the school.
The confirmation back to Snap carries the same share-framing as the school's, but the intention behind it is different.
Good morning Snap Foundation team,
Great news! The High School team just confirmed [date] works perfectly, so I'll go ahead and send everyone a calendar invitation placeholder. When possible, could you share any address and parking details, and I'll make sure to send those out.
Given that you've worked on a number of inspiring initiatives in the past, I'd love to dedicate 15 minutes of the meeting to your team sharing some of your favorite initiatives, so we can all get a better understanding of the work you do, and also learn about what's made these programs successful and created lasting impact.
I'll have a title slide presenting as your team shares, and if you'd like to share any photos or slides, that would also be great.
Thank you again for your support. We're all looking forward to it.
Best,
Jose
Working with Snap in the past, the hardest thing to identify was how they defined success, which is why I've avoided framing anything as "success metrics" among the stakeholders so far. They've always been conservative about publicity and impact-messaging around their philanthropic programming. That's admirable; you know the intention is pure. But it's challenging as an organizer when you don't know how you're being measured.
Asking their team to share the initiatives they're proudest of, and what made those programs successful and lasting, turns their segment into a window: the room learns what this funder truly values, and GPSN can set internal goals around that, without a single awkward "how will you evaluate us?" conversation.
Sequencing does quiet work here too: because the school's vision is voiced first, the funder's examples land as in service of that vision, not as a template the school is expected to fit.
Both threads converge in one email to all three teams.
Good morning everyone,
Thank you all for your support in coordinating our kick-off! We at GPSN are excited to get together, and I'm following up with the day's agenda and parking details.
Agenda · 9:00–10:30 AM · Snap campus, Santa Monica
9:00 · Council, led by a Snap facilitator
9:15 · GPSN welcome
9:25 · High School: your school, your vision
9:45 · Snap Foundation: favorite initiatives
10:00 · Before We Forget: capturing the morning's ideas
10:20 · Next steps & close
[Address · parking & arrival details]
You can also find the details in your updated calendar invite, and feel free to message me anytime.
See you all there,
Jose
Ninety minutes, per the brief. The convener talks least: GPSN holds 20 minutes total (welcome + close), the school holds the single longest share, and a third of the morning, Council plus the closing activity, belongs to everyone at once.
The arc: listen → share → capture → commit. Council teaches the room to listen; the shares give each team its voice; the activity harvests what the listening produced; the close converts it into named next steps before anyone reaches the parking lot.
The room opens in a circle: Snap's own practice, led by their facilitator. Everyone speaks; everyone listens; nobody presents.
Who's in the room, the partnership in one sentence, and the year at a glance.
History they choose to tell, current programs, needs and trends they're seeing with students and families, and their vision: outcomes, programs, or ideas jotted down. Their slide and any visuals are prepared for them.
The initiatives they're proudest of, and what made them successful and lasting.
Two rounds of sticky notes; every note read aloud. Full design in section 6.
Same-day recap email with every sticky transcribed · first working session scheduled at the school within two weeks · each team confirms its day-to-day point person · I draft the year-one roadmap skeleton from today's capture.
By 10:00 AM, everyone in the room has spent forty minutes listening, and listening generates ideas. This activity exists to catch them. In the room I'd frame it exactly like this: "As we've all been sitting here listening, I'm sure we've all had ideas come up: things we could do, inspiration from what we've heard. Before we forget those ideas, let's capture them." Two rounds, everyone writes, and I read every note aloud.
Every material below was committed to somewhere in the email threads; the prep list is simply the choreography kept honest. Nothing here is a 40-slide funder deck; each piece exists to remove burden from a partner or to make sure the morning's output survives the morning.
Agenda, welcome, and an introduction slide for each team, holding any photos or slides they choose to send. Purpose: the school and Snap share without preparing anything; their visuals are staged for them. Promised in emails 3 & 4.
Sticky notes, markers, and the two printed prompt cards for "Before We Forget." Purpose: the capture can't depend on improvisation; the prompts are worded in advance because the wording carries the design. Promised by the agenda.
Calendar invites, address and parking one-pager, arrival details, day-of contact. Purpose: the convener sweats every detail so partners never have to. For school staff crossing town on a school day, friction is tone. Promised in emails 3, 4 & 5.
The three parties, what the grant makes possible, the year at a glance, and who's who with contacts. Purpose: everyone leaves holding the same single page, the partnership's shared reference until the plan exists. Distributed in the room.
Pre-built before the meeting: summary, transcribed stickies, next steps with owners and dates. Purpose: the follow-up ships the same day; momentum is a deliverable, and the harvest becomes the first working document. Promised in the close.
Five materials, one of them a template and one a parking memo. That's deliberate: the meeting's centerpiece is the school talking and the room listening. Materials exist to protect that, not to compete with it.
Six slides: title cards and holders, not content. The people are the content.
The threads above assume email-first contact, because that's what the task's timebox allows. With a real runway, most of this would happen before email 1, and the kick-off would start even further downfield.
GPSN's brief invites candidates to use AI tools and note where and how. Here's exactly that.