The team group chat went quiet for three days after someone floated the idea of a 4th of July team BBQ, and then one parent, the same one who organizes the end-of-season gift and remembers every kid’s food allergy, posted a full plan: time, location, a sign-up list for sides, a note about who was bringing the cooler. Nobody had asked them to do it. They’d just done it, the way they’d done it for the spring banquet and the snack schedule before that.
We noticed the pattern because we’d watched it happen all season, not just this once. The same parent ends up running point on team logistics that have nothing to do with coaching, and a holiday weekend BBQ doesn’t get easier just because it’s supposed to be a fun, low-stakes team hangout. Someone still has to pick a location, coordinate around a dozen families’ holiday plans, remind people to sign up for sides, and show up early to get the grill going before anyone else arrives.
Naming the pattern out loud is the first useful step. We texted the organizing parent privately, not in the group chat, and said something simple: thank you for doing this again, and next time let’s split the actual list of jobs before you take it all on. They said, honestly, that they usually end up doing it because nobody else offers first and they don’t want the event to not happen. That’s the whole mechanism in one sentence. The job doesn’t get split because nobody claims a piece of it before one person claims the whole thing out of necessity.
The fix isn’t gratitude, it’s a list. For this BBQ, we suggested breaking the event into specific named jobs in the group chat: someone confirms the location and time, someone manages the sides sign-up, someone handles drinks and ice, someone brings a cooler, someone helps break down and haul trash at the end. Naming the jobs specifically, rather than posting a vague “let us know if you can help,” gets actual volunteers, because a specific ask is easier to say yes to than an open-ended one.
We also paid attention to who volunteers for which job. It’s easy for the same handful of parents to take on the visible jobs, main dish, drinks, and for the less visible ones, cleanup, ice runs, the early arrival to set up tables, to fall on whoever always does them. Holiday weekends make this worse because more families have their own plans and fewer people have slack to give. We volunteered for setup and cleanup specifically, since those are the jobs people notice least and skip first.
We also thought about families for whom a potluck contribution isn’t a small ask. Not every household has an easy spare twenty dollars for a side dish and a bag of ice on a holiday weekend, and a sign-up sheet that assumes everyone can show up with a store-bought dish treats a real cost like a given. We tried to make the lower-cost jobs, cups, napkins, folding chairs, count just as much as the higher-cost ones, so a family with less room in the budget that month could still contribute something visible without it being the expensive thing.
We noticed the same dynamic shows up in who talks during the event, not just who organizes it. The parent who always runs logistics also tends to be the one fielding every question once people arrive, where’s the bathroom, is there a vegetarian option, what time are we leaving. We tried to route some of those questions to other parents on purpose, partly to lighten the load on the organizer and partly so the team didn’t develop a habit of treating one person as the only source of answers.
A few things that helped the actual event go well:
- A sin