Create a guide for the work of your circle!
Considering that oikos is rather complex, we give our best to create clarity as we ride on the wave of change. Field guides aim to provide this clarity by giving further insight into the work of every circle. They are referred to in the organizational guideline and used by every circle to coordinate & organize their work.
How to set up a field guide
Field guides can have different elements and structures. They are living documents, which means updates can happen in the same document. Here’s a template for a field guide with potential elements that can help you in creating yours. A rule of thumb is: every circle (& if feasible, every sub-circle) should have a field guide & there is no right or wrong way. It is meant to support you in your processes.
Check out the examples from the chapter lifecycle circle, the homecoming initiative or the advisory council.
What goes into a field guide, what doesn't
| GO! | NO! |
|---|---|
WHO is responsible for field guides?
Field guides can in general be set up by any oikos International Team member. The ownership lays by a person(s) who takes over the responsibility in the circle. As this is a tool for better working together, make sure to not only create a field guide and say “hey look, here it is”. Always (!!) involve the people affected and consider storytelling, PP presentations or video tutorials when introducing a proposal or implementing changes to make sure people get how you plan to use it.
HOW to update a field guide?
Field guide changes can be expected regularly. The rule of thumb for the revision process, therefore, is: as often as needed, with at least one annual revision by the roles that are most related to the guide. Once updated, the relevant circle is asked for their consent on the update.
WHERE to store field guides? Store the field guide document in your local folder, close to where the work happens and where you can find it. As a second step, make sure to link the document in the field guide folder, so that we keep an overview of all the guides and make sure they all get updated in time.
HELP & SUPPORT
Contact Sophie or Elena via Discord :)
‘How’ as a guiding question
The same things that are stated in the constitution, guideline, or user guides
Granular topics that change rather often & description of processes how they change
Too much detail: make sure that the document still serves the purpose to provide orientation
Outcomes of processes, current roles etc. Eg. single program outlines
Templates (link them, but rather create an additional document)
Daily processes & descriptions of these