OVERVIEW AGENDA (BROAD BRUSH)
The Detailed Agenda often goes several layers deep and can be confusing to some.  To help make it clear here is the High Level (Broad Brush) Agenda

  1. Opening the call (7min)
  2. Purpose and Guidelines for Participation for this Call (7 min)
  3. Sub Group Topics (4 of them): Brief Reports and Deeper Dive Subjects (50 min)
  4. Evolving IO as an Organization / Working as a Team / Using the Protocols (20min)
  5. Other Items (Larry and Brandi items mostly)  (20 min)
  6. Closing the Call:  (6 min)

 

DETAILED CALL AGENDA:

  1. Opening the call (7min)
  1. Welcome any Newcomers to this call
  2. How Maestro Works :
  3. (1 Stack, 2 Twinklies, 3 Disagree  4 Direct Respond  5 Point of process.)
  4. Check-Ins (30 seconds each)
  5. Changes / Additions to the Call Agenda?
  6. Length of Call: Several have discussed the possibility and need to extend the amount of time for this and some future Thursday IO Planning meetings.  Shall we stick to 2hours or agree to go longer? (Time estimates, below and above, reflect a two hour call.)
  1. Nate.  OK to do today, not make a habit of it.
  2. Cal: Check in 15 mins before the end of 2 hours to see how we are doing and extend as needed.
  3. Go with Cal’s idea?  Yes

 

 

From previous call:  “Please reiterate that this is a planning meeting – a short call with lots to do! Newcomers are welcome but we ask that they hold their general questions for after the meeting so that we can stay on purpose and on schedule.”

  1. Purpose and Guidelines for Participation for this Call (7 min)
  1. The purpose and “openness” of this call has been discussed several times including at the Dec 19 -20 meeting.  We are still unclear as a team about it.  So we need to get clear and aligned as a team.
  2. Clarity is needed on on two fronts:
  1. 1) Here and Now/ How this call is to be conducted
  2. 2) Going Forward / How this call is characterized and managed from here on out (IO Business?, By invitation?, Way Open?  Might decide on this at end of call because it may get very clear by going through this agenda.)
  • Larry, on outreach call Discussed on-boarding process with buddy process:  Orientation → Training → Buddy System → TA Support → Active Participant → Invitation to Thursday Call
  • Steve, size of group, and the
  • Brandi: Watching from outside.  Having process is important.  Channels of contacts should be clear(er).  Jump in process, (with regards to how much of each of these steps is a new step and easily over whelming-therefore possibly discouraging)
  • Tammy, Proposal, Newcomers on Orientation call or whatever,  buddy system, directed to / into sub groups, everyone on each sub group is who comes to the Thursday call.(PASSED WITH CONSENSUS as Guideline; If needs to become a policy, take it up later.)
  1. Thursday call question.  Is Tammy’s proposal closing other openings to join the Thursday call.
  2. Brandi
  • Nate;  Potential for abuse in an open system, we have been lucky, Maestro can mute bad offenders.  Want to keep things open.  like Tammy’s prop.  Consent to put all recordings and minutes on site.
  • Jay’s Understanding of options:
  1. Guideline: Orientation, then Sub-Groups, then Thursday Night Planning Call. – - Consensus Achieved as Guideline; if needs to become a policy, take it up later.
  2. Just Listening – no mic for public (would pertain to reporters and movement participants) – Bike Racked/Tabled
  3. Membership – 2 calls before you can block/hold things up –  Bike Racked/Tabled
  4. Call Right now? – Everyone Can participate Fully Yes -8 No – 1 (Stood aside)
  • MP3 and notes on web  Consensus Achieved (One stood aside)
  • What does it mean by a newcomer – not applicable for future calls
  • Reporter:
  1. Michael, Can MSNBC be allowed to come on next Thursday night call,?  yes/no/stand aside
  1. First Vote: 1-No
  2. Second Vote: 9-Yes 2 -Stand Aside
  • Option 2: Can come to Thursday only if come to Monday first?


  1. Sub Group Topics: Brief Reports and Deeper Dive Subjects (50 min)
  1. ADMIN (12)
  1. Quick report (if needed)
  2. Field Call Requests and make Determinations: ?
  1. Call Requests are sent to Call Planning Subgroup for vetting and approval
  1. (basic) course. “run” to “support”
  2. “suggested or required” basic training, encouraged advanced!
  3. CONSENSUS ON a & b


  1. Once Approved, Call Request is forwarded to Andrea for Scheduling
  1. Call is Posted online, in call roster http://bit.ly/callroster) and in email blasts to announcement group
  2. Put on Call Calendar (Google Calendar) http://interoccupy.org/call-calendar/


  1. New Email Addresses on hold  (except for volunteers@interoccupy.org)
  1. We’d like to put this on hold, until a need is obvious, its redundant. Info can forward emails to appropriate subgroups as needed. (use jr and announcements as example)


  1. New Google Groups
  1. Transition – where do we stand on it
  1. Communication Structure Diagram by Joan: http://bit.ly/IO-commstructure
  2. emphasizing team practice of emailing only the people who need to know.
  3. UNANIMIOUS PROPOSAL clarify all-io-subgroups is for anyone on thursday call
  4. Clarification: all-io-subgroups is for business, io-general – is for discussion and announcements
  • Clarifications or Changes
  • Related Special Topic on Working as a Team (below) – Don’t know what this is.
  1. ? Code of Conduct??
  • Andrea would like to make it a requirement for people requesting calls to go through maestro basic and advanced training with Steve.
  1. Do we agree?
  2. Can we we publish it on the website? unanimous
  3. Link for all Online Meeting Options that don’t require IO training: (Jay)
  1. https://docs.google.com/document/d/1m11OEtWNx5OPsNABcX3hwAYBTPdwjvD3dG06dZ15-sA/edit
  • Work Goals and Plans (6 week)


  1. Web (12)
  1. Quick report (If needed)
  1. Click Here for Sub Group Agenda
  • Going Live with New Look (need at least on other to help with this)
  • Categories and Menus Revamped and rolled out (done at same time as going live)
  • Who will administer what on the Web going forward (Discussion 8min)
  1. Field Call Requests and make Determinations: (Covered above)
  2. Call Request Scheduling and Posting: Andrea? (Covered above)
  3. Announcements: JackRabbit?
  4. Actions/ Communiques (good to combine? who will do this?):
  5. Slide Show/Main Page Content Refresh  (twice a week? Who will do this?):
  6. CoC related Lists, Pages, Permissions (what needed, who will do?
  7. Web Style and Navigation Adjustments: (an occasional tuning, not daily admin)
  8. Build a Call Agenda/Notes Maestro Participant Dashboard User Page: (Hassab’s Idea.  Do we like it?  If yes, Who will build it?)
  • “Channel of Communication” need and function. (Tammy’s request)
  1. What is appropriate and manageable on our site?
  2. What Communication Tools outside our site should be considered?
  • Work Goals and Plans (6 week)


  1. Outreach (12)
  1. Quick report (If needed)
  2. (added by andrea) FROM NATE – Orientation Call- This one is pretty self-explanatory. I think that folks should follow a process to acclimate them to the system. It is unrealistic to expect folks to be able to jump into the process without being ushered into it and I think it is Outreach’s job to find them, orient them, support them, and then invite them to join the team. Just enough time after the Monday call announcement for disingenuous people to become uninterested and really interested people to plan for it.
  1. be invited to the orientation call which Outreach can provide,
  1. Wednesday nights at 9PM
  • sign up for TA training,
  • be assigned a buddy,
  • TA or facilitate three calls (the two with the buddy) and then,
  • be invited to the Thursday call.
  • (added by andrea) FROM LARRY Buddy System- in addition to recruiting and acclimating new folks to the process we also need to support them as we grow. We have talked many times about the buddy system but, as far as I am aware, no one has proposed a process for it.
  1. when someone goes through the orientation call then they should be assigned to someone in Outreach.
  2. After Steve and myself train them then the Buddy who was assigned to them will be on their first two calls that they TA to support them and offer assistance.
  3. During the Buddy period we would basically just offer to answer questions and be available to support them.
  4. The orientation and training call should solve alot of these problems but it will be good to have some accountability and take some of the pressure off Steve and Andrea.
  • Work Goals and Plans (6 week)
  • 1/10/2012 Committee of Correspondence Conference Call (In Process of Scheduling)


  1. IO Call Planning (12)
  1. Quick report (If needed)
  1. 40 in queue for basic course, 8 in stack for advanced.
  2. New breakout policy – TAs and facilitators will separate out “presentation” breakouts, if everyone mainly wants to listen to someone else talk. These can be bigger breakout groups if lots of people want to listen to the same person (instead of automatically breaking out into groups of 6 or 8, or whatever it usually is).
  3. Media alternating Sundays. DA alternating Tuesdays at 6p PT
  4. Aggressively want to build pool of TAs to service calls. Volume will continue to increase.
  5. Strongly reassuring encouraging external calls requests to send facilitator and TA to classes.
  1. IO Call Ecosystem Design Discussion:  Frequency, Adjustments, Changes + New Calls
  1. Movement Building (To Be Designed)
  2. CoC Call  (To Be Designed)
  3. Orientation Call (To Be Designed)
  4. Issue Specific  (To Be Designed)
  5. Working Group subjects (Like DA, Media but not yet covered, new ones To Be Designed)
  6. Geographically Organized calls (Organizing by request)
  7. Others
  8. When to say “no” to a call request and how to direct them to self organizing solution (not using Maestro)


  1. Clarifying Existing Calls
  1. Direct action and Media calls – do we hand them off?
  2. Hearts and Minds call – the future of that call?
  3. Facilitation Call Clarified:
  4. Friday Tech Call Clarified
  5. David Balkin web/tech calls.  Wiki start again next week?  CRM is cancelled.
  6. Other Call Clarifications?


  1. Call Planning Subgroup Work Goals and Plans (6 week)?

 

 

  1. Evolving IO as an Organization / Working as a Team / Using the Protocols (20 min)
  1. Organizing IO and Teams for High Performance, Accountability and Transparency
  1. Status, Accomplishments, Challenges?


b.  Code of Conduct and Statement of Autonomy;  Status, Discussion,Vote
Links are bellow…
Proposal:  Adopt the current Conduct of Accountability:  With our Agreed Upon Decision Making-Process. 91% to 8%  Yes – 11 No-1  PASSES
Proposal: Adopted the Statement of Autonomy :) Unanimous

  1. Principles and Protocols over Passions and Personalities
  1. What are our Core Principles, Protocols?  (Links here)
  2. Where do we need more work to get them articulated?
  3. Who will shepherd and what process to complete that work?
  4. What is the remedy for not following the process (addressing concerns for example)?
  5. What is the remedy for repeated disruptive behaviour?
  • Team Communications: When to Phone, when to Email, when to meet on Phone, in person)
  • Email Forums:  Best Practices, Ground rules and Principles.  Status and Discussion
  • Finance / Budget / Raising Money / Legal Entity.  Status and Discussion
  1. IO Yearly Bugdet doc (drafted by Joan) – http://bit.ly/IO-yearly-budget
  2. Paying people and sustaining IO as an Organization:  (When and how to have that deliberation?)
  • Next steps for Organizational Design.  Needs discussion.
  1. Special meetings to focus on Organizational Design and Core Service Delivery?
  1. Proposal:  Schedule three 2 hour calls in addition to the Thursday call to cover the OD work that doesn’t get done otherwise.  (If not a special meeting series then what is Option 2?)
  2. Extend Thursday Meeting Times: Four Hour Thursday Calls until the backlog is caught up?
  3. Third Option?
  • Next Face to Face Meeting?


  1. Other Items  (20 min)
  1. (added by Larry) PR Subgroup -to handle press releases and coordinate who will talk to media. The group could then report back on Thursday call and ask for volunteers for any radio, print, or tv interviews.
  2. Proposal from Larry: I propose that we make it official that we do not use blocks. It’s use is so prevalent in the Movement that people will expect to be able to block unless we explain that we have a 75%-modified consensus decision-making structure.
  3. (added by Larry) National Gathering Proposal Update from Philly and what it means for InterOcc.
  4. (added from Tammy) IO – International subgroup?
  5. (brandi) maybe part of earlier natnl group discussions…how are others seeing the language direction (many trying different subtitles) and how do we start those discussions. email sent to Outreach. power and problems with the term. Not to be decided today, but wanted to throw the topic out there for people to think about and talk to me about as we are struggling with Occupy label in Colorado. Not all places have had the “Denver Dynamic” in quite the same way.
  6. (brandi) facilitation intro letter….and other buddy system ideas. more visuals as to structure and what email topics go to who. flow charts. and other cool write ups. Nate has been putting out good stuff. Have not read through all of it just yet. (I think it was Nate) Link below to facilitation letter.
  1. CLICK HERE FOR Facilitation Conference Call Intro Letter
  2. https://docs.google.com/document/d/1lLot_9gh-Dv51E9WY1HC7dB2xaHRPYZhlsfyJymXbpo/edit?hl=en_US

 

Unanimous Approved – Statement of Autonomy – http://bit.ly/IO-Statement-of-Autonomy
PASSED 11 to 1 – Code of Conduct – http://bit.ly/IO-Code-of-Conduct
Call Ground Rules – http://bit.ly/IO-Call-Ground-Rules

 

  1. Closing the Call:  (6 min)
  1. Review “Action Required” (AR) and assignments and resulting from this call.
  2. Brief Check-Outs
  1. End