Skip to content
Team meeting audit: 3 tests for an effective Meeting OS (and 4 steps to fix it!)
  • Pages
    • Team meeting audit: 3 tests for an effective Meeting OS (and 4 steps to fix it!)
    • Facilitator Center
      • Data Center
    • icon picker
      Part I: Audit
      • Join the audit
      • 1. Balance test
      • 2. Flow test
      • 3. Effectiveness test
      • 4. Audit summary
    • Part II: Take action
      • 1. Define our current Meeting OS
      • 2. Minimize ad-hoc meetings
      • 3. Find flow
      • 4. Drive effectiveness
      • 5. Action plan for our Meeting OS
Team meeting audit: 3 tests for an effective Meeting OS (and 4 steps to fix it!)
/
Part I: Audit
Share
Explore

Part I: Audit

Steps to examine your current meeting structure.
Join the audit
1. Balance test
2. Flow test
3. Effectiveness test
4. Audit summary
Before we can build our Meeting Operating System, we need to take a hard look at our current meeting structure. The next group of pages sets up the audit process and then guides us through 3 key tests on meeting balance, flow, and effectiveness.
And at step 4, we’ll see the
audit summary
⁠
.

Now
Join the audit
⁠
.


Gallery
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.