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
    • Part I: Audit
      • Join the audit
      • 1. Balance test
      • 2. Flow test
      • 3. Effectiveness test
      • icon picker
        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

4. Audit summary

The high-level results of your team's meeting audit.

Balance test

Total meeting time:
45
hours
Our team spends
28%
of the work week in meetings.

Flow test

Average flow time:
22.4
hours
Average flow percentage:
78%

Effectiveness test

Our shared effectiveness score:
3.75
out of 5

Individual summaries

Who
Overall time summary
Free time summary
Mtg time summary
26% mtg time
30 hrs (84% flow)
11 hrs (78% effective)
24% mtg time
30 hrs (83% flow)
10 hrs (72% effective)
35% mtg time
26 hrs (62% flow)
14 hrs (74% effective)
27% mtg time
29 hrs (82% flow)
11 hrs (77% effective)
There are no rows in this table


Next up:


 
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.