Imagine your team has missed two deadlines. Someone proposes a daily check-in. It sounds reasonable. If everyone says what they’re working on each morning, problems should be easier to spot. You’d probably have an opinion by the time I finished describing the situation.
Now imagine you’ve already voted for it. Then you find out that both tasks were waiting on the same approval, and both delays had been flagged days before the deadlines. Would you still add the meeting?
That’s an exercise I’d put near the start of a critical thinking workshop. The first vote gets people to commit to an answer before anyone makes a persuasive case. The second gives them a chance to see what their answer depended on.
Give everyone a minute to think before anyone speaks
Give participants three choices. Start daily check-ins, keep the current routine, or gather more information before deciding. Give them a quiet minute to vote and write down one sentence explaining their choice. Show the results once voting closes.
Then ask, “What would have to be true for a daily check-in to prevent the next missed deadline?”
One person might assume nobody noticed the delays. Another might assume the team noticed but waited too long to tell anyone. Both people might vote for the meeting, even though they’re trying to solve different problems. Ask for one reason from the majority and one from a less popular option before moving on. If the vote is unanimous, ask what might lead someone to choose differently.
Add new evidence, then ask the same question
Now reveal the approval bottleneck and run the same poll again. Before showing the results, give everyone the same sentence to finish. “I kept or changed my answer because…”
Someone who switches might say, “I assumed we had a communication problem. We knew about the delays. I’d set a backup approver.” Someone who sticks with the meeting might say, “I’d use it to escalate blocked tasks, but only if someone in the meeting can act on them.” That second person cast the same vote twice and still sharpened their thinking. Ask what they would do differently on Monday. Their answer will tell you more than the bar chart.
There’s a good case for keeping “gather more information” on the ballot. Make people name the information they need and what they’d do with it. “I’d check how often approvals sit for more than a day. If this happens every week, I’d assign a backup” is a decision in progress. “We need more data” can leave everyone exactly where they started.
Where a tool like VersyNow fits
You can run the two live polls and collect written questions with VersyNow. Participants join from their phones or laptops through a link or QR code. With anonymous Q&A enabled, they can raise objections without displaying their names to the room.
Give that question box a specific job. Try “What are we assuming about why the approval took so long?” A question like “Could anyone else approve the work?” gives the group something concrete to examine, even if only one person asks it. Read it aloud before the second vote. You can run the same exercise with slips of paper around a small table. I’d use a digital tool when collecting everyone’s answer by hand would eat into the discussion.
For the last two minutes, ask people to think of a decision they actually face this week. Have them write down their current choice and one thing they could check before committing. The next time someone says, “Let’s add a meeting,” they’ll have a better first question. “Where did the work get stuck?”