Product
Company
Resources
Free tool · no signup
Should this be a meeting?
Answer six quick questions. You get a straight answer (skip it, go async first, keep it small, or meet), why, and a message you can send.
Updated October 4, 2026 · By the Align team
1.Do people disagree, or does a decision need everyone's input?
Real disagreement is hard to settle in writing.
2.Will it take more than two rounds of back-and-forth?
Fast replies and follow-up questions favour talking.
3.Is it sensitive: feedback, conflict, bad news or a big change?
Tone gets lost in text. People want to hear it from a person.
4.Could one person answer it in writing?
If one person holds the answer, ask them, don't convene.
5.Is it mostly sharing information or a status update?
A short written update is faster for everyone to read.
6.Would more than eight people need to be there?
Past eight people it turns into a presentation, not a discussion.
How to use it
- 1
Answer six yes/no questions
About disagreement, back-and-forth, sensitivity, who holds the answer, information sharing and group size.
- 2
Read the verdict
Skip it, go async first, hold a small meeting, or meet.
- 3
Send the message
Copy the ready-made message or invite text that fits the verdict.
The rule of thumb behind it
Meetings are good for disagreement, sensitive conversations and fast back-and-forth. They are poor for sharing information or for questions one person can answer. The six questions test for exactly those cases.
| Situation | Better as |
|---|---|
| One person holds the answer | A direct message |
| Status or information | A short written update |
| Disagreement or a hard decision | A small, short meeting |
| Sensitive feedback or bad news | A conversation, one-to-one or small |
| More than eight people | A written brief, then a smaller meeting |
If you do hold the meeting
- Send the question and the options the day before.
- Invite only the people who decide or know.
- Start with the goal and stop at the decision.
- Write down who does what by when before anyone leaves.
Frequently asked questions
How do I know if a meeting is necessary?
It is when people disagree, the topic is sensitive, or the answer needs fast back-and-forth. If one person can answer in writing, or it is just information, send a message.
Is the answer always right?
It's a rule of thumb, not a ruling. It is built to push you to try writing first when a meeting isn't clearly needed.
Are my answers saved?
No. The check runs in your browser and nothing is sent anywhere.
What if I answer no to everything?
Then there is probably no decision to make and no discussion to have, which usually means a message will do.
Related free tools
Go deeper
- 5 min readHow to end a meeting with a decisionWhy meetings end without a decision, and seven habits that fix it: one question, a decision owner, time boxes, an explicit roll call and a written record.Read more
- 6 min readHow to run a go/no-go meetingHow to run a go/no-go meeting: who to invite, launch criteria, a 30-minute agenda, getting a clear yes or no from every owner, and a copy-paste template.Read more
Let tomorrow’s standup write itself
Sign up, connect Jira or Linear (or just use Plans), and hold your standup as usual. The tickets are drafted by the time you hang up, and the next update is ready before anyone asks.
Free plan Two-way sync Nothing moves without your OK
Done yesterday
ENG-219 · Invite flow
In review
ENG-205 · Billing webhook
ENG-231 · from Daily standup
Ship the onboarding flag for new teams