The deadliest moment in a group trip is the destination conversation.
Six people, all of whom said yes to the trip in principle, suddenly cannot agree on where to go. Marcus wants Tokyo. Tasha wants Lisbon. Lebogang wants Cape Town. The host wants whatever everyone else wants, which is the deadliest position of all because it means no one is actually choosing. The chat goes quiet. The trip dies in week three.
This post is about the voting frameworks that actually break this deadlock. There are five that work. There’s one that everyone defaults to that’s worse than not voting at all. We’ll cover all of them.
Why “let’s just pick somewhere” is the worst possible approach
The default group dynamic is what I call “consensus by exhaustion.” Someone tosses out a destination, two people say “yeah I could do that,” one person says “ehhh,” and three people stay silent. After a week of this, the host eventually picks because the silence is unbearable. 30% of the squad is quietly disappointed. The trip happens but the picker is now the resentful host. (See: every group trip you’ve ever been on.)
The reason this fails is that the conversation has no structure. There’s no fixed candidate set, no deadline, no mechanism to surface preferences without confrontation. People with strong opinions dominate. People with weak preferences default to silence. The result feels democratic but isn’t.
The fix is to add structure. Below are five frameworks ordered from simplest to most rigorous.
Framework 1: First-past-the-post (the simplest)
Each squad member submits one destination they want. Whichever destination gets the most votes wins. Ties broken by coin flip or the trip host’s tiebreak.
When this works: Small groups (3-4 people), strong-opinion squads, trips where any of the candidate destinations would be acceptable to everyone.
When this fails: Larger groups where preferences are spread thin (everyone’s first choice is different), or when someone strongly opposes a winning destination but didn’t vote against it.
Variant: Veto power. Each member gets one veto they can spend if a destination they hate is winning. Use sparingly. If two people veto the same trip, you don’t have a squad, you have a fight.
Framework 2: Approval voting
Each squad member marks all destinations they’d be happy with, not just one. Whichever destination has the most approvals wins. This is the workhorse for groups.
Example: Five candidates: Lisbon, Tokyo, Mexico City, Cape Town, Paris. Marcus approves Lisbon, Mexico City, Tokyo. Tasha approves Lisbon, Paris. Lebogang approves Cape Town, Lisbon. Jen approves Mexico City, Paris. Casey approves Lisbon, Tokyo. Lisbon wins with 4 approvals.
Why this works: It surfaces the destination most people are okay with, not just the one with the loudest first-choice fan. Lisbon might not be anyone’s #1, but four out of five would happily go.
When this works: Most group trips with 4+ people. This is the default I’d recommend.
Variant: Rank-the-top-three approval. Each person ranks 1-3 candidates. First-choice = 3 points, second = 2, third = 1. Highest sum wins. Adds nuance without much complexity.
Framework 3: Budget-weighted voting
Real talk: the destination decision is constrained by budget. A 7-person squad with a $1,500 per-person budget cannot fly to Tokyo. The vote should reflect this.
How it works: Before voting, each person submits their budget. The destinations on the ballot are filtered to ones the squad’s combined budget can actually accommodate. Then approval voting on the survivors.
Why this matters: If half the squad has a $4k budget and half has $1.5k, you’re not picking between Lisbon and Tokyo. You’re picking between Lisbon and Mexico City. Voting on Tokyo is performative — it’ll never get booked.
TripSquad does this automatically. When Scout generates destination candidates, it filters for “destinations the squad can actually afford” before showing the candidates for voting.
Framework 4: The vetting round (for high-stakes trips)
For trips where the stakes are bigger — bachelorette, milestone birthday, family reunion — a one-round vote is too brittle. Use a two-round process:
- Round 1 (vetting): Anyone can propose any destination. Squad members can ask questions (“how’s the food scene?”, “how do we get there?”, “is the weather decent in May?”). Two days max.
- Round 2 (voting): Approval voting on the survivors of round 1.
This filters out impulsive picks (“oh let’s do Bali!”) and gives reluctant members a chance to surface concerns before they vote no.
Framework 5: Quadratic voting (the nuclear option)
Each squad member gets a fixed number of “vote points” (say, 10). They can spend them across destinations to express intensity of preference. Voting all 10 on one destination signals strong preference. Spreading 5/3/2 across three signals weak preferences.
When this works: Squads with very different intensities of preference. Someone who really wants Tokyo can outweigh three people who weakly prefer Paris.
When this fails: Most casual trips. It’s overkill. Save it for trips where someone’s birthday is on the line.
The deadline matters more than the framework
Here’s the truth: which framework you use matters less than that you actually use one and put a deadline on it. The biggest predictor of whether a group trip happens is whether the destination decision was made within 5-7 days of the squad agreeing to plan.
Trips that drag the destination decision past 2 weeks frequently die in the silence that follows. The chat goes quiet, inertia wins, the squad goes back to talking about TV shows. The longer the silence, the lower the odds the trip recovers.
So whichever framework you use, set a hard deadline for the vote. 5 days. After the deadline, the destination is decided and the conversation moves on.
How TripSquad does it
TripSquad’s voting is approval voting (framework 2) with a built-in deadline and an automatic candidate-generation step:
- Each squad member fills out their preferences (vibes, budget, dates).
- Scout generates 5 destination candidates that fit the squad’s combined preferences and budget.
- Each member approves the destinations they’d be happy with.
- After the deadline (host-set, usually 5 days), the destination with the most approvals wins.
- Ties are broken by Scout (the AI travel companion) using deeper context the votes don’t capture.
- The destination reveals at the same time on every member’s screen — a small ceremony so it feels like a moment, not a quiet announcement.
The reveal-at-the-same-time-on-every-screen part is the hardest to fake without a real app. It’s also the part that makes the trip feel real, and it’s why we built it that way.
What to do this week if your squad is stuck
- Stop asking “where should we go?” in the group chat.
- Pick approval voting as your framework.
- List 3-5 candidate destinations (do this yourself if nobody else will).
- Send the candidates to the squad with a deadline (5 days) and a tagline: “approve all the ones you’d be happy with. Whichever wins, we go.”
- After the deadline, the destination is fixed. No re-litigation.
Or use TripSquad and skip 1-5. We do them automatically.
Try TripSquad on the App Store →
By Bridgette Owusu, founder of Afia Labs and author of From Idea to Income with AI Apps.