(Closed) Radical Self Reliant Realizer - KORG rethink
For now I have created this basic text document for use by the Realizers, based on the format used for meeting notes/update text we used last year in KORG meetings.
The formatting is explained at the start of the document and ideally we will have 2 KORG members to oversee critical needs, and another 2 for the Too big to fail sections. These named people will be the check in point for lost or in-need-of-help Realizers, as well as being able to access the KORG discord channel for questions.
I hope this document serves the purpose of collating info for the overview, as well as providing future Realizers with a view as to the issues/timeline & other planning info that was worked on this year.
Tonight at the #1 Realizer Meeting (17.03) I will try to recruit a Realizer Overseer and minimum 4 KORG folk who will be able to decide on a regular meeting schedule, keeping in mind when it works to report to the Board of good news developments or issues that come up. (I suggest to drop in or submit something for review at the Board Meetings).
Thank you all for your feedback. :)
KB2022 Site Lead Realizer
KB2021 KORG lead, Board President, Summer Camp Lead Orga
The advice process
Right now things are moving slow, people are reluctant it seems to join the KORG as they are worried it will take too much of their time.
I would like to implement a way to move forward quickly, with the ability to have a transparent overview of the critical orga areas.
People/roles most affected by this proposal
Board: @Mareike @Veroca R. Sala @Cris @Caro T @Jan-Christian Kaspareit @Cairn (Clément)
@Kate (seems to be doing a lot of the work to recruit right now :) )
People/roles with the most knowledge and experience relevant to this proposal:
KORGi's last year: @Professor Kaos @Hanna-Maija (Animal) @Purzel @CJ Yetman @Diarmaid
@Franzi Leader of the OG KORG 2020
Last year somehow the KORG went from being intended to be no Realizers or Board members to being made up of a lot of them. We did end up taking on a lot of extra overview that was of areas not deemed 'critical' and also there seemed to be a large sense of responsibility or expectation that the KORG would step in and take on the burden of any unfilled Realizer roles if they were not filled.
I am willing to create a system and documentation which would allow Realizers to update weekly (or fortnightly?) on any updates, or issues they have - which would be looked over my myself and preferably a couple of others. This would be either a google sheet, or word document text in the KB Drive folder which would be editable by Realizers/KORG and viewable by any other community member who wished to see an overview of progress or problems in these areas.
This would focus ONLY on event critical or super important too big to fail parts of the event planning, as last year somehow we ended up including very much non critical area updates as part of KORG meetings.
This document could be accessed directly by the Board for their own viewing leisure, or if it makes it easier and they prefer - I am willing to submit a digestible update for Board meetings that would have any major causes for alarm highlighted.
The KORG would be still function as a body for helping point Realizers in the right direction for problem solving i.e. putting them in touch with someone who can answer their questions, prompt for timeline/deadline planning. There would not be a responsibility (as there never inherently was) for KORG to step in and take these tasks on themselves if failing, but they would take initiative in asking community for help if a Realizer needed back up or critical role needs attention.When would this proposal be implemented
I would implement this ASAP if people are happy. I am also scouting on the KORG Discord channel for other willing KORG members / opinions.
What would be the cost (time, money, effort, etc.) of this proposal
No money, just a little of my time and attention (and hopefully those couple of others) to keep an overview of what's going on. It would require Realizers to check in as they always have so that ultimately the Board is aware of progress and problems.
What are the advantages of this proposal (relative to the current situation and/or counter-proposals)
#Immediacy #Radical-Self-Reliance #Participation #Communal-Effort
There is a moving forward in a swift way to give Realizers a sense of the larger picture being drawn by them together and apart.
Realizers are put into the situation where they are more empowered to make decisions themselves without feeling they have a 'manager' above them.
More emphasis can be put on the larger community connecting and helping each other, lessening the idea there is a small group of powerful folk who run the show/fix all the problems/will remove your MOOP for you etc.
What are the disadvantages of this proposal (relative to the current situation and/or counter-proposals)
Some may feel a lack of support. Non critical areas will not be focused on.
One last thing...
Additionally I think it might be important to have a Realizer Co-ordinator role which may be a KORG member, another Realizer or someone who is neither who would also help play the role of recruitment and also potentially to hold larger Realizer meetings (in person or online) to connect Realizers in a face to face manner which is important when thinking about dependencies and also collaborative effort/encouragement etc.
This would hopefully also be the person who non-critical area Realizers could turn to for some support instead of the KORG.