Posted by: circadia | May 18, 2008

Groupwork

For better or worse, I have taken leadership on the project of trying to start up a cooperative business whose main purpose will be urban farming in underused spaces: backyards, front yards, abandoned lots. For now, I am the one organizing meetings of the little group of organizers, I’m responsible for keeping records of the outcomes of the meetings, and I’m the main driving force behind the whole project. I’m not completely comfortable in this role, and I often don’t know how best to structure the process so that everyone feels able to contribute and to disagree when necessary. I don’t want to monopolize the discussions, although I am the one with the most fleshed-out vision of where we’re going. It’s hard to find the right balance between going off in too many directions and just walking blindly down the first path you find. I’m getting very tired of being involved in discussions and projects that use one of those two strategies — more frequently the latter one, with the path being chosen by the alpha person in the room at some early meeting.

I don’t want to have to learn too much about facilitating group work either; maybe this is a foolish prejudice, but there is something about applying these consensus-building tools that smacks too much of the corporate mindset. Can’t we achieve the same end state by applying good old-fashioned discussion, argument, consideration of multiple possibilities, winnowing of choices, and so on? ~~~


Responses

  1. You are right. Beside the nicest perspectives provided by cooperative approaches, the reality is very hard, it is hard, I think to facilitate a co-production process taking into account the multiplicity of interests and points of view of the various actors, but I’m still convinced that this way of doing brings better results than a verticalised-hierarchical approach. I’m not convinced about the similarity between this approach and the corporate mindset, because in a corporate perspective this approach is very inefficient, it includes a series of trial and errors cases, it opens to the possibility for individual actors to make mistakes. It is redundant in the way resources are used. A corporate approach doesn’t admit errors and waste of resource. Perhaps your stress (I’m just guessing now) is due to your concern that the development of this “messy” system into the write direction does not takes to many blind paths.
    In your leading position I would be worried, as well, but did you try to see the development from a different perspective? Does it look as hard as you describe it?
    Thanks for you comment on my blog!

  2. Somehow i missed the point. Probably lost in translation :) Anyway … nice blog to visit.

    cheers, Jonathan.

  3. Thank you Nico and Jonathan for your comments. I’m surprised that anyone stumbles into this blog at all; it’s really little more than a weekly time capsule of where my head is at.

    Sometimes I lok back at my own posts and scratch my head a bit.


Leave a response

Your response:

Categories