Talk:Collective Level Expectations

Ali already started this page at Staff Survey. We should combine them somehow.

RfS 00:14, 13 March 2009 (UTC)

We need to hash out the expectations in the Needs more discussion area so that we are all agreeing on the same thing. Feel free to move any item from the Solid and ready to go section to the Needs more discussion section if you feel we should talk about it more.

Needs more discussion

• All collective members will keep up with communication tools (email, rt, wiki).

• All collective workers will get paid for attending meetings.

There are two items that we did not agree on that also deal with this item:

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

collective members should be paid for all meetings they attend. If a member abuses this, and attends all meetings, sleeps through them, and is generally unhelpful, we would have to deal with that. If someone did this, they would most likely be slacking in other areas as well. As long as staff members are working and helpful, I think they should be paid for all meetings they attend. Laurel

I like this. We will state clearly what we expect, while not trying to legislate against the exploitation of loopholes. If exploitation happens, it will be dealt with as an HR issue Dave

As long as collective workers are salaried, this is a moot point, as we're paid by the week, not by the hour. As far as paid hourly workers, it's different. Tonyc 04:56, 21 March 2009 (UTC)

Not really. Salaries are calculated on the expected amount of time it takes to complete the work, and so the question becomes which meetings are included in the job description. RfS 20:13, 24 March 2009 (UTC)

The relevant portions of the Oregon Administrative Rules (OAR 839-020-0044 ) states, (1) Attendance at lectures, meetings, training programs and similar activities need not be counted as work time if the following four criteria are met: (a) Attendance is outside of the employee's regular working hours; (b) Attendance is voluntary; (c) The course, lecture, or meeting is not directly related to the employee's job; and (d) The employee does not perform any productive work during such attendance. (2) Involuntary attendance: Attendance is not voluntary if it is required by the employer. It is not voluntary in fact, if the employee is given to understand or led to believe that the employee's present working conditions or the continuance of the employee's employment would be adversely affected by non-attendance. George 17:25, 27 May 2009 (UTC)

That would seem clear enough that most meetings we attend would need to be paid time. -- MW 17:34, 27 May 2009 (UTC)

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

Before we can make sense of the first statement we need to decide on the other two. Dave

I think this involves two, separate things: how much do we want to pay non-salaried folks for meetings, and how much is too much to expect from salaried people? One is a budget issue, one is a burnout issue. Tonyc 04:56, 21 March 2009 (UTC)

Since these are expectations for Collective members and since all Collective members are salaried, there is no need to consider in this discussion what non-salaried workers get paid for in terms of meeting attendance. Ali 20:39, 28 April 2009 (UTC)

Perhaps this one is ready to go. We will pay Staff for attending the meetings that they go to and not try to set a cap for them. If someone is going to way too many meetings and burning out we should talk to them about it and try to get them back on track, but not try to set a hard standard for what is "too much" Dave 19:05, 22 April 2009 (UTC)

As long as we're salaried, and as long as we're committed to paying people for all the work they do, the fact is: "paid" hours spent in meetings equates directly to hours not spend elsewhere (admin/floor shifts).Tonyc 03:44, 23 April 2009 (UTC)

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

What should this number be?Dave

Assuming all collective members are responsible for individual areas/programs, 24 seems like a realistic expectation to me. This allows for at least three 3-4 hour shifts in core coordination areas, a few shorter floor shifts, and enough hours for committee participation/admin time. We should also remember to factor the minumum amount of time we decide collective members should spend working with volunteers into this.Serge

I am happy with this number Dave 19:05, 22 April 2009 (UTC)

In my recent experience transitioning from full-time to part-time, I initially started out at 24 hours but then switched to 28 about 2 months later. My level of general awareness of what's going on around FG was severely limited by being at 24 hours and it's been a noticeable difference for me to be at 28 hours. For this reason, I think that 28 hours should be the minimum. Ali 02:06, 25 April 2009 (UTC)

Couple fussy thoughts:

If we're paid based on hours, but the benefits (health/dental/retirement/etc) are equal to all collective members regardless of hours worked, then technically some of us are being compensated more per hour than others. I don't see this as an issue, really, as long as we're all allowed equal flexibility in hours as our situations require. The ability to drop to part-time as needed is a benefit in itself. This is the biggest wrinkle I see here: some job descriptions/positions are more able to support this flexibility than others. This starts to stray into other areas, such as the ability to take vacation time/personal time based on job-description....you know...Meteor-proofing.

As an org, would we be able to afford this policy if half (or all!) collective workers worked only the minimum? I don't think it's a problem right now, but it could become one.

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. 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. Darryl 21:33, 23 April 2009 (UTC)

I think we pay ourselves too little to require collective members to pay for any portion of their benefits, providing they are working whatever we set as minimum number of hours. Tony brings up interesting points about the flexibility issue. In my opinion, everyone on the collective has the flexibility to change their schedule based on their personal needs. I don't foresee a problem with this, as I can't imagine circumstances where too many people would take advantage of this at the same time. Laurel 01:49, 25 April 2009 (UTC)

I agree Ali 02:06, 25 April 2009 (UTC)

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

What is this cap? Are we hourly or salaried?Dave

We are salaried. The cap should be 40 hours/week. Laurel

I agree. 37.whatever is silly. We all work over 40 hours. We should all be paid for that amount, at least. Tonyc 04:56, 21 March 2009 (UTC)

If we re-calculate our salaries at 40 x $11.55 instead of the current 37 x $11.55, that (a) gives a raise to most of us, and (b) puts the full time workers at the bottom of the bracket where we don't need to worry about legal liabilities relating to overtime laws. I'm a proponent of getting everyone who wants the full time work to be paid for salaries based on a 40 hour week (like the rest of the world). RfS 20:13, 24 March 2009 (UTC)

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

What is this minimum?Dave

Do we want this number to be the same for all collective members, or should this be a percentage for those of us that aren't full-time?Serge

That's a good point. Should the number of "floor" hours be expressed as a percentage of paid hours? What about half? Tonyc 04:56, 21 March 2009 (UTC)

Yes!... as a % of paid hours. Darryl 21:33, 23 April 2009 (UTC)

I don't think that we should require a minimum number of hours spent working floor shifts (unless it's something really small like 8-10 hrs/week), but I do think it's important to have meaningful contact with volunteers and an understanding of the organization as it changes. For example, some positions require much more time spent coordinating volunteers than other positions do. But it is necessary for any Collective member to be in touch with what's going on around Free Geek, especially to have a finger on the pulse of volunteers and to genuinely understand the flow of things. Ali 20:39, 28 April 2009 (UTC)

What about changing the text to this: All collective workers are required to spend an adequate and equitable amount of time working with volunteers

I feel this better expresses the spirit of the concept as well as the ideas in the discussionDave 19:35, 27 May 2009 (UTC)

• All collective workers are required to perform tasks that nobody wants (or not enough people want) to do.

What are these tasks? How do we split them up and hand them out?Dave

I think what the tasks are (exactly) will vary over time. RfS 20:13, 24 March 2009 (UTC)

Rotate these like chores on the fridge "wheel of drudgery" Darryl 21:33, 23 April 2009 (UTC)

I feel that we don't want to get into too many specifics in these statements and this is a statement that really needs specifics in order to at all meaningful. We should try to figure out what we are really trying to say and rephrase it. It seems like this is kind of a "boss clause". How do you get people to do undesirable parts of the job when there is no one telling them to? How about: All collective workers are required to perform and complete parts of the job that are neither fun or meaningful Dave 19:22, 27 May 2009 (UTC)

I like that. simple and to the point. MW

• All collective workers are required to participate in a minimum number of committees.

What is this number? Right now it seems to be two.Dave

I don't think it seems to be two. It is two. That's what I was told when I joined. If we want to change it, let's. But I'm going with a default of two. Tonyc 04:56, 21 March 2009 (UTC)

Wow. I musta been cranky when I wrote that! I gotta start using more emoticons.Tonyc 03:44, 23 April 2009 (UTC)

We used to say two for full-timers and one for part timers. There are currently 18 committees/working groups when all are running. There are 13 collective members. (2 part-timers, 11 full-timers). This would work out to 24 slots available for the 18 groups, which is 1.33 people per group (plus hourly workers and volunteers). Please remember this math when thinking about creating new committees. Point is, people are actually on more committees than the minimum, and if everyone is on the minimum amount, some committees would be short. RfS 20:13, 24 March 2009 (UTC)

It's two! Any objections? Dave 19:05, 22 April 2009 (UTC)

My only need for clarification here is whether a Working Group counts as a committee. If there's a distinction, it should be clarified in our policy. Could word it to be two committees and on WG? Just a thought. Truth is, it's a baseline that's just not an issue right now since we're all in up to our eyeballs.Tonyc 03:44, 23 April 2009 (UTC)

Some people are only involved in the minimum number of committees, so this is a relevant discussion. If the minimum is 2 committees for a full time Collective member, and the majority of folks are actively involved in much more than that, is it fair that others are only engaged in 2 committees? If there is X amount of committee work to be done and not everyone is sharing in that work, how do we address this? What if someone's 2 committees only meet once a month and are very light-weight in terms of work load? Oh, and I would not count a workgroup as a committee. Ali 20:39, 28 April 2009 (UTC)