How to make Meetings Successful and Useful

Tue, Jan 24, 2006

I knew that the meetings that we had are all successful ones with to-the-point discussions, coming out with objectives which we know what to do, when to do and who will do. So, I was always on the look-out for how to express that all Meetings are not that harmful.

I just saw "37Signal (37Signal)": come up with almost all the points which helped me gather up my semi-formed points that was in my mind.

Here are the points verbattim from "37Signal (37Signal)":;

# Begin with a specific problem. Meetings are wild horses that always try to run off course. Yoke the meeting to a specific problem. ǃ?Improve the flow on the New Entry pageǃ? is better than ǃ?Talk about New Entry page.ǃ?
# Meet on site. Meet at the site of the problem instead of the conference room. Get in front of the code, in front of the UI, and talk about it together. Point to real things and suggest real changes.
3 End with a solution and responsible parties. Your next action will be concrete if the problem is solved. YouǃÙre ready to go when you know what will be done and by whom. If you canǃÙt find a concrete solution, end the meeting and come back when you understand the problem better.
# Celebrate, shut up, and do something. Celebrate the solution. ItǃÙs good when heads come together and solve a problem. ItǃÙs great when they get back to work and build the damn thing.

Reference Article;
"Meetings considered harmful (Meetings considered harmful)":

Via: "37Signals (37Signals)":