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

Keep it short and to the point.

Have an agenda. Allow people to edit the agenda before-hand (a wiki is a good place for this).

Make sure actions come out of the meeting, so the time isn't wasted.




These are great suggestions! We use a private wiki that anyone on the team can edit: it saves a lot of time versus E-mail. We use the same page for both the agenda, the minutes, and a decision record (you can always re-factor or start pages to address ongoing issues/concerns, but there should be a single page for the meeting that links to related content). Since you are geographically separated I would use an IM session (e.g skype chat, google chat, AOL, Yahoo) that lets everyone take contemporaneous notes and pass links/URLs and raise their hand to speak. Take a few minutes after the meeting is over to clean up the transcript and paste it into the meeting wiki page, it doesn't have to be pretty, but comprehensible a few months from now (and everyone else can continue to refine/edit etc..). Key thing is to get decisions documented, the context that led to them, and for major decisions a brief prediction on expected outcomes and when and how to re-evaluate.


The other good thing about wiki vs email is that you have a permanent record of everything that has ever happened. E-mails get lost, and new employees cannot browse the old content


Ditto on the agenda-in-wiki, with the addition that if it's not on the agenda it has to wait until next week. This keeps meetings from wandering from topic to topic, usually on topics that someone just thought of that don't really need to be discussed in a group.




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

Search: