Picnic Sessions: Listening Beyond the Brief
LISTEN · COMMUNITY EVENT SITE
LISTEN · COMMUNITY EVENT SITE
This page shows the website I built in Google Sites for Picnic Sessions, an open-air gathering in Phoenix parks with music from Resident DJ Ashwagandha, known as Perry. Below, you’ll see what I heard, what I built from it, and screenshots of the live site.
Rather than build the site only from what Perry described, I went to several events myself. Each night had its own personality, from the music and the crowd to the park where everyone gathered. I took photos and captured TikTok videos of the people, performers, and vendors, then built the site around them, with event photos, a TikTok feed, social links, and a park finder link.
I wanted someone visiting the site to get a feel for the experience before ever showing up.
Picnic Sessions moves between Phoenix parks, with locations announced through Instagram and TikTok. Someone discovering the event might want to know who's behind the music, where to go, how to participate, or how to make contact.
I wanted the websites to answer those questions while still capturing what made the gatherings enjoyable in the first place.
I created two connected Google Sites: one for Picnic Sessions and another for DJ Ashwagandha.
The Picnic Sessions site brings the event experience to life through photos and videos, with access to park information and community merchandise. The DJ site introduces Perry and gives visitors a way to contact him.
To keep the scope realistic, I connected visitors to existing City of Phoenix park listings and Google Maps directions instead of building a separate park finder.
See the scope statement →
My approach began with observation. By attending the events, I could see what visitors experienced and hear the kinds of questions they asked.
Those observations became my starting point for identifying end-user needs. Each question pointed toward a feature, from introducing the DJ to finding a park or reaching him directly.
It was a practical lesson in requirements elicitation: sometimes you learn more by being where the activity happens than by relying on a description of it. Once the first version was ready, I walked Perry through a working draft. Seeing it, he could finally say what he needed, and that review became a second round of elicitation. I set aside ideas Google Sites couldn’t support well, such as auto play music embeds.
On the live site, a visitor’s path to an event works like this: from the Where We Meet page, they select Find A Park Here, pick a park from the City of Phoenix listing, and open its address in Google Maps to get directions from their own starting point.
I had a lot of fun building both sites. I was genuinely impressed with what I could create and how professional they looked.
Perry liked the website, too, but he didn't know what to do with it. And looking back, I understand something I missed.
I listened closely to the community, but not closely enough to the person who would have to run and maintain the site, the stakeholder who mattered most after launch.
If I started over, my first question to Perry would be: "What is the most important thing you'd want the website to convey to its visitors?"
Then I'd build around that one purpose. I think a site centered on his main goal would have felt less intimidating and been easier for him to maintain.
Google Sites · TikTok · Instagram · Printify · City of Phoenix park finder + Google Maps (linked existing tools)
Delivered two weeks ahead of the three-month timeline, so the site was live for summer events.
This project showed me why listening has to include both the people using something and the stakeholder responsible for it.
I observed the community, translated questions into website features, and built two connected sites. But I also came away understanding that a professional-looking result isn't enough if the owner doesn't know how to carry it forward.
That's a lesson I'll take into every future project: understand what people need, but also understand what the owner is prepared to maintain.
Each feature traces back to a need I heard or saw.
"Who is he?" → A Meet DJ Ashwagandha button connecting visitors to the DJ website I built.
"Where is it, and how far is it from me?" → A Find A Park Here button linking to the City of Phoenix park listing, where visitors can use a park's address with Google Maps for directions from their own starting point.
"Can I be part of it?" → A merchandise page featuring tee and tote mockups created with Printify, reflecting the sense of belonging around Picnic Sessions.
“How do I reach him?” → A contact form on the DJ website I built, with TikTok and Instagram links on the Picnic Sessions site.