Talk:Collective Level Expectations - Revision history

Ali: moved stuff from main page

2010-01-16T23:54:38Z

moved stuff from main page

Ali at 23:01, 21 August 2009

2009-08-21T23:01:50Z

Rfs at 18:48, 11 August 2009

2009-08-11T18:48:02Z

Rfs: /* From Job Descriptions */

2009-07-31T15:39:27Z

From Job Descriptions

Rfs: /* From Job Descriptions */ new section

2009-07-31T15:38:58Z

From Job Descriptions: new section

Rfs: /* From General Questions for Collective Reviews */ new section

2009-07-31T15:27:56Z

From General Questions for Collective Reviews: new section

Tonyc: /* There will be a cap on how many hours per week collective members should be paid for. */

2009-06-05T07:18:39Z

There will be a cap on how many hours per week collective members should be paid for.

Rfs: /* Should staff get paid for attending all meetings or just some? */

2009-06-05T01:38:40Z

Should staff get paid for attending all meetings or just some?

Rfs: /* There will be a cap on how many hours per week collective members should be paid for. */

2009-06-05T01:28:47Z

There will be a cap on how many hours per week collective members should be paid for.

Rfs: /* All collective workers are required to work a certain minimum number of hours per week. */

2009-06-05T01:18:10Z

All collective workers are required to work a certain minimum number of hours per week.

← Older revision		Revision as of 23:54, 16 January 2010
Line 1:		Line 1:
		+	As we discuss and agree upon other expectations we can add them to this list.
		+	* At a "Fifth Friday" staff collective meeting on July 31, 2009, we approved several items. These will need to be:
		+	*#<s> reorganized (including the above points),
		+	*# combined to avoid duplication,
		+	*# reworded for clarity, and
		+	*# finally approved by the staff collective.</s>
		+	* At a "Fifth Friday" staff collective meeting on October 30, 2009, we settled on the current wording here. We still need to:
		+	*# Create similar documents for each class of worker:
		+	# Paid Interns
		+	# Committeds
		+	# Nothers
		+	# Subs (can wait)
		+	# Exploratory Positions (can wait)
		+	*# Compare the expectations documents for each level with each other looking for items we may have missed.
		+	*# Settle on "final" draft of this whole "family" of expectations documents.
		+
		+
	'''Meetings, committee membership, floor shifts, and undesirable jobs are all work items that should be shared amongst all collective members. While it's unlikely that we can divide these tasks up using an exact number of hours or percentage per collective member, we agree that there is a (currently unidentified) range of acceptable workload for each of these items.'''		'''Meetings, committee membership, floor shifts, and undesirable jobs are all work items that should be shared amongst all collective members. While it's unlikely that we can divide these tasks up using an exact number of hours or percentage per collective member, we agree that there is a (currently unidentified) range of acceptable workload for each of these items.'''

← Older revision		Revision as of 23:01, 21 August 2009
Line 1:		Line 1:
		+	'''Meetings, committee membership, floor shifts, and undesirable jobs are all work items that should be shared amongst all collective members. While it's unlikely that we can divide these tasks up using an exact number of hours or percentage per collective member, we agree that there is a (currently unidentified) range of acceptable workload for each of these items.'''
		+
		+
	Ali already started this page at [[Staff Survey]]. We should combine them somehow.		Ali already started this page at [[Staff Survey]]. We should combine them somehow.

← Older revision		Revision as of 18:48, 11 August 2009
Line 170:		Line 170:

	== Solid and ready to go ==		== Solid and ready to go ==
−
−	~~== From [[General Questions for Collective Reviews]] ==~~
−
−	~~A collective member at Free Geek ...~~
−	* arrives on time or calls if going to be late.
−	* is efficient and makes good use of time.
−	* uses the phone, socializes, and takes breaks at appropriate times.
−	* is aware of safety on the job.
−	* leaves volunteer-inhabited areas clean and ready for next shift.
−	* actively participates in meetings.
−	* is a reliable member of standing committee.
−	* puts the interests of Free Geek before personal interests while working.
−	* makes volunteers and donors feel welcome, actively reaches out.
−	* actively involves volunteers in appropriate projects.
−	* is courteous and friendly.
−	* listens to volunteers/donors and tries to meet their needs.
−	* communicates effectively with other staff/core concerning needs of his/her area.
−	* accurately assesses her/his own abilities and constraints when taking on commitments.
−	* follows through with commitments.
−	* gives and receives constructive criticism.
−	* communicates directly to solve conflict.
−	* appropriately uses the standard tools Free Geek has available to do her/his job. (These tools might include email lists, RT, the wiki, bulletin boards, etc.)
−	* offers a safe space to communicate if issues arise.
−	* integrates into the whole of FG.
−	* sets goals.
−	* contributes to other areas of FG, presuming s/he has time.
−
−	~~== From Job Descriptions ==~~
−
−	~~A collective member ...~~
−	* is a volunteer coordinator of some sort or another.
−	* attends meetings as necessary.
−	* learns procedures for other parts of Free Geek and fill in as necessary.
−	* participates in collective management structure.
−	* has basic computer knowledge (use of web browser, email and word processor, database and spreadsheet).
−	* is able to multi-task.
−	* is able to work in a consensus decision making process related to staff and policy issues.
−	* is patient and courteous with the public.
−	* is able to work with and coordinate volunteers with a wide range of skills and experience.
−	* is able to work in an informal, friendly environment with a diverse staff.
−	* works well under stress in an unusual setting, maintaining a positive attitude even in the face of adversity.
−	* is not afraid to ask questions.
−	* but is able to work on projects almost entirely without supervision.
−	* is self-motivated.
−	* is able to remain flexible as Free Geek grows and changes.
−	* is able to work well under stress in a somewhat chaotic setting and maintain a positive attitude.
−	* is be afraid to ask questions but will be able to upkeep the area almost entirely without supervision.
−	* is able to remain flexible as Free Geek grows and changes.
−	* participates in a peer review process.
−	* is an active member of the committee(s) that relate to his/her job.

@@ Line 200: / Line 200: @@
 A collective member ...
-* are volunteer coordinators of some sort or another.
+* is a volunteer coordinator of some sort or another.
 * attends meetings as necessary.
 * learns procedures for other parts of Free Geek and fill in as necessary.

← Older revision		Revision as of 15:38, 31 July 2009
Line 196:		Line 196:
	* sets goals.		* sets goals.
	* contributes to other areas of FG, presuming s/he has time.		* contributes to other areas of FG, presuming s/he has time.
		+
		+	== From Job Descriptions ==
		+
		+	A collective member ...
		+	* are volunteer coordinators of some sort or another.
		+	* attends meetings as necessary.
		+	* learns procedures for other parts of Free Geek and fill in as necessary.
		+	* participates in collective management structure.
		+	* has basic computer knowledge (use of web browser, email and word processor, database and spreadsheet).
		+	* is able to multi-task.
		+	* is able to work in a consensus decision making process related to staff and policy issues.
		+	* is patient and courteous with the public.
		+	* is able to work with and coordinate volunteers with a wide range of skills and experience.
		+	* is able to work in an informal, friendly environment with a diverse staff.
		+	* works well under stress in an unusual setting, maintaining a positive attitude even in the face of adversity.
		+	* is not afraid to ask questions.
		+	* but is able to work on projects almost entirely without supervision.
		+	* is self-motivated.
		+	* is able to remain flexible as Free Geek grows and changes.
		+	* is able to work well under stress in a somewhat chaotic setting and maintain a positive attitude.
		+	* is be afraid to ask questions but will be able to upkeep the area almost entirely without supervision.
		+	* is able to remain flexible as Free Geek grows and changes.
		+	* participates in a peer review process.
		+	* is an active member of the committee(s) that relate to his/her job.

← Older revision		Revision as of 15:27, 31 July 2009
Line 170:		Line 170:

	== Solid and ready to go ==		== Solid and ready to go ==
		+
		+	== From [[General Questions for Collective Reviews]] ==
		+
		+	A collective member at Free Geek ...
		+	* arrives on time or calls if going to be late.
		+	* is efficient and makes good use of time.
		+	* uses the phone, socializes, and takes breaks at appropriate times.
		+	* is aware of safety on the job.
		+	* leaves volunteer-inhabited areas clean and ready for next shift.
		+	* actively participates in meetings.
		+	* is a reliable member of standing committee.
		+	* puts the interests of Free Geek before personal interests while working.
		+	* makes volunteers and donors feel welcome, actively reaches out.
		+	* actively involves volunteers in appropriate projects.
		+	* is courteous and friendly.
		+	* listens to volunteers/donors and tries to meet their needs.
		+	* communicates effectively with other staff/core concerning needs of his/her area.
		+	* accurately assesses her/his own abilities and constraints when taking on commitments.
		+	* follows through with commitments.
		+	* gives and receives constructive criticism.
		+	* communicates directly to solve conflict.
		+	* appropriately uses the standard tools Free Geek has available to do her/his job. (These tools might include email lists, RT, the wiki, bulletin boards, etc.)
		+	* offers a safe space to communicate if issues arise.
		+	* integrates into the whole of FG.
		+	* sets goals.
		+	* contributes to other areas of FG, presuming s/he has time.

← Older revision		Revision as of 07:18, 5 June 2009
Line 104:		Line 104:

	: This could be read to contradict the minimum number of hours needing to be 28 (or 24 or whatever we decide). I think a "full" salary should be based on 40 hours, and the part-timers get a % of that salary. [[User:Rfs\|RfS]] 01:28, 5 June 2009 (UTC)		: This could be read to contradict the minimum number of hours needing to be 28 (or 24 or whatever we decide). I think a "full" salary should be based on 40 hours, and the part-timers get a % of that salary. [[User:Rfs\|RfS]] 01:28, 5 June 2009 (UTC)
		+
		+	: That's a good point, Rfs. I worded the previous line in a clumsy way that contradicted the flexibility factor of having full collective members that work for a % of hours and pay. It feels like we're fishing for a range of acceptable work loads. Feels like the min. is hovering around 24-28 and the max is the standard 40. The max paid hours should be 40 imho, but we should also set a max of actual hours we'll accept for the people who tend to do more as a burnout prevention measure. It's a cultural thing to discourage salaried folks from doing more than is healthy. [[User:Tonyc\|Tonyc]] 07:18, 5 June 2009 (UTC)

	===All collective workers are required to spend a minimum amount of time working with volunteers. ===		===All collective workers are required to spend a minimum amount of time working with volunteers. ===

← Older revision		Revision as of 01:38, 5 June 2009
Line 42:		Line 42:

	:: I think there is allot of overlap here (between committe work and floor shifts) and I agrey with you. if a floor shift is defined as something like "spending time with volunteers in a meaning full way" then id say we can turn anything into a floor shift (and should). Its hard for me to think of things that could not be defined as floor shifts. In reality what happens is we end up doing the work we create and call it admin work.(I'm probably writing this in the wrong section) --[[User:Matteo\|Matteo]] 03:53, 28 May 2009 (UTC)		:: I think there is allot of overlap here (between committe work and floor shifts) and I agrey with you. if a floor shift is defined as something like "spending time with volunteers in a meaning full way" then id say we can turn anything into a floor shift (and should). Its hard for me to think of things that could not be defined as floor shifts. In reality what happens is we end up doing the work we create and call it admin work.(I'm probably writing this in the wrong section) --[[User:Matteo\|Matteo]] 03:53, 28 May 2009 (UTC)
		+
		+	::: There are (at least) three categories of work here:
		+	:::# floor shifts (have to be there, with volunteers or public)
		+	:::# other necessary work that must be done in a certain tight time range but doesn't include managing volunteers (for example calling in payroll, beancounting, bookkeeping) -- things where stuff falls apart fast if they're not done
		+	:::# straight admin time (answering emails, documentation, etc.) -- things that can usually wait awhile, even if they're important
		+	::: Anyway, we agree that everyone needs to do some reasonable amount of floor shifts. On top of that, your job description might require more or less work from that second category. Whatever wording we use in the long run, it should be an attempt to balance the work load as a whole, not '''just''' balance the floor shifts.
		+	:::[[User:Rfs\|RfS]] 01:38, 5 June 2009 (UTC)

	====Should there be a cap on the number of committees a collective worker should participate in? ====		====Should there be a cap on the number of committees a collective worker should participate in? ====

← Older revision		Revision as of 01:28, 5 June 2009
Line 96:		Line 96:
	''"Collective members are paid based on an expectation they work 40-hours/week, no more and no less."''		''"Collective members are paid based on an expectation they work 40-hours/week, no more and no less."''

		+	: This could be read to contradict the minimum number of hours needing to be 28 (or 24 or whatever we decide). I think a "full" salary should be based on 40 hours, and the part-timers get a % of that salary. [[User:Rfs\|RfS]] 01:28, 5 June 2009 (UTC)

	===All collective workers are required to spend a minimum amount of time working with volunteers. ===		===All collective workers are required to spend a minimum amount of time working with volunteers. ===

@@ Line 71: / Line 71: @@
 Having many, part-time collective members could tweak the spirit of the ratio policy (collective/non-collective workers). Could be addressed by changing the ratio policy to reflect hours in each category, not the number of workers. Just a thought. [[User:Tonyc|Tonyc]] 03:44, 23 April 2009 (UTC)
 Maybe benefits for collective members could be based on hours worked.  e.g. if you were to work 24 hrs/wk (60% of full time) then you could get benefits, but would supply 40% of the cost for them.  [[User:Darryl|Darryl]] 21:33, 23 April 2009 (UTC)
@@ Line 81: / Line 83: @@
 I can get behind that. As long as the collective can maintain the flexibility to allow any member to drop in hours to the minimum, I'm fine with bennies remaining full for all and the number being set in the ballpark of 28.[[User:Tonyc|Tonyc]] 02:57, 28 May 2009 (UTC)
 === There will be a cap on how many hours per week collective members should be paid for.===