JavaScript required
We’re sorry, but Coda doesn’t work properly without JavaScript enabled.
Gallery
Team meeting audit: 3 tests for an effective Meeting OS (and 4 steps to fix it!)
Share
Explore
Gallery
Team meeting audit: 3 tests for an effective Meeting OS (and 4 steps to fix it!)
Team meeting audit: 3 tests for an effective Meeting OS (and 4 steps to fix it!)
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
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
Part I: Audit
4. Audit summary
The high-level results of your team's meeting audit.
Balance test
Total meeting time:
41.5
hours
Our team spends
26%
of the work week in meetings.
Flow test
Average flow time:
24.3
hours
Average flow percentage:
82.1%
Effectiveness test
Our shared effectiveness score:
3.75
out of 5
Individual summaries
Who
Overall time summary
Free time summary
Mtg time summary
Who
Overall time summary
Free time summary
Mtg time summary
1
Alan Chowansky
26% mtg time
30 hrs (84% flow)
11 hrs (78% effective)
2
Joel Davis
22% mtg time
31 hrs (88% flow)
9 hrs (72% effective)
3
Polly Rose
32% mtg time
27 hrs (69% flow)
13 hrs (74% effective)
4
Buck Dubois
23% mtg time
31 hrs (86% flow)
9 hrs (77% effective)
There are no rows in this table
Next up:
Part II: Take action
Gallery
Share
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Ctrl
P
) instead.