My Love (or Hate) Affair with Meetings

Years ago, I began to get annoyed with meetings. I wasn’t quite sure what I didn’t like about them, so I attended as few meetings as possible. Of course skipping all meetings is somewhat of a CLM (career limiting move), so I had to be selective. Sometimes I left meetings energized and felt like they were a great use of my time, but mostly, I wished I could have had the hour back plus compensation for emotional damage.

Eventually, I discovered Pat Lencioni’s Death by Meeting and gathered some insight. Just like when I began to study testing and was able to classify my testing knowledge with more widely understood patterns and concepts, Lencioni succinctly described why some meetings worked and some didn’t, and I was able to relate that learning to my own experiences. I learned why some (but not all) meetings need agendas, and why conflict is necessary for essential brainstorming. I haven’t perfected every meeting I attend (or run), but the concepts from that book remain in my conscious. I’ve become sort of a sucker for Lencioni’s writings since then and think all of his stories are fascinating insights into team growth and leadership.

I got a bit of a boost a few weeks ago when I read Read This Before Our Next Meeting by Al Pittampalli. This book is a manifesto on how to run a good meeting – and more importantly on why bad meetings are killing us. Having worked in organizations where status and informational meetings are abundant makes the points in this book ring home, and remind me why we can, and must do better about how we hold meetings and make decisions.

I love a good meeting, and after reading Pittampalli’s book, reflecting on Lencioni’s book, and recalling my own meeting experiences, I’m reminded of why. Brainstorming, collaboration, and a level of conflict all contribute to a meeting where the thoughts of the many are far better than the sum of their parts. These are the meetings that energize me.

I’m also reinvigorated to eliminate the bad meetings from my calendar. Meetings where goal is consensus or shoving information down attendees throats don’t belong in successful organizations. We can do better, and I’m inspired to try.

Similar Posts

  • More on the Coding Tester

    Every day, it seems, I come across an article, a forum posting, a blog, or a tweet bemoaning the end-of-test-as-we-know-it because some company has hired / is hiring people with programming knowledge to become testers. I’ve written about coding-testers (here, and in other posts) before (as have many others that I’m too lazy to look…

  • Presentation Maturity

    Test conference season is upon us, and so begins the onslaught of “slides” from  powerpoint / keynote / (google docs presentation app whatever-it’s-called). I have seen hundreds of presentations on a wide variety of subjects over the years and thought I’d share what I know about what a presentation tells you about the presenter. The…

  • Fog Creek Fun

    Whaaa…? Two posts on automation in one week? Normally, I’d refrain, but for those who missed it on twitter, I recorded an interview with Fog Creek last week on the Abuse and Misuse of Test Automation. It’s short and sweet (and that includes my umms and awws).

  • |

    Five for Friday – January 26, 2018

    Quote I’m pondering “Asking “Why?” can lead to understanding. Asking “Why not?” can lead to breakthroughs.” – Daniel Pink I’m a big Dan Pink fan (my favorite is still “A Whole New Mind“), but I’m currently reading “When“ As much as I rant about the pitfalls of UI / Web automation, I don’t discount it…

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.