The timezone problem

It is not that remote teams decide badly. It is that the mechanism they inherited — talk until it's obvious — requires everyone in the same hour.

What replaces it is usually an open Slack thread, which has the same requirement in disguise: it rewards whoever is online, reading in real time and willing to keep replying. The teammate who opens Slack six hours later reads a conversation that has already narrowed, and either agrees with where it landed or reopens something everyone else considers settled.

The fix is not more discussion. It is putting the same fixed question in front of everyone and giving the decision a closing time that does not depend on attendance.

What an async decision needs

Structured options

An open thread rewards whoever is awake and articulate. A fixed set of options means the person who reads it eight hours later is answering the same question you were.

A deadline everyone can meet

24 to 48 hours covers every timezone's working day at least once. Verdo closes it automatically when the deadline fires — nobody has to be online for the decision to happen.

A rule that handles uneven turnout

Under majority an option needs votes from more than half of the people invited, not just whoever answered first, so an early timezone cannot carry the decision alone.

A result that doesn't depend on who was in the room

The authority rule is fixed before voting. Nobody who logs on after the deadline has to take on trust that the result was read fairly.

How it runs

  • Create itType /verdo in the channel. Set the question, the options, the method, the deadline, the authority rule and the owner.
  • People vote on their own timeFrom the Slack message or a link, whenever they are online. No meeting, no overlap window required.
  • Verdo chases the quiet onesNon-voters get one DM at 24 hours and one at 1 hour before the deadline. Voters get nothing.
  • The deadline closes itThe authority rule is applied automatically and the result is posted to the channel with the full breakdown.
  • The owner takes it from thereTagged in Slack, accountable for follow-through, and prompted a month later to say whether it worked.

The owner model

One name, before the vote

Not a team, not a channel, not “whoever picks it up.” The owner is set at creation and tagged in Slack where everyone can see it.

Accountable for follow-through

The vote decides what; the owner is responsible for whether it happens. On a distributed team that gap is where most decisions are lost.

The person the review goes to

30 days on, the owner gets one DM asking how it landed. Success, Partial or Failed, one tap.

Closing the loop

The habit distributed teams most often lack is checking whether a decision actually landed.

30 days after a decision, the owner gets one DM: Success, Partial, or Failed. One tap. Over a quarter that produces something no retro does — a record of which decisions worked, which quietly didn't, and which are worth revisiting.

Admins also get a Monday digest: open decisions, what was decided last week, what stalled, and which reviews are due. Two minutes to know where everything stands, without anyone opening a dashboard.

Frequently asked questions

How do distributed teams make decisions without meetings?
By making the decision asynchronous rather than the discussion. Fix the question and the options, choose a method and an authority rule before anyone votes, set a deadline that covers every timezone's working day, and name an owner. Everyone contributes when they are online, and the result arrives at the deadline without anyone having to be present.
What is the best deadline for an async decision?
24 to 48 hours for a team spread across three or four timezones — long enough that everyone sees it during working hours, short enough that it stays urgent. Anything past a week has no deadline in practice, because people respond in the last hour whatever you set.
Why does the authority rule matter for remote teams?
Because nobody is in the room to agree on what the numbers meant. Verdo fixes the rule before voting: under majority an option needs votes from more than half of the people invited, so a decision cannot be carried by whoever happened to be online. If no option gets there by the deadline, it stalls rather than defaulting to the most popular.
What happens if someone doesn't vote before the deadline?
Verdo sends one DM at 24 hours and one at 1 hour before the deadline, to non-voters only. At the deadline the authority rule is applied to the votes that came in. Under majority the decision closes; under consensus it does not pass without everyone. Either way the record shows who responded and who didn't, so a pattern of non-participation is visible rather than assumed.
How do you keep track of decisions across timezones?
A searchable log with a status on every entry. Verdo records question, options, votes, method, rule, owner and timestamp, tracks status through Active, Decided, Implemented, Stalled, Superseded and Reversed, and sends admins a Monday digest of open decisions, what was decided last week, what stalled and which outcome reviews are due.

Decide without the meeting.

Run your next cross-timezone decision on a 48-hour deadline and see it close itself.

7-day free trial. Card required. Cancel anytime during the trial with no charge.