Difference between revisions of "Team:Infodesk/Planning"
From SHA2017
(more elaborate list of tasks than what was at the "does" section, plus rough planning) |
(+resources (from Team:Infodesk)) |
||
Line 1: | Line 1: | ||
− | + | ==Things to do (and when)== | |
− | ==Before Save the Date== | + | ===Before Save the Date=== |
− | * Initial website (wiki) (with: communication; design) | + | * Initial website (wiki) (with: communication; design; sysop) |
+ | ** | ||
* team mailinglist | * team mailinglist | ||
* team roles, tasks, and planning | * team roles, tasks, and planning | ||
Line 10: | Line 11: | ||
** responding to replies on social media | ** responding to replies on social media | ||
* Responding to 'outside' questions (mail, social media): answering known questions, redirecting when needed | * Responding to 'outside' questions (mail, social media): answering known questions, redirecting when needed | ||
− | |||
* [https://files.sha2017.org/ team filestorage] | * [https://files.sha2017.org/ team filestorage] | ||
* wiki information architecture (with infra, communication, ?) | * wiki information architecture (with infra, communication, ?) | ||
− | ==Before ticketsales (2017-01-01?)== | + | ===Before ticketsales (2017-01-01?)=== |
* Wiki: | * Wiki: | ||
** FAQ | ** FAQ | ||
Line 19: | Line 19: | ||
** Information about volunteering | ** Information about volunteering | ||
** Information on how to get there | ** Information on how to get there | ||
+ | ** Information for other teams: how we communicate, what infrastructure we use | ||
* Social media | * Social media | ||
** 'branding' (logo etc.) | ** 'branding' (logo etc.) | ||
Line 28: | Line 29: | ||
* wiki usage tracking (Piwik, Google search console) | * wiki usage tracking (Piwik, Google search console) | ||
− | ==Before event== | + | ===Before event=== |
* Booklets (with communication; design) | * Booklets (with communication; design) | ||
* Physical infodesk | * Physical infodesk | ||
+ | ** probably one 'island' together with a front-office for Logistics, NOC, POC | ||
* Full FAQ | * Full FAQ | ||
− | ==At event== | + | ===At event=== |
+ | * Getting people where they need to be | ||
** Routing visitors to Tickets | ** Routing visitors to Tickets | ||
** Routing volunteers to Volunteers | ** Routing volunteers to Volunteers | ||
Line 40: | Line 43: | ||
* Routing people, welcoming them, handing out booklets (with Ticket?) | * Routing people, welcoming them, handing out booklets (with Ticket?) | ||
* trying to accommodate simple needs (who accommodates more complex needs?) | * trying to accommodate simple needs (who accommodates more complex needs?) | ||
+ | ==Resources== | ||
+ | ===Humans=== | ||
+ | * 25hr/month for responding to questions (june 2016-februari 2017) | ||
+ | * 45hr/month for responding to even more questions (march 2017 - august 2017) | ||
+ | * 15hr/month for planning the event | ||
+ | * 15hr/month for collecting information from other teams | ||
+ | * 60hr of beautiful design (perhaps by someone from [[Team:DECO]])? | ||
+ | * 50 shifts of 4 hours during the week itself (assuming build-up needs one spot during the day) | ||
+ | |||
+ | ===Desks=== | ||
+ | * [[Resource::1 person desk at entrance]] - or instructing the ticketing fokes how to help people on their way | ||
+ | * [[Resource::3 person desk at infodesk]] - probably near NOC helpdesk | ||
+ | * BYOD for our hacker-receptionists | ||
+ | * [[Resource::Office (or at least a large locker) for materials and lost-and-found]] | ||
+ | ===Materials=== | ||
+ | * [[Resource::Booklets (€2000 inc VAT)]]{{Deadline | ||
+ | |Date=2016/04/30 | ||
+ | |Text=First plan - mainly with scope. | ||
+ | }} |
Revision as of 22:56, 6 June 2016
Contents
Things to do (and when)
Before Save the Date
- Initial website (wiki) (with: communication; design; sysop)
- team mailinglist
- team roles, tasks, and planning
- Social media:
- Claiming channels
- Redirecting to wiki
- sporadic announcement
- responding to replies on social media
- Responding to 'outside' questions (mail, social media): answering known questions, redirecting when needed
- team filestorage
- wiki information architecture (with infra, communication, ?)
Before ticketsales (2017-01-01?)
- Wiki:
- FAQ
- Dates
- Information about volunteering
- Information on how to get there
- Information for other teams: how we communicate, what infrastructure we use
- Social media
- 'branding' (logo etc.)
- policy (with communication)
- helpdesk ticketing system (Linux trackers)
- Knowledge system (FAQ, including standard customisable replies to frequently sent requests like visa)
- Escalation system
- team IRC channel
- wiki usage tracking (Piwik, Google search console)
Before event
- Booklets (with communication; design)
- Physical infodesk
- probably one 'island' together with a front-office for Logistics, NOC, POC
- Full FAQ
At event
- Getting people where they need to be
- Routing visitors to Tickets
- Routing volunteers to Volunteers
- Routing press to PR/communications
- Assemble a knowledgebase (based on questions and presumed questions)Event:
- Routing people, welcoming them, handing out booklets (with Ticket?)
- trying to accommodate simple needs (who accommodates more complex needs?)
Resources
Humans
- 25hr/month for responding to questions (june 2016-februari 2017)
- 45hr/month for responding to even more questions (march 2017 - august 2017)
- 15hr/month for planning the event
- 15hr/month for collecting information from other teams
- 60hr of beautiful design (perhaps by someone from Team:DECO)?
- 50 shifts of 4 hours during the week itself (assuming build-up needs one spot during the day)
Desks
- 1 person desk at entrance - or instructing the ticketing fokes how to help people on their way
- 3 person desk at infodesk - probably near NOC helpdesk
- BYOD for our hacker-receptionists
- Office (or at least a large locker) for materials and lost-and-found
Materials
2016/04/30 - First plan - mainly with scope.