The average knowledge worker spends 12 hours per week in meetings. A significant proportion of that time is spent on decisions that could have been made asynchronously — team preference polls, priority votes, option selections — things that don't require real-time interaction. They require votes. The problem is that most teams don't have a structured way to run votes outside of meetings. So they schedule a meeting, spend the first 20 minutes catching up, spend 15 minutes debating the options, make a decision in the last 5 minutes, and then wonder why their calendar is always full. This guide shows you which meetings can be replaced with async decisions, how to run them, and what a realistic meeting reduction looks like.
Why teams over-meet: the decision vacuum
Teams schedule meetings for many reasons — information sharing, relationship building, collaborative problem-solving. But a large percentage of meetings exist for one specific reason: to make a decision. When there's no structured async process for collecting input and reaching a decision, the path of least resistance is "let's schedule a meeting." This creates a decision vacuum that meetings fill. The fix is structural: give teams a tool for making decisions outside of meetings. When a structured async process exists, the question shifts from "when can everyone meet?" to "what's the decision deadline?" — and that question has a much better answer.
Which meetings can be replaced with async decisions
Priority votes and ranking sessions
Sprint backlog prioritisation, feature roadmap votes, quarterly OKR priority-setting — any meeting where the primary activity is choosing between options or ranking a list. Replace with dot voting (for ranking) or ranked choice (for selection). Run async 24-48 hours before any review meeting.
Team preference polls
"When should we schedule the team event?" "Which catering option?" "What should we name the feature?" These are pure preference polls with no complex dependencies. They don't need a meeting — they need a deadline and a vote.
Decision alignment checks
Many teams schedule 30-minute "alignment" meetings to confirm that everyone agrees with a proposed direction. Replace with an anonymous temperature check vote: "Can you support this decision?" If the vote shows broad support, the meeting is unnecessary.
Vendor or tool selection meetings
After a shortlist has been established, the selection meeting is often just a structured vote with discussion. Run the vote async first. If there's a clear winner, skip the meeting. If the vote is close or contested, hold a shorter meeting focused on the contested items.
Retro action item votes
Sprint retrospective action items are perfect for async dot voting. After the retro generates ideas, run a dot vote to identify top priorities. This can happen in a 24-hour window before the next sprint planning rather than extending the retro meeting itself.
The async decision framework: structure, not just tools
Create the decision: options, context, deadline
Every async decision needs three things: clearly defined options (ambiguous options produce low-quality votes), enough context for voters to make informed choices, and a deadline. Without a deadline, async decisions linger indefinitely — which is worse than a meeting.
Share widely with a clear timeline
Share the decision in Slack, email, or wherever your team communicates. State the deadline explicitly. "Vote by Thursday 5pm" is better than "vote soon." Chooseday sends automatic reminders to anyone who hasn't voted — you don't have to chase.
Let the vote run privately
Anonymous mode prevents anchoring. Don't share partial results while voting is open. Let everyone vote without knowing how others have voted — this is especially important when senior team members are participating.
Share results and close
When the deadline passes, share the results with the whole team. Include the context: what was decided, why the options were what they were, and what the next steps are. A 3-sentence Slack message with the result is often all the "meeting" the decision needed.
Making remaining meetings shorter with async prep
Even meetings you keep can be dramatically shorter when structured async input precedes them. Before any decision-heavy meeting, run an async vote to identify the majority view. Walk into the meeting with data: "7 of 10 people ranked Option A first, 3 people ranked Option C. Let's discuss why those 3 people prefer C." You spend 10 minutes on the real disagreement rather than 40 minutes surfacing positions that a vote would have captured in 5. This pattern — async vote precedes sync discussion — consistently cuts meeting time by 50-70% for decision meetings.
A 30-day implementation plan for reducing meeting time
Week 1: Audit your recurring meetings
List every recurring meeting on your team's calendar. For each one, identify the primary purpose. Flag any meeting whose primary purpose is voting, preference collection, or decision alignment.
Week 2: Pilot async decisions for two "decision meetings"
Pick two meetings from your audit and run them async instead. Create a decision in Chooseday with the relevant options, set a 48-hour deadline, and share it. See if the meeting was needed after the vote.
Week 3: Add async pre-votes to 3 remaining meetings
For meetings you're keeping, add a structured async vote 24-48 hours before each one. Compare how much time was spent on options the pre-vote had already resolved.
Week 4: Cancel or reduce meetings that are consistently skippable
With 3-4 weeks of data, you can make a case for restructuring your meeting calendar. Cancel meetings that the async process replaced fully. Shorten meetings where the async pre-vote made most discussion unnecessary.
Frequently asked questions
Most excessive meetings exist because there is no structured way to make decisions without them. When a decision needs to be made, the easiest path is to schedule a meeting. An async voting tool eliminates the need for most "decision meetings."
Sprint planning prioritisation votes, vendor/tool selection meetings, team preference polls, retro action item votes, and "alignment check" meetings where the goal is confirming consensus. Any meeting whose primary purpose is to collect votes.
Async decisions maintain alignment because everyone still participates — on their own schedule. The decision record is visible to all. Anonymous voting often surfaces genuine views that live meetings suppress, producing better alignment than meeting votes.
Teams that systematically replace decision meetings with async tools typically reduce total meeting time by 30-50%. A 10-person team that moves 4 hours/week of decision meetings to async saves 40 person-hours per week.
Chooseday is designed specifically for async team decisions — majority voting, ranked choice, and dot voting with anonymous mode, deadlines, and permanent decision history.