Organizations have need of ceremony. It's perfectly reasonable to call a meeting with a purpose that is strictly ceremonial, particularly at project milestones, when new people come on board, or for celebrating good work by the group. Such meetings do not waste anyone's time. They fulfill real needs for appreciation. They confirm group membership - it's importance and its value. Ceremonial meetings that only celebrate the bossness of the boss, however, are a waste.
When people's time is wasted in unnecessary meetings ar by early overstaffing, they'll know it. They'll be frustrated and they'll know why. If there is enough of such waste, they'll probably let you know about it, too. So these problems, though serious, are at least not invisible. There, however, one way that people's time gets wasted that is likely to go unnoticed, and thus uncorrected. This has to do with time fragmentation...
Fragmentation is particulary injurious when two of the tasks involve qualitively different kinds of work habits. Thus, the mix of a design tasks (which requires lots of immersion time, relative quiet, and quality interaction time with a small group) with a telephone support task (which requires instant interruptibility, constant availability, quick change of focus) is sure to make progress on the more think-intensive of these tasks virtually impossible.
Sometimes as a manager, it’s your job to do the grubby, ugly stuff so the sales guys can sell and the developers can develop.