How to stop work being blocked waiting on a decision

Treat a pending decision as a dependency with a due date, not a request for feedback. Write the decision as one precise question, name one owner, set a deadline that states what waiting costs, propose a default, escalate on a fixed clock, keep unblocked work moving, and record the outcome so it isn't reopened.

Why decisions block work

The architecture call that waits for one more opinion. The release call nobody scheduled. The change window that waits for someone to say yes. The work is ready, but the decision isn't. Three things are usually missing.

1. A deadline

Without one, “let's think about it” has no end.

2. An owner

When everyone is consulted, nobody is accountable for closing it.

3. A record

Decisions made in a thread get lost and reopened weeks later.

Count the cost in blocked days: days waiting multiplied by the people waiting. A three-day wait on a five-person team is fifteen person-days.

The 7-step playbook

1. Write the decision as one question

Not “what should we do about auth?” but “Do we use provider A or provider B for the first release?” List the options, your recommendation and the trade-offs.

2. Name one owner

If you use DACI, that means one Driver who prepares it, exactly one person who makes the call, Contributors who advise, and Informed people who get the result. If the team decides by vote, still name one person who acts on the result.

3. Set a deadline and say what waiting costs

“We need this by Wednesday 3 p.m. After that the release slips a week.” A visible cost turns a low-priority question into a scheduled one.

4. Separate one-way doors from two-way doors

If the choice is cheap to reverse, decide quickly and move on, behind a feature flag if needed. Save the long process for decisions that are expensive to undo.

5. Propose a default

“Unless there's a blocking objection by Friday, we go with B.” People can react to a recommendation faster than they can build an answer from scratch.

6. Escalate on a clock

Day 0Decision requested.
Day 2Reminder to anyone who hasn't weighed in, with the cost of waiting.
Day 3Escalate to the sponsor.
Deadline passedApply the default, or pause the work and replan explicitly.

Meanwhile, keep unblocked work moving: interfaces, mocks, tests against an abstraction, the common path.

7. Record the outcome

The decision, who made it, the options considered, the reasoning, the date and what would make you revisit it. Then check after a few weeks whether it worked.

Copy-paste request template

Decision needed: [one precise question]
Options: A) … B) …
Recommendation: B, because …
Owner: @name
Deadline: [day, time]. If we miss it, [cost of waiting].
Default: If there's no blocking objection by the deadline, we go with B.

Where Verdo fits

Verdo automates the parts of this playbook that depend on someone remembering. Here's what it does and doesn't do.

Step	Verdo
1. One precise question	You write it in /verdo. /verdo suggest <topic> can propose options, and the six built-in templates (Architecture Decision and Vendor Selection among them) pre-fill the modal.
2. One owner	Optional owner field. When one is named, the owner is shown on the decided card and gets the outcome review.
3. Deadline	Required when you create the decision, prefilled to 48 hours (or the template's hours). The people you pick as participants vote through a one-click vote link from the card. At the deadline Verdo closes the vote and applies the majority or consensus rule you chose.
4. One-way vs two-way doors	Your call.
5. Default	Put it in the question. Verdo doesn't auto-apply a default.
6. Escalation clock	Reminders to non-voters 24 hours and 1 hour before the deadline, by Slack DM with an email fallback (a deadline under 24 hours gets only the 1-hour reminder). If no option wins (no votes, no majority, a tie, or consensus not reached), the decision is marked stalled and the creator is told. From the dashboard you can extend it once by 24 hours or mark it superseded. Verdo doesn't escalate to managers.
7. Record and outcome	Every decision is searchable, with filters and an audit trail, and can be marked implemented, reversed or superseded. Export to CSV or JSON. After 30 days the owner (or the workspace owner, if none is named) is asked in Slack whether it worked: Success, Partial or Failed.

Written by the team behind Verdo. Verdo details checked against the product on 3 November 2026.

Verdo is for decisions the team votes on in Slack. If one person decides alone, ask them directly. The playbook still applies.

Pro is $49/month per workspace (Business $149/month), each with a 7-day free trial.

Frequently asked questions

What is the DACI framework?

A way to assign decision roles: a Driver who prepares the decision, one accountable decision-maker, Contributors who advise, and Informed people who hear the result. Its main rule is that exactly one person makes the call.

How long should a team decision take?

Most reversible team decisions should close within two to three working days. Set the deadline when you ask, not after the discussion stalls.

What should happen when a decision deadline passes?

Apply the stated default, or pause the dependent work and replan on purpose. Don't let it slide silently.

How do you stop decisions being reopened?

Record them where people will find them: the question, the options, the result, the owner and the date. Point to the record when the question comes back.

Or type /verdo and let the clock run itself.

The question, the deadline, the reminders and the record, handled for you. The default and the escalation stay with you.

Start 7-day free trial See pricing Add to Slack

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