I&#x27;ve been to hundreds of meetings and I can count on both hands the meetings that were actually important for the team assembled.<p>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.<p>The problem with &quot;meeting culture&quot; is completely unrelated to the problem addressed in the article, except to say that the problem addressed in the article wouldn&#x27;t be such a problem if the &quot;meeting culture&quot; problem were addressed instead.<p>Don&#x27;t call a meeting if you don&#x27;t <i>really</i> 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 &quot;Agile&quot; development &quot;stand-up&quot; meetings. With the correct tools they become completely unnecessary, and only serve to hinder (or artificially accelerate) development milestones.<p>I&#x27;m sure that there are <i>some</i> teams out there who do this correctly, but I haven&#x27;t been lucky enough to come across any yet.