How to plan a trip when nobody wants to be the organiser

There's a person in your group who books things. They chase the deposit, remember the ferry, and know what time everyone's flight lands. If you're reading this, there's a decent chance it's you.

Here's the thing about that person: they're one trip away from not doing it again. And when they stop, the group doesn't find a replacement — it just stops going anywhere.

Why one person ends up doing everything#

It isn't because they're bossy or because everyone else is lazy. It's a fairly predictable dynamic:

Someone has to go first. A group of eight discussing a trip generates a lot of enthusiasm and no bookings. Eventually one person, uncomfortable with the drift, books something. That act makes them the owner of everything downstream.

Coordination work is invisible. Nobody sees the twenty minutes of comparing prices, or the four messages to the host. What they see is a link in the chat. Invisible work doesn't get shared, because nobody knows it needs sharing.

Asking for help costs more than doing it. Explaining what needs doing, to whom, with what constraints, takes longer than doing it. So the organiser does it. Each time this is locally rational and globally corrosive.

The state lives in their head. Because they made the decisions, they're the only one who knows them. Now every question routes to them, which reinforces the whole thing. (This is the group chat problem — state stored in a stream ends up centralised in one person.)

The fix isn't "everyone helps more"#

"Everyone should pitch in" is not a system. It's a hope, and it's the same hope that produced the current situation.

What works is named ownership of specific, bounded jobs. The distinction matters: "help with the planning" is unassignable, while "book the accommodation for nights 2 and 3" is a task with an owner and a definition of done.

The four roles#

For any group trip larger than four people, there are exactly four jobs. Name them, out loud, in the first conversation. They take between twenty minutes and two hours each across the whole trip.

The Timekeeper. Owns the dates and the schedule. Their job is that every agreed time is written down somewhere everyone can see, and that the group knows what's booked and what isn't. They don't decide anything — they record decisions and chase the undecided ones.

The Treasurer. Owns money visibility. Not paying for everything — making sure that every shared expense is logged with the right payer and the right split, and that balances are visible throughout rather than reconstructed at the end. Twenty seconds per expense; five minutes on the last morning.

The Quartermaster. Owns the shared kit and the checklist. Every shared item has a name against it before departure. This is the role that prevents the mallet problem.

The Navigator. Owns places and logistics: the route, the meeting points, the addresses, the parking. Their job is that nobody is ever typing an address while driving.

Four roles, four people. If your group is smaller, one person takes two. If it's bigger, nobody takes two.

Make the state visible, and the roles get easier#

Roles only work if the work is visible. If the Treasurer's records live in their notes app, the group is back to trusting one person's memory, and the Treasurer is back to being a bottleneck.

Put the four categories somewhere shared:

• Times on a shared timeline everyone can read and edit.
• Money in a shared ledger where each expense shows who paid and who it's split between.
• Kit in a shared checklist with names against lines.
• Places as saved pins everyone can navigate to.

This isn't a plug for any particular tool — a calendar, a spreadsheet and a shared note will do it. It is a plug for the property: everyone can see the current state without asking a person. That's what dissolves the bottleneck, and it's the reason Lumela puts those four things in one shared space rather than one person's inbox.

Decisions: the two-thirds rule#

The other half of organiser burnout is decision fatigue — the endless "what does everyone think?" that produces eleven opinions and no outcome.

A simple protocol that works:

1. Whoever proposes, decides. If you propose the place and nobody objects within an agreed window, it's booked. Enthusiasm without objection is agreement.
2. Set the window explicitly. "I'm booking this tomorrow at 8pm unless someone objects." Vague proposals die; deadlined ones get answered.
3. Objections come with alternatives. "Too expensive" isn't an objection; "too expensive, here are two cheaper options" is. This single rule kills most of the drift.
4. Two-thirds is consensus. Waiting for unanimity in a group of nine is waiting forever. Say up front that two-thirds decides, and the one person who wanted the other thing knows the rules going in.

What to do if you're the organiser now#

You can hand this over mid-trip-planning. It takes one message.

"I've been doing most of the coordination and I'd rather it wasn't all on me. I'll keep the schedule. Can someone take money, someone take the kit list, and someone take places and meeting points?"

Two things make this work. First, you're keeping a role rather than dropping everything, which makes it a redistribution rather than a resignation. Second, you're naming specific jobs rather than asking for help — people say yes to specific jobs.

Then, critically: let them do it badly. The Quartermaster will forget something. The Treasurer will log an expense with the wrong split. If you fix it silently, you've taken the job back and taught them it wasn't really theirs.

What to do if you're not the organiser#

Look at the four roles and take one, unprompted, before the trip starts. Say which one. Then do it.

It costs an hour across a whole trip, and it's the difference between a group that keeps travelling together and a group that has fond memories of the last time it did.