![Minutes: Process: Infoco 2010-09-07 [Minutes]](display/images/gocohologo.gif)
Process: Infoco minutes: 2010-09-07
Minutes:
Minutes of InfoCo Meeting9/7/10
Present: Elph, Mary, Tammy, Catherine, Amy, Liam
1. Facilitation planning for the 9/20 Community Meeting – Tammy & Amy are
facilitating
A. Hoop House proposal
Kate consulted with an extension agent, who recommended against building a
hoop house for one season only. However, Kate heard a lot of enthusiasm
from the community, and she is willing to propose to help/advise GO on
building mini- or quick-hoop houses for GO’s use.
InfoCo recommends that Kate work with Grounds on this idea first, to make
sure it is something Grounds will support, particularly since it would need
to be included in the budget process. The Grounds Committee’s next meeting
is 9/13.
We will wait to hear how this goes at Grounds and then decide whether to
present this on 9/20 or postpone this item. We will develop a Plan B agenda
item in case of postponement.
B. Meals Discussion item
The Meals Committee has heard a number of concerns about the Meals program
and has identified the top two concerns to bring before the community to
find out if community is satisfied with the status quo or would like the
Meals Committee to make changes. The two items are:
1) Increase meal attendance and general satisfaction
2) Support and seek ways to increase numbers of Head Cooks
We discussed the process for each agenda item separately, on the assumption
that they will come up at separate meetings. Mary, Nancy, and Amy met
yesterday and came up with an outline of data that could be presented as a
backdrop to these discussions.
ITEM 1: Increase meal attendance and general satisfaction
Process:
1) Frame the issue
2) Present data in a fun and engaging format (Elph will help with this;
he suggested a game show format)
3) Present problems that Meals has heard about; invite missing issues
4) Small group discussion by problem: task is to suggest solutions,
improvements that will help increase meal attendance and general
satisfaction with meals
5) Report back
6) Next steps; what would the community like Meals to do.
We decided to focus on changes to improve the experience of people who
participate in meals regularly or sometimes rather than to focus on the
people who don’t participate at all.
Nancy was tasked yesterday with talking with the ¼ of the community that
attends the least meals.
MONKEY: Mary will review the participation list and modify it for Nancy so
that she is focusing on people higher up on the curve.
More data questions:
How many households who eat a lot of meals also do meals work?
What’s the avg meal attendance by night of the week?
Tammy likes to crunch data so if we get data to her she will work with it!
ITEM 2: Head Cooks
When there is a mismatch of the # of cooks/workers to the # of meals, do you
increase workers or decrease meals? And do you do it by default, or do it
intentionally?
Right now the number of meals gets reduced when there aren’t enough workers,
but it is not done according to an agreed-upon policy, and this causes a lot
of stress for the Work Committee and Meals Scheduler. This is something
that needs to be addressed, but we think it is the Work Committee’s job, not
Meals’, because the issue is bigger than Meals. It is intertwined with the
entire work system’s hours.
Meals’ job is to make the Meals Program work as effectively as possible. We
currently have and agreement to offer 5 (or really 4-1/2 if you factor in
Sunward meals) meals/week by agreement. Until the comty changes that, it’s
Meals’ job to focus on making this work.
So for now, Meals will just focus on the problems that Head Cooks have and
how could we address that.
Process:
1. Frame the issue
2. Present data and problems that cooks seem to be having. Make this
fun, and get Elph to help make it interactive again.
MONKEY: Get data from Willie about how many meals lack enough head cooks,
crews, and how many missing shifts are filled by the Job Fair.
3. Invite missing pieces
4. Divide into these small groups with specific questions:
* Current Head Cooks – what can we do to support you? How could you support
the other two groups? Under what circumstances would you sign up for more?
(Work survey was changed this time from 4 to 2 meals per season and not
everyone realized that.) If you have reduced your load, under what
conditions would you increase it?
* Used to be a Head Cook but stopped – What happened? Under what conditions
would you be willing to resume cooking?
* Never have been a Head Cook – What would need to change for you to become
a Head Cook?
5. Report back
6. Next steps – what would the community like Meals to do next
MONKEY: Get data from Willie about how many meals lack enough head cooks,
crews, and how many missing shifts are filled by the Job Fair.
2. Consensus training
We now have a powerpoint presentation about consensus decision-making at GO.
Amy has presented it to Kate and Peter, and got great feedback from them.
We have three new members: Elisha, Kendra, Syndallas – Catherine offered to
share the powerpoint presentation with them when she meets with them.
MONKEY: Amy will review the document and put it on Google docs shared with
everyone. Then she will send URL to Infoco.
3. Topics for future InfoCo meetings
- When in discussion and new ideas come up, at one point do you go
into a sub-discussion?
- How to make meetings more fun and interactive?
- Making sure we know where the mandates are for all of the
committees.
4. Updating InfoCo's mandate
Amy edited the document with proposed changes. Energy was lacking on Infoco
for this, so Amy has asked Process to review it and will report back.
5. Next Meeting
Tuesday, October 5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gocoho.org/pipermail/infoco-minutes_gocoho.org/attachments/20100913/482cc514/attachment-0001.html>