4 ms·
The other problem is that a 2 hour team meeting takes 2 hours for the manager 2*n hours for the team, even before considering the disruption.
by tybris 17y ago
The other problem is that a 2 hour team meeting takes 2 hours for the manager 2*n hours for the team, even before considering the disruption.
- req2 17y agoThis probably just means the meeting is too large. I'd recommend cutting n in half and trying again. From a smaller n, I'd expect not only a shorter meeting, but also a greater per person output.
- kd5bjo 17y agoThis is why our team meetings are only 15 minutes long, and usually shorter. Any discussion or questions get done offline by only those people that are directly affected.
- pg 17y agoOne way to prevent 2 hour meetings is not to let people sit down. We had an unofficial rule to that effect at Viaweb. I remember once passing by a room and noticing a bunch of people sitting around a table. I must have raised an eyebrow or something, because one of them jumped up and said "We're not having a meeting! We were just talking."
- projectileboy 17y agoOne of the better practices from the world of "agile" software methodology is dropping the team's weekly status meeting and instead having morning "stand-up meetings" every day. Same thing - you don't let people sit down. It completely changes the tone of the conversations, because no one wants to stand in a meeting room for longer than 10 or 15 minutes.
- abalashov 17y agoNot to mention that when the status meetings - or, even more significantly, other kinds of meetings (design meetings, planning meetings, etc.) - are spaced that far apart temporally, every meeting just becomes mostly a rehash of everything forgotten since the last meeting. The "agile" folks have the additional insight that reporting early and often is good.
- deleted 17y ago[deleted]