Vancouver Hack Space

User Tools

Site Tools

You are here: start » tutorials » quadworkshoppostmortem
tutorials:quadworkshoppostmortem

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
tutorials:quadworkshoppostmortem [2015/12/12 14:31] – external edit 127.0.0.1tutorials:quadworkshoppostmortem [2019/04/05 19:50] (current) – 00739
Line 1: Line 1:
 +====== Quad Workshop Postmortem ======
 +
 “I” is actions from or for Jon G. “We” refers to the participants in the build workshop. “VHS should” are my recommendations for what the membership of the space can do to help and improve future workshops. “I” is actions from or for Jon G. “We” refers to the participants in the build workshop. “VHS should” are my recommendations for what the membership of the space can do to help and improve future workshops.
  
Line 23: Line 25:
  
   * We took signups by having people paypall us the money. this worked reasonably well, having an in person signup & payment method (ex: Square) may have helped. I don’t feel that skipping [[http://www.eventbrite.ca/|eventbrite]] was a mistake, given the additional cost. We did not have a method to limit registration, as we had a great deal of flexibility for group size. Date choice was run as a [[http://www.doodle.com/|doodle]], with a second doodle with capped attendance used for attendees to select which they would attend, while capping numbers.   * We took signups by having people paypall us the money. this worked reasonably well, having an in person signup & payment method (ex: Square) may have helped. I don’t feel that skipping [[http://www.eventbrite.ca/|eventbrite]] was a mistake, given the additional cost. We did not have a method to limit registration, as we had a great deal of flexibility for group size. Date choice was run as a [[http://www.doodle.com/|doodle]], with a second doodle with capped attendance used for attendees to select which they would attend, while capping numbers.
 +
   * Providing updates via a running email thread to attendees worked, but it would have helped to have a form to collect non-paypal email addresses, and other contact info with the payment.    * Providing updates via a running email thread to attendees worked, but it would have helped to have a form to collect non-paypal email addresses, and other contact info with the payment. 
 +
   * Having a full prototype kit gave us an opportunity to troubleshoot issues before the workshop. For the most part this wasn’t visible to the participants, but a few issues took several hours to debug before hand.   * Having a full prototype kit gave us an opportunity to troubleshoot issues before the workshop. For the most part this wasn’t visible to the participants, but a few issues took several hours to debug before hand.
 +
   * As a time guideline, what took us 1 hour to assemble once we had done it once took the workshop roughly 3 hours. Writing the documentation took around 6 hours (see below for recommendations - I'd suggest spending MORE time on documentation).   * As a time guideline, what took us 1 hour to assemble once we had done it once took the workshop roughly 3 hours. Writing the documentation took around 6 hours (see below for recommendations - I'd suggest spending MORE time on documentation).
 +
   * Running the workshops as “here’s the instructions, I’ll be wandering around to check and help, ask if you have any questions” worked well, as long as the instructions were reasonably well prepared.    * Running the workshops as “here’s the instructions, I’ll be wandering around to check and help, ask if you have any questions” worked well, as long as the instructions were reasonably well prepared. 
 +
   * ‘voluntelling’ participants to help one another out with steps that they had completed was also effective.   * ‘voluntelling’ participants to help one another out with steps that they had completed was also effective.
 +
   * Having experienced help around was invaluable for the bigger build day -    * Having experienced help around was invaluable for the bigger build day - 
 +
   * Progress speed during the workshop will likely vary wildly, especially for participants with kids along. Trying to encourage ‘buddying’ them up with a member you know to be technically adept will help keep progress in the same band.   * Progress speed during the workshop will likely vary wildly, especially for participants with kids along. Trying to encourage ‘buddying’ them up with a member you know to be technically adept will help keep progress in the same band.
 +
   * Limiting attendance at a day to 10 ± 1 was a good level for a kit of this size, in the bunkers amount of space. Increased attendance would have required pushing people to the perimeter tables, and made it harder to keep track of.    * Limiting attendance at a day to 10 ± 1 was a good level for a kit of this size, in the bunkers amount of space. Increased attendance would have required pushing people to the perimeter tables, and made it harder to keep track of. 
 +
   * Shipping times and parcel tracking drove my stress rates up, ultimately for no reason. A spreadsheet tracking what was in each shipment, what had arrived, and what was remaining was very helpful, and I didn't make any ordering errors.   * Shipping times and parcel tracking drove my stress rates up, ultimately for no reason. A spreadsheet tracking what was in each shipment, what had arrived, and what was remaining was very helpful, and I didn't make any ordering errors.
  
tutorials/quadworkshoppostmortem.txt · Last modified: 2019/04/05 19:50 by 00739
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki