Draw the line between what genuinely requires a live meeting and what should move to a written or asynchronous channel, so status and simple information stop consuming meeting time.
Once these norms exist, status moves off live meeting time and into writing, and people stop treating every message as urgent. This is what keeps the redesigned meetings from refilling with status recital.
| Goes to a live meeting (synchronous) | Moves to a written channel (asynchronous) |
|---|---|
| Real-time decisions | Status updates |
| Complex or sensitive discussion | Information sharing |
| Alignment that needs back-and-forth dialogue | Simple approvals |
| Relationship and trust-building moments | FYI and reference material |
Define where each kind of information belongs, so people know without asking.
| Information type | Channel | Expected response time |
|---|---|---|
| Urgent and time-critical | ||
| Routine coordination | ||
| Status and updates | ||
| Reference and documentation |
Your answers stay in your browser on this page and are never sent anywhere. These norms are honored at the individual level in the Communication Load Protocol.