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
      • 4. Audit summary
    • icon picker
      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 II: Take action
Share
Explore

Part II: Take action

Now that you know where you stand, it's time to take action to improve your meetings.
1. Define our current Meeting OS
2. Minimize ad-hoc meetings
3. Find flow
4. Drive effectiveness
5. Action plan for our Meeting OS
We’re ready to take action!
With our audit in place, these next few pages will guide us through 4 different ways to improve our approach to meetings. In each page, we will add to a running action plan — brainstorming ideas, voting on which ones we want to take on, and selecting the top candidates.
And at step 5, we will see the aggregated
action plan
⁠
.
⁠
Clear action items
⁠
to start fresh.
⁠

Next up:
1. Define our current Meeting OS
⁠


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.