What success looks like
Match the format to the work instead of defaulting to a video call. The practical test is whether the people involved can point to a format that supports the actual task without reconstructing the whole conversation.
If the same meeting also needs a purpose that names the change the meeting should create, read How to Write a Meeting Purpose Statement before finalizing the design.
| Target result | A format that supports the actual task |
|---|---|
| Method to use | Sort the work into information sharing, idea generation, coordination, decision, or relationship building; then choose synchronous or asynchronous delivery. |
| Failure to prevent | Treating every collaboration problem as a sixty-minute calendar event |
A practical method
Set the boundary for the work
Write a format that supports the actual task as the boundary. Keep only the evidence, authority, and participation needed to produce that specific result.
Work through the sequence
Sort the work into information sharing, idea generation, coordination, decision, or relationship building; then choose synchronous or asynchronous delivery. Place that instruction in the shared workspace and use it to distinguish the real work from background discussion.
Create a usable record
A durable record should make sense beside this example: A status update becomes a written check-in, while unresolved trade-offs get a 25-minute decision meeting. Name any owner, due point, decision rule, or review trigger needed for another person to act.
Worked example
A status update becomes a written check-in, while unresolved trade-offs get a 25-minute decision meeting.
The example connects directly to a format that supports the actual task. Put similarly concrete wording in the invitation, agenda, or record so the result can be checked later.
A failure to avoid
Watch for Treating every collaboration problem as a sixty-minute calendar event. If it appears, pause and compare the discussion with a format that supports the actual task before more meeting time is used.
A useful recovery question
Ask: “What is the smallest responsible move that would still create a format that supports the actual task?” If the answer depends on missing evidence, record that evidence, one owner, and the exact return condition.
Final checklist
- The stated goal is a format that supports the actual task.
- The working method is visible to everyone involved.
- The record is specific enough to support an example such as: A status update becomes a written check-in, while unresolved trade-offs get a 25-minute decision meeting.
- The design actively guards against Treating every collaboration problem as a sixty-minute calendar event.
Next, use the meeting health check to turn the method into a working artifact.
See how Meet You develops and checks meeting guidance, including the role of AI-assisted drafting.