Policy Example: Organizational Model

CREEKSIDE COMMONS COHOUSING

ORGANIZATIONAL MODEL

 

Background to how we got here…

This proposed organizational structure is the product of several Council meetings investigating:

- What works here at Creekside?

- What we’ve seen work elsewhere?

- What seems to need change to work better?

- What tasks are we doing to keep our Community & facilities functioning?

- 5 alternate models of organization (based on previous meeting feedback) & what still

  needs attention

 

At the March 13, 2010 Council meeting, the Organizational Review team was tasked with creating a hybrid of the 5 models that would reflect favoured features in each, and would address additional concerns raised at that meeting.

 

Alan, Brian, Don, Mary, Nancy, Pam, Phil, Rene, Rod, Sharon, Terry, & Tim met and created a proposed organizational structure. The following model represents the results of that effort.

 

Some guiding principles behind this model…

- Visualize a circular structure of interdependent teams around our central Community

   Council

- Keep on-going feedback in the structure so that a lengthy re-organizational review is not    necessary in the future

- Assume people want to volunteer

- Make team mandates less overwhelming

- Make room for those people who want to help but don’t do meetings

- Minimize bureaucracy & unnecessary steps

- Empower teams with clear mandates & the Decision-Making Criteria questions

- Focus on optimizing communication

- Encourage individual responsibility

- Highlight the tasks that must be done and will cost us in higher strata fees if we don’t

  to do them ourselves – this way all of us, and any new residents are clear

  on how volunteerism is linked to our enjoyment of  low strata fees

 

Some remaining issues that emerged in our discussion that are beyond the scope of this ad hoc team & will require Community Council conversations & decisions…

Proposals – Where do they start life? How do they proceed to consensus in a way that optimises community input & minimizes frustration for people with ideas & passion?

Decisions – Do we have a shared understanding of our card system  & what constitutes 

   a consensus decision? How do we revisit previously consensed decisions?

Volunteerism – Is it a problem even after we’ve re-organized? If so, what restrains 

  some community members from volunteering & can we fix that? Do we need to explore

  mandatory service options?

CREEKSIDE COMMONS COHOUSING

ORGANIZATIONAL MODEL

 

COMMUNITY COUNCIL

  • This is the ultimate authority for everything that happens at Creekside.  
  • All owners and families are members of Community Council.
  • Community Council will meet at least quarterly for business meetings.
  • Community Council will meet as required for community discussions in order to air ideas fully before Community decisions are solicited & in order to maintain the emotional health of the Community as a whole
  • Community Council delegates the maintenance of Creekside Commons Cohousing to the teams described below.

 

 

TEAM PRINCIPLES

All teams will operate with the following principles:

  • Membership is open to all Creekside residents at all times.
  • One person will be the “contact” for each team.  That person may self-select or be appointed by the team members. This person will have the signing authority for reimbursements &  be the “contact” name given to the Internal Communications & Information Team
  • Teams will undertake tasks described in the team mandate – if unable to meet the mandate they will bring the issue to Community Council for review of the volunteer resources in the community or to review the team mandate
  • Clear mandates are recorded & posted
  • Teams are responsible to operate within the budget assigned to the team at the time of approval of the yearly budget.
  • When deciding on a new action, teams will use the Decision Making Criteria questions to determine 1) if they have prepared the community sufficiently for such a decision (within team’s task mandate) or 2) if the item should be taken to a Community Council meeting.
  • Teams will post agendas to inform the community of upcoming consideration of initiatives & proposed actions that impact common spaces.
  • Teams will take (and post) minutes/reports of meetings at which decisions that affect the community are considered or made.
  • Formal meetings are not a requirement for all teams, or for any team member.
  • Teams will report to Community via minutes or quarterly reports (hard copy posted  & electronic copy distributed/posted on WIKI)
  • The “contact person” signs reimbursement forms for team expenses before going to Finance & Administration.
  • No team members are expected to act as surrogates or ombudspersons. If something appears to need attention, the individual in our community that notices it will bring the item to the team “contact” who will assistthat individual to bring the concern forward in the appropriate forum (team/Council)
  • Ad Hoc Special Project teams will form by Community Council direction and dissolve upon completion of projects rather than being added to existing team mandates.
  • Have fun. Join the team that fits your passion! Or choose a couple of tasks & tell the “contact person you’re taking care of them!

Tags: