Staff inservice time - Revision history

Dheiber at 18:59, 10 February 2012

2012-02-10T18:59:35Z

Scellef: /* Publicity */ Marked completed

2012-02-10T17:14:21Z

Publicity: Marked completed

Ideath: /* Activities */

2012-01-11T18:45:58Z

Activities

Ideath at 07:14, 7 January 2012

2012-01-07T07:14:29Z

Ideath: /* Activities */

2012-01-07T05:59:46Z

Activities

Ideath: /* =Timing */

2011-12-29T20:59:59Z

=Timing

Ideath: getting down some basic questions, a first draft

2011-12-29T20:58:50Z

getting down some basic questions, a first draft

New page

This page is a workspace for the committee appointed by the board to explore and plan logistics for an in-service period in early 2012. The goal is to close down most operations of Free Geek during part of the slowest time of the year in order to provide time for the staff to catch up on admin work, hold meetings, provide trainings, and otherwise regroup.

==The Committee==
The committee consists of two board members (laurel and Kathey), the collective-board liaison (Paul), and the non-collective-board liaison (vagrant). The idea of the inservice time was approved by the board, and this group was set "to figure out how many days, what will be done, budget impact and operationally how it is to be done." [http://lists.freegeek.org/pipermail/board-discuss/2011-December/000046.html Board minutes 12/11] Basically, we need to generate a proposal for the board for the specifics and have it ready to roll out ASAP.

==Logistics and cost==
Some of these are factual questions that can be answered via the database (marked with [DB]) or require operations knowledge. The question of how long is needed may require more conferring. The minutes from the board meeting show a rejection of January that i ([[User:Ideath|Ideath]]) do not recall, but at this point the end of January is probably the closest we could do and have sufficient notice.
===Timing==
''When'' is the slow time of year?
* volunteers [DB]
* donations [DB]
* store [DB]

How much time do we need?

If receiving and store were open half-day each day
* ''how many people'' would it take to staff them?
* which half-day would be better? [DB]

===Cost===
What is the average income in donations and sales from the time proposed? [DB]

What is the total staffing expense if all staff work their usual hours?

Would some staff welcome the option to work fewer hours if they don't have much admin work?

==Activities==
* '''Admin time''' (basically all non-meeting time, though if the front-end operations are going to be open staff can rotate through)
* '''All-staff meeting'''
** how long?
** who builds the agenda?
** outside facilitator?
** set goals for the meeting beforehand
* '''Non-collective staff meeting'''
** needs facilitator and agenda, should precede all-staff
* '''Departmental meetings'''
** if we hold these, they should be staggered due to personnel overlap
* '''Staff trainings'''
** consensus process? (someone on-staff? non-collective, perhaps?)
** data security @ FG (database and donated materials)?
** health and safety?
** FG history?
* '''Physical plant/organization/network work'''
** get volunteers involved

==Publicity==
These can be prepared as soon as we have the date and other relevant details, and should be ready to go.
* Signs for windows/bulletin boards
* Get message out to all staff
* Email to volunteer lists (which?)
* Note at scheduling desk (paper slip?)
* Voicemail message
* Website
* Newsletter? will there be one before then?

← Older revision		Revision as of 18:59, 10 February 2012
Line 41:		Line 41:
	* Website -- DONE		* Website -- DONE
	* Newsletter? will there be one before then? -- DONE		* Newsletter? will there be one before then? -- DONE
		+
		+	[[Category:Inservice Trainings]]

@@ Line 34: / Line 34: @@
 ==Publicity==
 These can be prepared as soon as we have the date and other relevant details, and should be ready to go.
-* Signs for windows/bulletin boards
+* Signs for windows/bulletin boards -- DONE
-* Get message out to all staff
+* Get message out to all staff -- DONE
 * Email to volunteer lists (which?)
 * Note at scheduling desk (paper slip?)
-* Voicemail message
+* Voicemail message -- DONE
-* Website
+* Website -- DONE
-* Newsletter? will there be one before then?
+* Newsletter? will there be one before then? -- DONE

@@ Line 30: / Line 30: @@
 ** if we hold these, they should be staggered due to personnel overlap
 * '''Staff trainings'''
-** to be planned by staff. orientation to process, structure, procedures and culture for new and not-so-new folks.
+** see [[Winter/Spring 2012 Inservice Trainings]]
 ==Publicity==

@@ Line 1: / Line 1: @@
 This page is a workspace for the committee appointed by the board to explore and plan logistics for an in-service period in early 2012. The goal is to close down most operations of Free Geek during part of the slowest time of the year in order to provide time for the staff to catch up on admin work, hold meetings, provide trainings, and otherwise regroup.
-==The Committee==
+==The committee==
-The committee consists of two board members (laurel and Kathey), the collective-board liaison (Paul), and the non-collective-board liaison (vagrant). The idea of the inservice time was approved by the board, and this group was set "to figure out how many days, what will be done, budget impact and operationally how it is to be done." [http://lists.freegeek.org/pipermail/board-discuss/2011-December/000046.html Board minutes 12/11] Basically, we need to generate a proposal for the board for the specifics and have it ready to roll out ASAP.
+The committee charged with coming up with a proposal consists of two board members (laurel and Kathey), the collective-board liaison (Paul), and the non-collective-board liaison (vagrant). The idea of the inservice time was approved by the board, and this group was set "to figure out how many days, what will be done, budget impact and operationally how it is to be done." [http://lists.freegeek.org/pipermail/board-discuss/2011-December/000046.html Board minutes 12/11] Basically, we need to generate a proposal for the board for the specifics and have it ready to roll out ASAP.
 ==Logistics and cost==
-Some of these are factual questions that can be answered via the database (marked with [DB]) or require operations knowledge. The question of how long is needed may require more conferring. The minutes from the board meeting show a rejection of January that i ([[User:Ideath|Ideath]]) do not recall, but at this point the end of January is probably the closest we could do and have sufficient notice.
+Some of these are factual questions that can be answered via the database (marked with [DB]) or require operations knowledge.
 ===Timing===
-''When'' is the slow time of year?
+Our preferred model is currently Tuesdays in February
-* volunteers [DB]
+* this makes four days
-* donations [DB]
+* to customers and donors, it only ends up being one day inconvenience instead of potentially a week
-* store [DB]
+* it's easy to remember and explain
+* there would be time between inservice days for people to prepare and process things
 ===Cost===
@@ Line 22: / Line 17: @@
 What is the total staffing expense if all staff work their usual hours?
 ==Activities==
 * '''Admin time''' (basically all non-meeting time, though if the front-end operations are going to be open staff can rotate through)
-* '''All-staff meeting'''
+* '''All-staff meeting''' Potentially Feb 28.
-** how long?
+** how long? (All day, half about communication, half about strategy?)
 ** who builds the agenda?
-** outside facilitator? ''checking for Tasha's availability''
+** outside facilitator? Tasha Harmon, who facilitated the THM, may be available. Her fee is sliding scale $80 - 125/hr and needs to include at least 2 hours agenda prep and 1 hour debrief. I ([[User:Ideath|Ideath]] 07:14, 7 January 2012 (UTC)) strongly recommend budgeting for more than those minimum before & after tasks.
-** set goals for the meeting beforehand
+** set goals for the meeting beforehand (Needs delegates from collective & noncollective)
 * '''Non-collective staff meeting'''
 ** needs facilitator and agenda, should precede all-staff
@@ Line 37: / Line 30: @@
 ** if we hold these, they should be staggered due to personnel overlap
 * '''Staff trainings'''
-** consensus process? (someone on-staff? non-collective, perhaps?)
+** to be planned by staff. orientation to process, structure, procedures and culture for new and not-so-new folks.
 ==Publicity==