---
title: "The Meeting Test I Use Before Asking a Team to Show Up"
url: "https://smallbizleader.com/insight/the-meeting-test-i-use-before-asking-a-team-to-show-up/"
author: "MING-YUAN XIE"
published: "2026-09-25"
updated: "2026-09-25"
---

# The Meeting Test I Use Before Asking a Team to Show Up

I used to treat recurring status meetings as a normal part of running a company. When information needed to move between people, the default solution was to put everyone on a call, share updates, and make sure nothing had been missed.

Over time, I changed one part of that system. I moved fixed status-reporting meetings to written, asynchronous updates. The meetings that remained were reserved for decisions, removing obstacles, and coordinating work across teams.

That change gave me a simple test before asking people to attend a meeting:

**If we cancel the next meeting, will a decision be delayed, a dependency become exposed, or the person responsible for the work become stuck?**

If the answer is no, the meeting probably does not need to happen.

This is not an argument that meetings are inherently unproductive. Some conversations are easier when people can respond in real time. A difficult decision may require several perspectives. An obstacle may need to be removed by someone outside the immediate team. Cross-functional coordination can also benefit from a shared conversation when the work cannot move forward without it.

The problem begins when a meeting is used to perform a task that does not require a meeting.

A routine status update usually asks people to report what has happened. That information can often be written down in a way that is easier to access, review, and reference. People do not have to remember every detail during a short reporting window, and others do not have to attend simply to discover whether anything relevant changed.

When I changed these fixed status meetings into written asynchronous updates, I personally observed that shared information became easier to access while collaboration remained healthy. That observation matters to me because the purpose of the change was not to reduce interaction for its own sake. It was to make interaction more deliberate.

The distinction is important:

- A status update communicates information.
- A decision meeting resolves an open choice.
- An obstacle-removal meeting addresses something preventing progress.
- A coordination meeting aligns people whose work depends on one another.

These categories can overlap, but they should not be treated as interchangeable. If a proposed meeting is only collecting updates, I first ask whether the same information can be shared in writing. If the meeting is intended to produce a decision, I ask whether the decision and the people needed to make it are clear. If it is meant to remove an obstacle, I ask what is blocked and who can unblock it. If it is for coordination, I ask which dependency requires a live conversation.

This test also changes how I think about attendance. The question is not whether someone is generally interested in the topic. The question is whether their presence is necessary for the outcome. A person may need the resulting decision or update without needing to sit through the conversation that produces it.

That does not mean every written update will be perfect. Written communication can be incomplete, unclear, or difficult to interpret. A team still needs judgment about when a document has created more ambiguity than clarity. When that happens, the meeting has a real purpose: clarify the issue, make the decision, remove the obstacle, or coordinate the dependency.

The limitation is that this is a practical operating rule, not a universal formula. I am not claiming that asynchronous updates are always better, or that every status meeting should be removed. The right choice depends on whether the team can access the needed information and continue working without a live conversation.

Before asking a team to show up, I return to the same question: if we cancel the next meeting, what specifically gets delayed, exposed, or stuck? If I cannot name one of those consequences, I usually start with a written update instead.

---

Ming-Yuan Xie is a Serial Entrepreneur & Founder of Meow Universe. Learn more at [https://xmy.tw/en/expertise](https://xmy.tw/en/expertise).