Hacker News new | past | comments | ask | show | jobs | submit login

That's not a free form discussion. That's team status updates which you can do as an agenda item. In the event that they're of interest to people there those people can get together separately and discuss them.

But if they're not an agenda item they shouldn't be discussed because it's not that meeting.

The point is to allow people to make their own decision on whether they attend by giving them useful information on what will be discussed.

Just because that's what you want to do, doesn't mean that's what some particular meeting you happen to be in should be about.




Every meaningful point might not be on the agenda, and refusing to have a pertinent discussion because it was not on the agenda will lead to a second or third meeting, who knows when, with revised agendas that still might no be good enough. That's largely inefficient and a time loss for everyone.

Of course if nobody cares about some tangent point, it should be stopped on the spot. If a discussion appears while some of the stakeholders are missing, it might be postponed as well, but if it's not the case there's no reason no to go on and discuss it, just because it's not on the agenda.


>Every meaningful point might not be on the agenda, and refusing to have a pertinent discussion because it was not on the agenda will lead to a second or third meeting, who knows when, with revised agendas that still might no be good enough. That's largely inefficient and a time loss for everyone.

But this is exactly how it's supposed to work. It's efficient to table side discussions that don't apply to everyone. Otherwise, you're just wasting a subset of the participants' time.

A proper agenda should contain everything that absolutely needs to be talked about at that time. That is the focus of the meeting. If additional discussions are spawned that aren't covered by it, they should be taken offline, either with an additional meeting, or with an informal discussion after.


I guess your premise is that someone did extensive research before building the meeting agenda, communication by mail and other means allowed everyone to do one's homework, and everyone actually did it, so the meeting is really just to seal the consensus.

I agree in this kind of situation, unexpected items are of limited scope, shouldn't affect the meeting agenda, and can be dealt at other time.

Now, this would be more the exception than the rule, at least in my experience. And if you can reach this point in your organization, I think you can get rid of the meeting altogether, and just validate the different points by mail or group chat.


It's not if no-one cares, it's if not EVERYONE cares.

If you've got 10 people in the meeting and 6 people start discussing something, you've got 4 people who are having their time wasted and were given no choice in the matter.


Perhaps it has to do with the attitude towards meetings. If someone is wasting his/her time in a meeting, he/her should excuse him/herself and leave.

It's the same pattern as when you need to be in a meeting about a specific point, but not attend all the other points. You ask to have the stuff you care about come first and you can leave it after. If some unexpected things needs your input, you'll be called in anyway.


I'm not sure if that's as efficient as sticking to the prescribed agenda, and having the non-agenda stuff taken offline / discussed after.

You don't have to schedule an entirely different meeting room to talk about it - more often than not at my work, the people who want to discuss the unexpected point just stay after the original meeting has ended to discuss it.

To everyone who was there for the agenda, the meeting is effectively over - for the others, you could say the meeting continues on with the unexpected topic.

The important part is that everyone meets for as short as is needed - they don't have to keep running in and out of meetings to see if things are relevant, or stay and listen to things that don't matter to them.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: