Comment by dahart

Okay, but only if this is balanced by accounting for the cost of IC engineers’ solo time too. Sometimes it does feel like meetings waste a lot of time/money quickly, but I’ve also watched people burn money by not having meetings and going the wrong direction for weeks, watched teams over-engineer the crap out of features nobody asked for, watched people tear out huge swaths of working code they just didn’t like and waste years re-implementing it, only to have it be buggier for a few years and then end up with basic design flaws, sometimes the same ones as before, and sometimes new ones…

A blanket force to reduce meetings isn’t quite the right incentive; we need incentives to have the right amount of meetings and to make them more effective. The right amount of meetings is probably always going to be more than ICs want, and less than managers want. But if you have any reliable ways to make that happen, to keep meetings effective, that’s gold. Charge money for that knowledge and consult, or become a CEO, either way you’ll get rich!