I've been to hundreds of meetings and I can count on both hands the meetings that were actually important for the team assembled. I agree with the spirit of th

I've been to hundreds of meetings and I can count on both hands the meetings that were actually important for the team assembled. I agree with the spirit of the article, but the problem remains that most meetings are, at best, fora for discussing things that could be discussed in a more decentralized manner, and, at worst, complete wastes of time where one person is flexing control muscle in order to inflate their self-importance. The problem with "meeting culture" is completely unrelated to the problem addressed in the article, except to say that the problem addressed in the article wouldn't be such a problem if the "meeting culture" problem were addressed instead. Don't call a meeting if you don't really need one. Hint: most projects really only need 2 meetings: one at the beginning, and one at the end. Everything in-between can be dealt with in a much more streamlined manner. This, unfortunately, includes "Agile" development "stand-up" meetings. With the correct tools they become completely unnecessary, and only serve to hinder (or artificially accelerate) development milestones. I'm sure that there are some teams out there who do this correctly, but I haven't been lucky enough to come across any yet.