Learning to Lead Without Leading: Notes from a Festival Organizer

 I'm organizing a community music festival, and I'm learning something I didn't expect: the hardest part isn't the logistics. It's figuring out how much to guide and how much to get out of the way.

I came into this with ideas. I had a vision for how the stages should feel, how rosters should work, how performers should think about their sets. What I didn't have — not yet — was a real understanding of how this particular community operates. So before I started handing down policies, I went to the open mics. I went to the jams. I listened.

That instinct, I think, was the right one.

Start with presence, not pronouncements.

It's tempting, when you're in charge of something, to establish authority early — to show people you have a plan. But credibility in a community group often works the other way around. You earn it by showing up, paying attention, and demonstrating that you actually care how things already work before you propose changing them. Attending those open mics taught me more about these performers than any planning meeting could have.

Offer structure as a floor, not a ceiling.

One of the first things I heard from the group was that some guidelines would be welcome — not a rulebook, but a starting point. That distinction matters. A floor gives people something to stand on. A ceiling just limits how high they can go. My job is to provide the former: basic principles around fairness, inclusivity, and community spirit, and then trust the stage hosts to build something genuine on top of them.

Distribute the work — and the credit.

I'm not running five stages. Five experienced people are running five stages, and I need to behave accordingly. That means sharing the scheduling function, looping in people who know things I don't (like Kim, our Stage Host Liaison, who knows this scene far better than I do), and making clear that the hosts' judgment matters more than my preferences when it comes to their own venue.

This is harder than it sounds. There's always a temptation to centralize, to keep things consistent, to make sure it all reflects your vision. But a community festival isn't your vision. It's the community's.

Meet people where they are — literally.

We're alternating meeting venues so that everyone can get to at least one gathering. It's a small thing, but it signals something: nobody's convenience matters more than anyone else's. The same logic applies to the rosters. Finalizing them by June gives performers time to prepare. Offering open mic nights as practice space gives newer performers a chance to "up their game" without pressure. Mentorship from veterans helps the whole community rise together.

These aren't just scheduling decisions. They're statements about whose success you're invested in.

Hold the line on fairness without becoming a gatekeeper.

One of my core commitments is that every performer gets a fair shot — one slot, one stage, real time to shine. That means resisting the natural drift toward letting the most enthusiastic (or most persistent) performers dominate. A long-handled shepherd's staff, metaphorically speaking, is sometimes required. But the goal isn't exclusion — it's making room. "Community takes the stage" only means something if the stage actually belongs to the community.

Know what you're good at, and offer it.

I'm good at building models — frameworks, templates, structural sketches. So that's what I'm offering: a singer-songwriter model, a small-combo model, a band model. Not mandates. Thinking tools. The hosts can use them, adapt them, or ignore them. But having something concrete to react to is often more useful than an open-ended ask.

I don't have this figured out. I'll call a mandatory meeting closer to the festival date, and by then I hope we'll have settled the questions that still feel open. But the bigger lesson I'm taking from this process is simpler than any agenda item:

Supporting a group means making their work easier, not redirecting it toward yours.

That's what I'm learning.