Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service Hours: BWS Service Awareness event prep and retrospective notes #149

Closed
8 tasks done
Rabia2219 opened this issue Mar 14, 2022 · 3 comments
Closed
8 tasks done

Comments

@Rabia2219
Copy link
Member

Rabia2219 commented Mar 14, 2022

Overview

We are partnering with BWS to onboard volunteers for community service hours and we need to plan our pitch, create presentation materials, assign speakers and attendees, and fill out all the paperwork sent by BWS by Monday, March 14th 12 pm PDT. BWS Service Awareness Day is scheduled for Tuesday, March 15th 2022 at 9 am PDT.

Action Items

  • Plan our pitch
  • Create presentation
  • Figure out who will speak
  • Create script for presentation
  • Assign guest attendees
  • Ask for Zoom link for guest attendees
  • Fill out paperwork
  • Send paperwork and presentation slides to BWS by 12 pm on Monday, March 14th 2022

Resources/Instructions

Folders:

*Note: Housed on new Service Hours Drive

Drafts:

Resources sent by BWS:

@Rabia2219 Rabia2219 added this to the 04 - Org Requirements milestone Mar 14, 2022
@Rabia2219 Rabia2219 changed the title Prepare for community service event Prepare for BWS Service Awareness event Mar 14, 2022
@Rabia2219
Copy link
Member Author

Grace needs a guest Zoom link to attend. Will wait for Jhamasa to send the new link to figure out if we need to ask for a Guest link or just forward the new link to Grace.

@Rabia2219
Copy link
Member Author

@ExperimentsInHonesty if you have any feedback after the event...please comment here and then the issue can be closed. Thanks

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Mar 16, 2022

Notes from the event

Items can be approved

  • Form did not have workforce development in it, had to ask for it be added (was added promptly).
  • 2 presenters, at the end, were cut for time
  • BWS team, If they had orgs slide decks, cut them themselves instead of asking the org to cut (one of the orgs got pretty upset)
  • Original time invitation was 15 min, which got change to 5 min on Friday morning the week before, to 2 min the night before (8:30 pm)
  • The run through that was scheduled for day of 8:45am (15 min prior) was not available
  • No panelists could rename themselves because it was locked down (must be set in zoom general settings before meeting).
  • Which required the one Host to do all the renaming. Which led to people duplicating their asks if there were multiple people on a team, trying to watch out for their team members
  • Assumed people understood that a panelist link should not be shared and didn't ask us to provide a list of all the people who would attend. They could have provided the guest link for non-speaking attendees.
  • zoom and calendar links were not setup early enough in the process
  • If the students had experience with the non-profit, they were more effusive about their intros (minor issue)
  • The participants were not told that their mission statement would be the introduction
  • When Bonnie screen shared, she forgot to unmute for 5 seconds.

What went well

  • The students read the intros well
  • We were in good company (other impressive non-profits)
  • It moved quickly, it was exciting and there were no draggy moments
  • The technical glitches were pretty much invisible to the attendees
  • Saw examples of other good presentations

Suggestions for improvement

  • Add a timer to the screen
  • Website or slide deck that guides non-profits through the program
  • DocuSign for agreements
  • Allow for participants to add their slides to a common google slide deck
  • timeline of dates by which prep items have to be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants