codeformilwaukee / hack-night-planning

Hack Night Planning Repository
0 stars 1 forks source link

Log Attendance & improve communications from Hack Nights #11

Open BarkleyBG opened 5 years ago

BarkleyBG commented 5 years ago

update We are still interested in: "2. keep in touch with interested community members."

It would be good to keep in touch with what projects people are working on


original We'd like to

  1. track attendance
  2. keep in touch with interested community members.

potential strategy

  1. One-question google poll to grab email from every attendee
  2. Short google poll to ask “what did you work on” “did it go well” “other feedback” after a hack night
    • open it up in the last 30 mins of hack night
    • be sure to share it out during closing remarks
    • Take all email addresses that haven’t responded and prompt them with an email within 24-48 hours linking to that survey
  3. Get info on new members
    • For all new email addresses that we don’t recognize, ask for name / pronouns / basic information in short follow-up google poll

long-term strategies

We can also think about in-depth longitudinal surveys once we nail down the basics. [ edit ] - we are moving this last part to #15

BarkleyBG commented 5 years ago

Erin and Brian are assigned this

BarkleyBG commented 5 years ago

@erinmagennis maybe we should ask the CFA brigades to see if anybody has a better idea than we have?

BarkleyBG commented 5 years ago

Andrew said that the Discourse site is where CfA brigades talk about this kind of stuff.

BarkleyBG commented 5 years ago

@erinmagennis

BarkleyBG commented 5 years ago

Moving to November so that we can attempt to tackle the goal: "2. keep in touch with interested community members."