The trip was great. Everyone had a brilliant time.
Someone found the route, booked the campsite, confirmed the headcount three times, made the gear list, chased people for their dietary requirements, worked out the food quantities, sent the directions, collected the money, organised the car shares, checked the weather, and sent the "remember to bring your waterproofs" message the night before.
At the end of the trip, everyone said "we should do this again." Nobody said "and you should organise it again."
What the group sees
From the outside, a well-run group trip looks effortless. You got sent some information, you showed up, and things worked out. The information was comprehensive, the timing was right, there was food and it suited most people, someone knew where to park, someone had the booking reference, someone had thought about what to do if the weather turned.
None of this looked like work because it was all done before you arrived. Pre-trip logistics, when they go well, are invisible.
What the organiser actually did
Organising a typical group outdoor adventure involves a surprising amount of distinct work.
Picking a destination means researching options, checking permit requirements or booking availability, thinking about access and parking, and honestly assessing whether the terrain suits the group's experience and fitness levels. That alone takes a few hours. Then comes proposing it to the group, which means drafting a message, answering questions, chasing non-responders, and interpreting a collection of ambiguous "maybe"s into a workable headcount.
Then comes booking, which usually means making financial commitments on behalf of the group based on a headcount that may still be shifting, often against non-refundable policies. Gear means deciding what shared kit is needed, working out who owns what, figuring out what needs to be borrowed or bought, and distributing the load so weights are roughly fair. Food means calculating quantities for the group, accounting for dietary requirements, building a shopping list, and either doing the shop yourself or coordinating who's bringing what.
Then there's transport and timing, a proper safety brief, and a pre-departure communication to the group that actually tells them what they need to know rather than just "see you Saturday." Most of this happens in the organiser's head, or in a tangle of documents and notes that only they have access to.
"Just let me know what I need to bring"
Every group has someone who says this. It's not malicious — it genuinely comes from a place of trust, confidence that you've got it sorted and they just want to be a useful participant by showing up ready.
But it concentrates the cognitive load in one person. "Let me know what I need" effectively means "I'm outsourcing the thinking to you." Multiplied across a group of eight, that's eight people outsourcing their preparation to one person who's already managing everything else. When the trip goes well, the organiser absorbs this quietly. When something goes wrong — and eventually something does — the pressure all runs back to that same person.
The appreciation asymmetry
Groups are generally grateful, and people enjoy the trip and are glad it happened. But the appreciation tends to land on the experience rather than the planning. "That was a great weekend" is not the same as "that was a great weekend and I'm aware you put twenty hours of invisible work into making it happen."
This matters because organising is real effort, spread over real time. When it consistently goes unacknowledged, organisers burn out. They start to feel resentful. Eventually they stop organising, and the group wonders why nobody seems to want to plan trips anymore.
Sharing the load actually helps
Distributing the work doesn't just protect the organiser — it makes the trip better. When one person owns everything, they become a single point of failure. If they miss something, nobody catches it. If their circumstances change and they can't attend, the trip is suddenly at risk.
When work is genuinely distributed, with someone owning gear, someone owning food, someone owning transport and communication, the planning becomes resilient. Multiple people know what's going on and are invested in making it work. The organiser becomes a coordinator rather than a one-person operation.
Making distribution work
The reason work doesn't get distributed usually isn't that people don't want to help — it's that helping requires clear tasks, and clear tasks require someone to define them first.
"Can anyone help with the planning?" produces vague offers that don't materialise into action. "Can you own the meal plan — quantities for eight people, accounting for a vegetarian and a nut allergy?" produces a defined piece of work that someone can actually take on.
The organiser still needs to structure the work initially. But once it's structured, other people can carry it. The first step is making the invisible work visible, not as a guilt trip, but as a genuine invitation for people to contribute. The second step is using tools that make distributed ownership actually work — a shared gear list that multiple people can edit, a food plan that lives somewhere the "food person" can update without going through the organiser, a task list where everyone can see what's done and what still needs doing.
The trip gets better, the organiser doesn't burn out, and the next time around, more than one person has the context to step up and do it again.