058 Anatomy of a Successful Meeting - ProductivityCast

058 Anatomy of a Successful Meeting

You’ve likely experienced good and bad meetings in your work and personal lives. Meetings that seem to never end, or as aimless or dull that they possibly lull you to sleep or madness from boredom. On this week’s episode of ProductivityCast, we cover the anatomy of a successful meeting so that if you’re able to, you can lead your organizational gatherings, volunteer group huddles, church committee confabs, and/or family meetings in a positive, productive direction.

(If you’re reading this in a podcast directory/app, please visit https://productivitycast.net/058 for clickable links and the full show notes and transcript of this cast.)

Enjoy! Give us feedback! And, thanks for listening!

If you’d like to continue discussing managing digital notebooks from this episode, please click here to leave a comment down below (this jumps you to the bottom of the post).

In this Cast | Anatomy of a Successful Meeting

Ray Sidney-Smith

Augusto Pinaud

Francis Wade

Show Notes | Anatomy of a Successful Meeting

Resources we mention, including links to them, will be provided here. Please listen to the episode for context.

Doodle

LettuceMeet

Advisory Board Anatomy of a Great Meeting

3M Meeting Anatomy Guide

Outlook group scheduling

Google Calendar group scheduling

N.B. G Suite Calendar allows you to see coworkers’ availability for scheduling (if your G Suite Administrator allows it), as well.

GTD DC Meetup

GTD NYC Meetup

Everlast Rocketbook notebooks

Raw Text Transcript | Anatomy of a Successful Meeting

Raw, unedited and machine-produced text transcript so there may be substantial errors, but you can search for specific points in the episode to jump to, or to reference back to at a later date and time, by keywords or key phrases. The time coding is mm:ss (e.g., 0:04 starts at 4 seconds into the cast’s audio).

Download a PDF of raw, text transcript of the episode here.

Leave a Reply

Your email address will not be published. Required fields are marked *