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
      • icon picker
        Data Center
    • 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!)
/
/
Data Center
Share
Explore

Data Center

All the data behind this doc.
This doc has two main data sets:
⁠
All Calendar Events
⁠
: Everyone on your team uses the
Join the audit
⁠
instructions to sync their calendars into a combined table.
⁠
Full Action plan
⁠
: As you go through the steps in
Part II: Take action
⁠
, you will be adding actions to this central table. You’ll see the summary in
5. Action plan for our Meeting OS
⁠
. Press
Clear
⁠
to start fresh.
All Calendar Events
⁠
Full Action plan
⁠


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.