Skip to main content


I've always, and I do mean always, had an aversion to meetings.  If we don't have a clear task to accomplish or To-Do items coming out of the discussion they are a waste of time, since it's likely a discussion best convened between two or three people, not all meeting attendees.

Then I came across Tony Morgan's review of The Four Obsessions of an Extraordinary Executive by Patrick Lencioni.  One of the quotes he mentions is this.

For cohesive teams, meetings are compelling and vital. They are forums for asking difficult questions, challenging one another's ideas, and ultimately arriving at decisions that everyone agrees to support and adhere to, in the best interests of the company.

I can't tell you how much this resonated with me.

Over the past year I worked on a project team of four people.  I can say, without a doubt, that this was the best team I've ever worked with in my working career.  We could meet for 2 to 4 hours straight, work together or on our own, joke about how I thought the vet in Sesame Street was cute and they found her and said she looks like a witch.

Through it all though we got things done.

This quote put into words incredibly well the feelings I still have remembering that team experience.

Any teams you lead, and as I begin to take on the leadership of Eucharistic Ministers, Acolytes and such in my church, I plan on making this a reality.  If our meetings are dull, slow or passionless than we'll be working on some serious friendship building.

I definitely have this book on my Amazon Wishlist.

What meetings and teams have you worked with that you'll never forget?  What made them so memorable?



Popular posts from this blog

Advantages and Disadvantages of Using Microsoft Access

I've answered this question in some form or another far more times than I care to count.  Most often it's a question of "why do I need a fancy Web application when I can just build this myself in two days in Access.  I mean, the data's already in Excel."  So I figured I'd post out what I threw together, I know I've missed some points. Overview Microsoft Access is an ideal solution for relatively small datasets and a limited number of users. From the Microsoft Web site: “As a desktop database, Access is well suited for small, departmental applications. These applications may start as one user’s project. For example, an employee realizes that productivity can be increased if a paper-based process is automated with an Access application. Other users in the department recognize that they can take advantage of the application if additional features are added. As more features are added, more employees run the application. As time goes by, more and more Access

Beryllium Spheres

I'm sitting here at home watching The Shadow , easily one of the best movies made based on one of the best old time radio shows.  I hadn't picked up on this earlier, but the weapon used to destroy the city is none other than the same power source used to power the NSEA Protector in Galaxy Quest . I never knew Beryllium was so cool.  Now I want a sphere of my own. Anyone know of other places Beryllium Spheres are mentioned? Peace, +Tom

Red-Gate SQL Compare

Every now and then I come across a program that becomes so ingrained in my daily work that I hardly know how I'd get by without it.  I'll probably break down a couple over the next few days, but for database work, I have never found anything as good as Red Gate's SQL Compare and SQL Data Compare .  Essentially these tools let you compare two SQL Server databases (all objects, users, permissions, functions, diagrams, anything) and update changes to whichever database you want.  This is amazingly useful for deploying database changes to a test or production environment (do it to production with ridiculous care, even though it will generate a SQL Script for you and run all updates in one transaction), and making sure everything is synchronized. For releases we can just generate the compare script, confirm that the changes match the updates we want to go out, and store it all in one place with the release details.  This is true for both the structure and the data, to