Latest / 5 Minute UX / The Meeting Justification Test
Transcript
- 0:08This lesson is The Meeting Justification Test. Let's get
- 0:11started.
- 0:19A meeting is only valid if the necessary information or
- 0:21approvals cannot be obtained through more efficient channels.
- 0:24Before you schedule anything, you must verify that those
- 0:26specific results cannot be achieved by picking up the
- 0:29phone, sending emails, or using instant messages. This step is
- 0:31critical because the approach chosen must be the most
- 0:34efficient and effective way to get the required results. If a
- 0:36simple call gets the approval, a full meeting is a failure of
- 0:39process. There is a specific trap to avoid here. Do not use
- 0:41email as a crutch to avoid face- to-face or asynchronous one-to-
- 0:44one meetings when genuine interaction is required. The
- 0:47channel must match the complexity of the decision. If
- 0:49you need nuanced feedback or real-time debate, a text message
- 0:52won't cut it. But if the goal is just a yes or no, stop and send
- 0:54the email. This efficiency threshold is the foundation for
- 0:57the five-question verification framework we will use next.
- 1:05Diane Brewster-Norman, who created the Franklin-Covey
- 1:07Meeting Advantage workshops, frames the decision around five
- 1:10specific verification questions. You ask them to determine if a
- 1:12meeting is truly necessary before you commit anyone’s time.
- 1:14The first question is whether the total cost of the meeting
- 1:17justifies the advantages of holding it. This forces you to
- 1:19weigh the expense against the specific outcome you need.
- 1:21Next, you check if the people who can make decisions are
- 1:24available to attend, which is really about whether the timing
- 1:26is right. If key decision-makers are absent, the meeting often
- 1:28stalls. Then you ask if the purpose of the meeting is clear.
- 1:31You can’t move forward without a defined goal for the
- 1:33conversation. The fourth question asks if the necessary
- 1:35information is already available. If the data is
- 1:37sitting in an inbox, a meeting is redundant. Finally, you must
- 1:40ask if alternatives to holding a meeting have been considered.
- 1:42This ensures you’re not defaulting to a calendar invite
- 1:44when a quick email or phone call would solve the problem.
- 1:47Answering yes to these questions confirms that a meeting is the
- 1:49right channel. This verification process sets the stage for
- 1:51choosing the most efficient way to get the approval you need.
- 2:00Once you have answered the five verification questions with a
- 2:02yes, you have established a clear need for a meeting. This
- 2:05confirmation is the trigger for the next phase: selecting the
- 2:07right channel and timing. When you know your attendees are in
- 2:10the office, prioritize early time slots for the session. This
- 2:12strategic choice maximizes the likelihood of full
- 2:14participation, which directly supports the cost-justification
- 2:17argument you built earlier. However, the definition of a
- 2:19meeting is broader than a scheduled block on a calendar.
- 2:22Any discussion about a project, whether conducted via technology
- 2:24with distant teams or in person, constitutes a meeting. This
- 2:27means even a quick sync requires preparation, such as drafting a
- 2:30punch list of questions or a brief agenda. By treating every
- 2:32project discussion as a formal meeting, you ensure that the
- 2:35necessary information is always available and the purpose
- 2:37remains clear. This discipline prevents the drift that often
- 2:40turns casual chats into inefficient, unstructured
- 2:42interactions. You are now ready to apply this framework to
- 2:44specific approval scenarios.
- 2:52Say you need a stakeholder to sign off on a design change.
- 2:54Before you schedule a full team meeting, run the verification
- 2:57questions through that specific request. Can you get that
- 2:59approval by picking up the phone or sending an email? If the
- 3:02answer is yes, the meeting fails the efficiency threshold. If
- 3:04the approval requires a nuanced discussion that a text-based
- 3:07channel can't handle, consider a "minimeeting" instead of a full
- 3:09team session. This format involves only a couple of people
- 3:12discussing a limited number of issues, which minimizes the
- 3:14signal-to-noise ratio. You are applying the justification test
- 3:17to a scenario requiring project approvals by choosing the most
- 3:19efficient channel that still delivers the necessary result.
- 3:22That choice between a phone call, a minimeeting, and a full
- 3:24session is where the real work of justification happens, and it
- 3:27reveals the specific errors people make when they assume a
- 3:29meeting is the default.
- 3:36The most common failure is skipping the check to see if the
- 3:39necessary information is already available. You schedule the call
- 3:41because it feels urgent, but you never verify if a quick email or
- 3:44phone call would have gotten the same approval. This ignores the
- 3:47core principle that a meeting only holds if efficient channels
- 3:49fail. Another trap is ignoring the timing of decision-makers.
- 3:52You book the slot, but the person with authority is in
- 3:54another time zone or out of the office. The cost justification
- 3:56question gets skipped because the meeting feels routine. You
- 3:59assume it's free because it's just a chat, but you are burning
- 4:01hours on a conversation that could have been a text. Strong
- 4:04execution looks like pausing before you click send. You ask
- 4:06yourself if the people who can make decisions are actually
- 4:08there. You confirm that you have considered alternatives to
- 4:11holding a meeting. You treat the cost of their time as real, not
- 4:13abstract. Weak execution looks like a calendar full of slots
- 4:16where no decisions were made. You end up with unscheduled
- 4:18interactions that lack a punch list of questions. You miss the
- 4:21chance to use a minimeeting format with limited people and
- 4:23limited issues. The reason this matters is that your calendar
- 4:26reflects your judgment. When you apply the verification
- 4:28framework, you protect your team's focus. You stop treating
- 4:30meetings as a default and start treating them as a specific,
- 4:33justified choice. The moment you next see an open slot,
- 4:35you'll know the difference between a necessary conversation
- 4:37and a costly habit.
- 4:41Welcome to The Take. I'm joined by a fellow practitioner and
- 4:44together we're going to dig into The Meeting Justification Test —
- 4:47what it means in practice and what's worth remembering.
- 4:50[HOST] I kept coming back to that trap about using email as a
- 4:53crutch. It feels risky to suggest we avoid text for
- 4:56nuanced feedback. [LEARNER] Exactly. The danger is people
- 4:59using async tools to dodge real conflict. They hide behind a
- 5:02thread instead of addressing the tension. [HOST] That’s the
- 5:05signal-to-noise ratio issue. A minimeeting forces you to be
- 5:08present with the discomfort. [LEARNER] True, but have you
- 5:11seen how AI agents handle these "nuanced" discussions now?
- 5:14They’re getting too good at summarizing dissent. [HOST] So
- 5:17the AI smooths over the friction. It makes the "no"
- 5:20sound like a polite "maybe." [LEARNER] Yes. And that’s
- 5:23dangerous. We lose the raw data of disagreement when the tool
- 5:26filters it out. [HOST] It changes the cost justification.
- 5:29If the AI makes the meeting feel less painful, we stop asking if
- 5:32we need it. [LEARNER] That’s a subtle shift. We optimize for
- 5:35comfort rather than decision quality. [HOST] And that ties
- 5:38back to the timing question. If we don’t check if the decision-
- 5:41maker is actually there, we’re just performing. [LEARNER]
- 5:44Right. I’ve seen teams book calls where the boss is on mute.
- 5:48The meeting is a ritual, not a process. [HOST] It’s a failure
- 5:51of the efficiency threshold. You’re paying the time cost
- 5:54without getting the approval. [LEARNER] So the framework is
- 5:57really about respect for the attendee’s time. Not just
- 6:00efficiency. [HOST] Precisely. The calendar is a contract.
- 6:03Breaking it by scheduling without verification is a breach
- 6:06of trust. [LEARNER] That’s a heavier way to frame it. I
- 6:08usually think of it as productivity. [HOST] But
- 6:11productivity is the outcome. Respect is the mechanism.
- 6:14[LEARNER] I like that. It makes the "no" easier to give. [HOST]
- 6:17And it makes the "yes" more meaningful when it happens.