meetings_how_to
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
meetings_how_to [2020-06-01 15:11] – [Avoiding Bikeshedding] tkerby | meetings_how_to [2020-06-08 01:05] – [Avoiding Bikeshedding] river | ||
---|---|---|---|
Line 24: | Line 24: | ||
* Meetings should have a purpose. | * Meetings should have a purpose. | ||
* Send out an agenda ahead of time, so that the purpose of the meeting is clear to all attendees and they can come prepared if necessary. Ideally this should include a quick background paragraph/ | * Send out an agenda ahead of time, so that the purpose of the meeting is clear to all attendees and they can come prepared if necessary. Ideally this should include a quick background paragraph/ | ||
- | * After the meeting has finished, create | + | * Create |
* Discuss this action list at the start of the next meeting if there is one. | * Discuss this action list at the start of the next meeting if there is one. | ||
* Agree on a time limit in advance (eg an hour max) and try and stick to it: Better to have two shorter meetings with fresh people than one enormous mega-meeting that burns everyone out. | * Agree on a time limit in advance (eg an hour max) and try and stick to it: Better to have two shorter meetings with fresh people than one enormous mega-meeting that burns everyone out. | ||
Line 38: | Line 38: | ||
===== Avoiding Bikeshedding ===== | ===== Avoiding Bikeshedding ===== | ||
Some general points on how to collaboratively solve problems. Key thing is to consider the problem fully before we all jump in with possible solutions. | Some general points on how to collaboratively solve problems. Key thing is to consider the problem fully before we all jump in with possible solutions. | ||
+ | |||
+ | See also: [[bikeshed|]] | ||
=== Think Problems === | === Think Problems === |
meetings_how_to.txt · Last modified: 2020-08-10 09:26 by river